Quantcast
Channel: Android Guides – Appuals.com
Viewing all 342 articles
Browse latest View live

How to Install TWRP and Root the Samsung Galaxy S8 and S8 Plus Exynos

$
0
0

The Samsung Galaxy S8 and S8+ are Samsung’s latest Galaxy phones released April 21st, 2017. While Android enthusiasts have yet to root the Snapdragon version of the Galaxy S8/S8+, rooting is already possible for the Exynos variants. This guide will walk you through the steps of rooting the Galaxy S8 and S8+ Exynos variants.

Warning: This guide is only for the Exynos variants (not Snapdragon) of the Samsung S8 and S8+. The Exynos variants are the following models:

Samsung S8 – G950F/FD/N/X

Samsung S8+ – G955F/FD/X/N

Check under Settings > About to make sure your model is one of those listed above.

Required Files:

  1. TWRP: Galaxy S8 here or Galaxy S8+ here.
  2. Odin 3.12.3+ for PC here
  3. Samsung mobile drivers here

Installing TWRP and Root via Odin

You will need to enable USB Debugging and OEM Unlock, found under the Developer options. Navigate to Settings > About Phone > Software Info, and tap “Build” 7 times until it notifies you that developer mode is enabled. After it’s enabled go back to Settings > Developer Options and enable both USB Debugging and OEM Unlock.

  1. Install Odin on your PC. Odin is a rooting and flashing tool specifically made for Samsung phones.
  2. Install the Samsung mobile drivers on your PC.
  3. Open Odin on your PC, turn off your Samsung device, and boot it into Download Mode (hold Bixby + Volume Down + Power).
  4. Connect your Galaxy S8 / S8+ to your PC via USB. You should see an “Added!” message in Odin’s message screen.
  5. Click the PDA tab in Odin and choose the TWRP recovery.tar file you downloaded earlier.
  6. Disable Odin’s “Auto Reboot” in the Options menu.
  7. Press the “Start” button in Odin. The message box will output a few things, and it will say “Pass!” when it’s all finished. Disconnect your phone from your PC.
  8. Turn off your Samsung phone, and boot into TWRP recovery (Volume Down + Power).
  9. Tap the “Install” button in the main TWRP window, and navigate to /twres/flashables/. You will see two files here

    No-verity-opt-encrypt.zip – This will disable dm-crypt thus making /data encryption optional. There are pros and cons to doing this, so research before trying it. If you decide to do so, use TWRP to wipe your /data partition and completely disable encryption.

 

Magisk-v12.0-arm64.zip – Magisk is a systemless root app that modifies your boot image and adds files to your /data and /cache folders. It will only modify the /system folder if it detects a /system root already installed.

  1. If you want to root your Samsung Galaxy S8 / S8+, simply flash the Magisk .zip via TWRP.
  2. After flashing the .zip completes, reboot your phone, and download the Magisk Manager from Google Play store.

The post How to Install TWRP and Root the Samsung Galaxy S8 and S8 Plus Exynos appeared first on Appuals.com.


How to Unlock and Root the ZTE Axon 7

$
0
0

The ZTE Axon 7 is a powerful phone that comes in a variety of firmwares. It is extremely important to pay attention to the steps below and make sure the steps are compatible with your firmware and model version. Thus I have separated this guide into sections for different models where necessary.

You should always have a stock firmware and a backup of your data on standby.

Tools Used in this Guide:

ADB (see also “How to Install ADB on Windows”)
MiFlash (Bootloader unlocking tool for A2017 + A2017U only)
TWRP for ZTE Axon 7 (for A2017 + A2017 only)
SuperSU for obtaining root OR No-Verity-Opt-Crypt for disabling encryption and rooting with something else of your choice. ONLY CHOOSE ONE!
Qualcomm QUSB_BULK Drivers

EDL Packages for MiFlash Tool:

Warning: Unlocking your bootloader will reset your device to factory settings and erase all userdata.

Fastboot Unlock – Unlocks bootloader without installing TWRP or restoring boot stack.
B29_TWRP (Marshmallow 6.0) – TWRP 3.0.4-1 + B29 boot stack.
B15-NEW_TWRP (Nougat 7.0) – TWRP 3.0.4-1 + B15-NEW boot stack.
B15-NEW_FULL (Nougat 7.0) – Complete B15-NEW firmware + boot stack (OTA update capable)
B19-NOUGAT_TWRP (Nougat 7.1.1) – TWRP 3.0.4-1 + B19-NOUGAT boot stack.
B19-NOUGAT_FULL (Nougat 7.1.1) – Complete B19-NOUGAT firmware + boot stack (OTA update capable)

How to Unlock Your Bootloader and SuperSU Root (A2017 + A2017U)

  1. Enable OEM Unlocking. Go to Settings > About Phone > Tap “Build number” 7 times. Then go to Advanced Settings > Developer Options > Enable OEM Unlocking.
  2. Download the SuperSU .zip from above and transfer it to your SD card.
  3. Install the Qualcomm QUSB_Bulk drivers from the download links above. Just extract them, right-click on qcser.inf and Install.
  4. If you do not have an Install option from right-clicking, enter EDL Mode first (Volume Up + Volume Down + Power until you see a black screen)
  5. Select Manual Install, and point to the qcser.inf file. When the driver installation is successful, your PC will recognize the device as COM Port “Qualcomm HS-USB QDLoader 9008”.
  6. Install the MiFlash tool and open it. Select an EDL package for your device.
  7. Boot your device into EDL Mode (if step 3 wasn’t necessary)
  8. Hit the Flash button in MiFlash and wait until the operation is completed. If flashing fails, use Power + Volume Up + Volume Down to restart EDL, and then wait 10 seconds before trying a new flash.
  9. If you chose a package with TWRP included, press Power + Volume Up to exit EDL Mode and boot into recovery. Release Power + Volume Up at the ZTE logo.
  10. Navigate to “Install” in TWRP and flash the SuperSU .zip from your SD card.
  11. When it’s finished, go to Reboot > System and wait for your device to finish all of its operations. SuperSU will reboot your device a few times, just leave it alone until your device boots completely into Android system.

Root Without Unlocking Bootloader

A2017U B20: http://d-h.st/LqR5
A2017U B27: http://d-h.st/kRgq
A2017 B06: http://d-h.st/ztXw
A2017 B07: http://d-h.st/VVlf
A2017 B08: http://d-h.st/bT6r
A2017 B09: http://d-h.st/sBjo
A2017 B10: http://d-h.st/aceq

  1. Download the .zip file for your device from above and extract it on your computer.
  2. Turn off your phone and reboot into EDL Mode (Volume Down + Volume Up + Power).
  3. Connect your phone to your computer via USB.
  4. Install the Qualcomm drivers using the WWAN option during the install process.
  5. Open your computer Device Manager and check which COM port your device is using.
  6. Right-click inside the folder you extracted earlier and choose “Open command window here”.
  7. Type the following commands into the terminal (replace COM# with your device’s port, e.g. COM4):
    exe -p COM# -br –r
  8. Exit the terminal and boot into TWRP recovery.
  9. Format your Data partition in TWRP.
  10. Reboot into the Android system and download pHH SuperUser from Google Play Store.

ZTE Axon 7 Brick Recovery

Warning: This is for A2017U and A2017 models only. A2017G users can convert to A2017U firmware but should not follow these instructions on A2017G firmware.

Follow the same steps for unlocking your bootloader until Step 10. When you enter TWRP recovery, you can flash a stock firmware or backup restore.

Flashing an OTA update .zip may fail in stock recovery, even after you’ve flashed an EDL package. Run this command in TWRP terminal or ADB shell before re-flashing the EDL package:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/system bs=272144

Putting Your Axon 7 Back to Stock

If you want to completely reset your phone back to stock factory (locked bootloader, no root)

  1. Copy all of your personal data from your internal storage and SD card. If you’re rooted but using stock firmware (bootloader not unlocked), skip down to Step 6.
  2. Download the StockSystem .zip for your device version here and place it on your SD card.
  3. Boot into TWRP recovery and perform a System, Data, Dalvik, and Cache wipe.
  4. Flash the StockSystem .zip in TWRP and turn off your phone. This will restore your stock boot, but not your stock recovery.
  5. Download your stock recovery here and flash it in EDL Mode.
  6. Turn off your phone, unplug it from your PC, and boot into stock recovery.
  7. Choose “Wipe Data / Factory Reset”, and then reboot to bootloader when it’s done.
  8. Connect your phone to your PC, open an ADB terminal and enter:
    fastboot oem lock

If everything is done correctly, your phone should be completely factory reset, and you could even accept OTA updates if you wanted. However, be warned that accepting an OTA could in fact lock you into the stock bootloader and prevent you from rooting your phone again.

The post How to Unlock and Root the ZTE Axon 7 appeared first on Appuals.com.

How to Root the Galaxy J5 and J7 2016 Editions

$
0
0

The Samsung Galaxy J5 and J7 2016 editions were released early in 2016, but are still fairly powerful budget devices. This guide offers the Magisk rooting method for the J5, and the SuperSU rooting method for the J7.

Required for Either Device (or pretty much all Samsung device flashing):
Odin Flash Tool

All official stock firmware can be found here. These firmwares can be flashed via Odin in case of boot loop or other disaster, but make sure you grab the firmware for your region.

Root for Galaxy J5 2016

  1. Enable Developer Options and USB debugging. Go to Settings > About Phone > Tap “Build Number” 7 times until Developer Options is activated, then go into Developer Options and enable USB Debugging.
  2. Download 0.2_SM_J510_2016_Recovery.tar and save it on your PC.
  3. Download Odin on your PC and launch it.
  4. Download Magisk flashable .zip and drag the .zip to your phone’s SD card.
  5. Turn off your phone and boot into download mode (Volume Down + Home + Power) while it’s connected to your PC via USB.
  6. Click the AP button in Odin and choose the TWRP .tar file from your desktop, uncheck “Auto-Reboot” in Odin, and click Start.
  7. Wait for Odin to finish (it will say “Success!”), and pull the battery out of your Galaxy J5 for about 10 seconds.
  8. Put the battery back into your device and boot into TWRP recovery (Volume Up + Home + Power).
  9. Navigate to the Install button in TWRP, and choose the Magisk .zip file from your SD card.
  10. Swipe right to flash. When it’s done, wipe dalvik + cache in TWRP, and then reboot.
  11. Open the Magisk app on your phone, and update from the Google Play store when prompted.
  12. Download pHH SuperUser from Google Play Store

Root for Galaxy J7 2016

  1. Enable Developer Options / USB debugging as shown in the steps above for the J5, but also enable OEM Unlocking.
  2. Download these files: TWRP 3.0.2-0-J7Elte and UPDATE-SuperSU-v2.65-20151226141550.zip
  3. Turn off your Galaxy J7 and reboot into Download Mode (Volume Down + Home + Power)
  4. Press Volume Up to continue.
  5. Launch Odin on your PC and connect your phone via USB.
  6. Click the AP button in Odin and choose the TWRP .tar file, then click Start.
  7. When flashing is successful, your phone will boot into recovery. Swipe to allow modifications, then boot into System.
  8. Copy the SuperSU .zip file to your phone’s SD card.
  9. Reboot into TWRP recovery (Volume Up + Home + Power)
  10. Go to “Install”, and choose the SuperSU .zip from your SD card.
  11. When the flashing is complete, wipe your Dalvik + Cache, and then reboot into System.

How to Recover from Boot Loop

If your Galaxy J5 / J7 is experiencing boot loop or other issues with booting into the Android system, the best course of action is usually to simply flash a stock ROM via Odin.

Warning: Flashing a stock ROM will reset your device back to factory settings, and you will lose all of your user data saved on the internal memory. Make a backup of anything you need from internal storage before proceeding.

The post How to Root the Galaxy J5 and J7 2016 Editions appeared first on Appuals.com.

How to Edit the Android Build.Prop with Essential Tweaks

$
0
0

Android devices use a universal build.prop that controls runtime flags when the Android system boots. Many of the properties are unique to each device, but there are a handful of build.prop tweaks that can be applied universally to virtually all Android phones. This guide will show you these tweaks, and how to edit the build.prop file.

Warning: Tweaking your build.prop can brick your Android device. The tweaks I am sharing should work without problem on any Android device, but you should always have a backup of your data and stock ROM just incase something happens.

How to Edit Your Build.Prop

The fastest method is using a root explorer app (which requires a rooted phone) – ES File Explorer, FX, and Root Explorer are great apps. You will need to mount your /system as read/writable in your root explorer options.

Navigate to your /system folder and find build.prop file, then open it with a text editor.

Alternatively, you can download a build.prop tweaker through Google Play store. BuildProp Editor and ROM Toolbox are recommended apps.

The second method which does not require a rooted phone is through recovery mode. Not all manufacturers’ stock recovery modes allow mounting of /system partition, so if this applies to you, search for how to install a custom recovery such as TWRP on your device.

If your stock recovery does allow /system mounting, you just need to connect your device to your PC via USB and open an ADB terminal, then pull your build.prop to your PC using this command:
adb pull /system/build.prop <save path, e.g. C:\MyBuildProp)

Now you can edit the file on your computer with a text editor, then push it back to your phone via ADB with:
adb push <file path> /system/build.prop

After you push the build.prop back to your device, you need to set its permissions. Continue to type the following into ADB terminal:
adb shell
chmod 644 /system/build.prop
adb reboot

Essential Build.Prop Tweaks for All Android Devices

More Efficient RAM Management

ro.HOME_APP_ADJ=1

Improved audio/video recording quality

ro.media.enc.jpeg.quality=100

ro.media.dec.jpeg.memcap=8000000

ro.media.enc.hprof.vid.bps=8000000

ro.media.capture.maxres=8m

ro.media.panorama.defres=3264×1840

ro.media.panorama.frameres=1280×720

ro.camcorder.videoModes=true

ro.media.enc.hprof.vid.fps=65

Less video buffering on streaming services

media.stagefright.enable-player=true

media.stagefright.enable-meta=true

media.stagefright.enable-scan=true

media.stagefright.enable-http=true

media.stagefright.enable-rtsp=true

media.stagefright.enable-record=false

Faster Internet Speeds

net.tcp.buffersize.default=4096,87380,256960, 4096, 16384,256960

net.tcp.buffersize.wifi=4096,87380,256960,409 6,163 84,256960

net.tcp.buffersize.umts=4096,8 7380,256960,4096,163 84,256960

net.tcp.buffersize.gprs=4096,8 7380,256960,4096,163 84,256960

net.tcp.buffersize.edge=4096,8 7380,256960,4096,163 84,256960

Reduced Battery Consumption

ro.mot.eri.losalert.delay=1000 (could brake tethering.)

ro.ril.power_collapse=1

pm.sleep_mode=1

wifi.supplicant_scan_interval=180

ro.mot.eri.losalert.delay=1000

3G Network Tweaks

ro.ril.hep=0

ro.ril.hsxpa=2

ro.ril.gprsclass=12

ro.ril.enable.dtm=1

ro.ril.hsdpa.category=8

ro.ril.enable.a53=1

ro.ril.enable.3g.prefix=1

ro.ril.htcmaskw1.bitmask=4294967295

ro.ril.htcmaskw1=14449

ro.ril.hsupa.category=6

Faster Phone Reboot

ro.config.hw_quickpoweron=true

Change LCD Density

ro.sf.lcd.density=xxx <replace xxx with a numeric value>

Enable VoLTE (Voice over LTE / HD call quality)

#ifdef VENDOR_EDIT
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=0
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=0
#endif

Rotating Launcher and Lock Screen

log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true

Rotating Launcher and Lock Screen

log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true

Audio Enhancements (Music and audio resampling quality, etc)

persist.audio.fluence.mode=endfire
persist.audio.vr.enable=true
persist.audio.handset.mic=digital
af.resampler.quality=255
mpq.audio.decode=true

The post How to Edit the Android Build.Prop with Essential Tweaks appeared first on Appuals.com.

How to Root the Infinix Note 3 Pro

$
0
0

The Infinix Note 3 Pro X601 is a budget-friendly premium Android phone manufactured by Infinix Mobility. This MediaTek chipset phone offers 3gb of RAM, a 16gb ROM, and an impressive 6.0 inch screen with 1080 x 1920 display resolution, and best of all, it’s incredibly easy to root.

This guide will walk you through rooting the Infinix Note 3 Pro X601, but make sure to follow all the steps exactly as described.

Required Files

TWRP_X601-H536-Note3
SP Flash Tool
Mediatek USB Vcom Drivers
SuperSU

Stock ROMs

Optional to download, but worth having incase of disaster (e.g. boot looping device). Make sure you download the correct ROM for your Infinix device, check under Settings > About > Build Number. Flashing an incorrect ROM can lead to device failure! Also note that these ROMs are for the Infinix Note 3 Pro, so their ROMs are noted with X601-H537. The Infinix Note 3 basic version ROMs begin with X601-H536. Also note that in the ROM names, “N” stands for Nougat (Android 7.01) and “M” is for Marshmallow (Android 6.01).

X601-H537A1-N-TEST-170120V48
X601-H537A1-M-161229V106
X601-H537-A1-M-20160715V10

How to Root the Infinix Note 3 Pro X601

  1. We must first install the Mediatek USB drivers on your PC. MTK devices are typically much easier to root compared to other chipsets, but the SP Flash Tool will not recognize any MTK device until the Mediatek drivers are installed on your PC. So begin by extracting the Mediatek drivers to a folder somewhere on your computer.
  2. Mediatek USB drivers are not digitally signed, thus we will disable Driver Signature Enforcement in Windows. Press Windows Key + X and choose “Command Prompt (Admin)” from the menu that opens, then type into the command terminal:
    bcdedit /set testsigning on

The terminal should return “The operation was completed successfully”, so now restart your computer. When it boots back to your desktop, you should see “Test Mode” in the bottom-right corner of your screen.

Note: If your command prompt returned “The value is protected by Secure Boot policy”, then Secure Boot must be disabled in your BIOS settings. Refer to your BIOS manual.

  1. Open Device Manager under Windows – the quickest way is to hold Windows Key + R to open the Run command, and type “devmgmt.msc” and click OK.
  2. Now click on your computer’s name, then click the Action tab, and choose “Add Legacy Hardware”. Click Next in the Hardware Wizard box, then choose “Install the Hardware that I manually select from a list”, and click Next again.
  3. Enable “Show All Devices” before clicking Next, then “Have Disk” > Browse > navigate to your Mediatek drivers folder you extracted earlier. Be very careful which driver you choose to install, you must choose only the driver for your Windows version and system type (e.g. Windows 10 64-bit or Windows 7 32-bit).
  4. Now choose the Mediatek Preloader USB VCOM Port and click Next a couple times, then wait for the driver installation to finish. If an error comes up like “This Device Cannot Start (Code 10)”, just click Ignore and Finish.
  5. Now extract the TWRP recovery to your desktop, and also extract the SP Flash Tool. Run the Flash_Tool.exe with Administrator privileges.
  6. In the SP Flash Tool, click the “Browse” tab and then navigate to your TWRP folder. Select the “scatter.txt” file for your device. Now uncheck all of the options except Recovery.
  7. Enable USB Debugging on your Infinix Note 3 Pro under Settings > Developer Options. If Developer Options is not enabled, go to Settings > About > tap “Build Number” 7 times until it notifies you that Developer Options is now granted.
  8. Turn off your phone, and click the Download button in the SP Flash Tool. Connect your phone to your computer via USB, and the SP Flash Tool will automatically begin installing TWRP. You’ll see a green button in SP Flash Tool when it’s done.
  9. Now transfer the SuperSu.zip file to your phone’s SD card, turn off the device, and boot into TWRP recovery mode (hold Power + Volume Up).
  10. In the main menu of TWRP, choose “Install”, then navigate to your SD card and select the SuperSu.zip file you transferred over. Swipe right to install, and then reboot your device when it’s done. That’s it!

The post How to Root the Infinix Note 3 Pro appeared first on Appuals.com.

How to Root the Asus Zenfone 3 Max (MT6737T Chipset)

$
0
0

The Asus Zenfone Max 3 is a mid-range Android phone released in late 2016. Its features are a 13mp rear camera, 3GB of RAM, and the slick ZenUI interface. This device shipped with two different chipsets – the MT6737T and the MT6737M. This guide is only for the MT6737T chipset version of this device. You can use an app like CPU-Z to see which one you have.

Required Files

SP Flash Tool
Mediatek USB VCom Driver
TWRP 3.0 for Zenfone Max 3 (WW Mediatek version)
TWRP 3.0 for Zenfone Max 3 (EMCC Mediatek version)
SuperSU

Stock ROMs

Optional to download, but recommended to always have a stock ROM in case of device failure.

ZC520TL Firmware

How to Root the Asus Zenfone 3 Max (MT6737T Chipset)

  1. Begin by downloading and extracting the Mediatek USB drivers to somewhere on your computer. These drivers allow the SP Flash Tool to properly communicate with basically all Mediatek chipset devices.
  2. We need to disable Driver Signature Enforcement in Windows, so Press Windows Key + X and choose “Command Prompt (Admin)” from the menu. Now type into the command terminal:
    bcdedit /set testsigning on

The terminal will output “The operation was completed successfully”, so restart your PC. When it boots back to your desktop, you will see a “Test Mode” watermark in the bottom-right corner of your screen.

Note: If your command prompt returned “The value is protected by Secure Boot policy”, then Secure Boot must be disabled in your BIOS settings. Refer to your BIOS manual.

  1. Open Device Manager on your computer – the easiest way is to hold Windows Key + R to open the Run command, and type “devmgmt.msc” and click OK.
  2. Click on your computer’s name, and then click the Action tab, and choose “Add Legacy Hardware”. Click Next in the Hardware Wizard box, then choose “Install the Hardware that I manually select from a list”, and click Next again.
  3. Enable “Show All Devices” before clicking Next, then “Have Disk” > Browse > navigate to your Mediatek drivers folder you extracted earlier. Be very careful which driver you choose to install, you must choose only the driver for your Windows version and system type (e.g. Windows 10 64-bit or Windows 7 32-bit).
  4. Now choose the Mediatek Preloader USB VCOM Port and click Next a couple times, then wait for the driver installation to finish. If an error comes up like “This Device Cannot Start (Code 10)”, just click Ignore and Finish.
  5. Now extract the TWRP recovery to your desktop, and also extract the SP Flash Tool. Run the Flash_Tool.exe with Administrator privileges.
  6. In the SP Flash Tool, click the “Browse” tab and then navigate to your TWRP folder. Select the “scatter.txt” file for your device. Now uncheck all of the options except Recovery.
  7. Enable USB Debugging on your Infinix Note 3 Pro under Settings > Developer Options. If Developer Options is not enabled, go to Settings > About > tap “Build Number” 7 times until it notifies you that Developer Options is now granted.
  8. Turn off your phone, and click the Download button in the SP Flash Tool. Connect your phone to your computer via USB, and the SP Flash Tool will automatically begin installing TWRP. You’ll see a green button in SP Flash Tool when it’s done.
  9. Now transfer the SuperSu.zip file to your phone’s SD card, turn off the device, and boot into TWRP recovery mode (hold Power + Volume Up).
  10. In the main menu of TWRP, choose “Install”, then navigate to your SD card and select the SuperSu.zip file you transferred over. Swipe right to install, and then reboot your device when it’s done.

The post How to Root the Asus Zenfone 3 Max (MT6737T Chipset) appeared first on Appuals.com.

How to Build a Custom ROM from Android Source Project Pt. 2

$
0
0

In our previous “How to Build an Android ROM from AOSP” guide, we went over the basics – setting up Linux, the build environment, and compiling the most basic of Android ROMs. This guide will show you how to add flavor to the ROM by adding a custom boot animation and system themes. Get your gloves on, because things will get messy.

How to Create a Boot Animation

Tools Required:

  • A photo editor that saves in .PNG format (like GIMP or Photoshop)

Assuming you want to create your very own custom boot animation, remember that the image resolution should meet your device’s resolution. So your images should be 720 x 1280 if you have a phone with that resolution, for example. Save them as 32-bit .PNG files. You need to save each frame of your images in corresponding steps:

00001.png
00002.png
00003.png

There is no limit to the number of frames you can have in your boot animation, but the best practice is to use a lesser amount of frames on a loop. CyanogenMod for example uses a looping animation of only a few frames, rather than one long continuous animation.

You need to create two folders on your desktop – name them part0 and part1. If you’re creating something really fancy, you can create more part# folders. This is because the part0 folder will be the animation’s “intro”, and part1 will be the looping frames, and part2 can be the outro, if you decide to do this. So think of it this way: your image fades onto the screen – these frames are saved in part0. Now your image spins around a few times – these frames are saved in part1. Now your image fades out of the screen – these frames are saved in part2. Makes sense, right?

Now what controls how your animation is played is a text file called “desc.txt”. The desc.txt is broken down like this:

720 1280 30
c 1 15 part0
c 0 0 part1
c 1 30 part2

Here is what all of that means:

  • 720 1280 30 = Resolution (width x height) + play at 30 frames-per-second. You can also do 60 or 10 FPS.
  • C means the animation will continue to play fully and not abort, even if the OS is loaded. You can optionally use P instead of C, which will abort the animation and go straight to the OS when its loaded, but this makes for an ugly boot-animation that never plays fully – unless you create an infinitely-looping animation.
  • 1 is the loop count, meaning how many times the frames inside the part# folder will be played before moving to the next folder.
  • 15 is how long each frame will “pause” before going to the next frame. 15 is 0.5 seconds, because 15 is half of 30.
  • Part# is obviously the folder being played.

Basically you want your desc.txt file to read like this:
[type] [loop count] [pause] [path]

Now, create a new .zip archive and name it bootanimation.zip, then drag your desc.txt and part# folders into this archive. If you followed Part 1 of this guide, you will have a WORKING_DIRECTORY on your Linux machine. You need to copy your bootanimation.zip into the following folder:
out/target/product/<product>/system/media

Now the next time your build your ROM, your bootanimation.zip will be the default boot animation for your ROM.

Set the Default Wallpaper

Navigate to this folder:
/frameworks/base/core/res/res/your-resolution

In there you will find a file “default_wallpaper.jpg” – you can replace this with an image of the same resolution and filename, and when you build your ROM, it will be the default wallpaper.

Add ROM Info to Settings > About

Navigate to ./packages/apps/Settings/res/xml/ in your build tree folder.

Now open device_info_settings.xml with GEdit and edit this information to your liking:

<!– ROM name –>

<Preference android:key=”rom_name”

android:enabled=”false”

android:shouldDisableView=”false”

android:title=”ROM name”

android:summary=”Appuals ROM Build Guide ROM”/>

<!– ROM build version –>

<Preference android:key=”rom_number”

android:enabled=”false”

android:shouldDisableView=”false”

android:title=”ROM build number”

android:summary=”7.0.1″/>

Customize the Messenger App

Modifying a pre-existing app is much easier than replacing the core apps, so let’s perform a simple tweak on the default messaging app.

Navigate to ./packages/apps/Messaging/ and open BugleApplication.java with GEdit. We’re going to make a simple toast function, that is, the app will display a pop-up message when the app is opened. So inside the BugleApplication.java file, look for this bit of code:

import android.widget.Toast;

Look for the onCreate() function and just before the Trace.endSection(), add these lines:

Toast myToast = Toast.makeText(getApplicationContext(), “Appuals Rocks!”, Toast.LENGTH_LONG);myToast.show();

Save the file and now the messenger app will display that toast message whenever the app is opened on your ROM!

Edit the Build.Prop File

Navigate to the /build/tools folder in the Android source directory and edit the file buildinfo.sh with a text editor. It basically contains what will be output to the ROM’s build.prop file when the ROM is compiled, for example you will see in buildinfo.sh things like:

echo “ro.build.date.utc=$BUILD_UTC_DATE”
echo “ro.build.type=$TARGET_BUILD_TYPE”
echo “ro.build.user=$USER”
echo “ro.build.host=`hostname`”
echo “ro.build.tags=$BUILD_VERSION_TAGS”
echo “ro.product.model=$PRODUCT_MODEL”
echo “ro.product.brand=$PRODUCT_BRAND”
echo “ro.product.name=$PRODUCT_NAME”
echo “ro.product.device=$TARGET_DEVICE”
echo “ro.product.board=$TARGET_BOOTLOADER_BOARD_NAM E”
echo “ro.product.cpu.abi=$TARGET_CPU_ABI”

Anything you change in here will be copied over to build.prop when you compile the ROM. Read this Appual’s guide “How to Edit The Android Build.Prop with Essential Tweaks” as it will show you a lot of useful things to edit in the buildinfo.sh file.

The post How to Build a Custom ROM from Android Source Project Pt. 2 appeared first on Appuals.com.

How to Root the Motorola Moto G5 and G5 Plus

$
0
0

Motorola introduced its mid-range G5 and G5 Plus phones earlier in 2017, and they are pretty awesome phones for the money. Unfortunately, Motorola locks the bootloaders on nearly all their devices, but savvy Android enthusiasts always find a way.

TWRP has not made an official release yet for this device, so this guide will utilize an unofficial TWRP 3.1.0.0, and root with Magisk instead of SuperSU. Many users confirm this method as working, so this guide will walk you through the necessary steps. Happy rooting!

Required Files:

Motorola USB Drivers for PC
no-verity-opt-encrypt-5.1
Magisk v11.6 | Mirror
TWRP Recovery
Minimal ADB and Fastboot (see “How to Install ADB on Windows”)

How to Unlock the Bootloader for Moto G5 and G5 Plus

Warning: Always remember that unlocking your bootloader will erase your user-data, so back up everything important before we begin.

  1. First we need to enable Developer Options on your phone. Go to Settings > About > tap “Build Number” 7 times. Now go into Developer Options and enable USB Debugging and OEM Unlocking.
  2. Now assuming you have already installed the Motorola USB drivers and ADB on your computer, open an ADB terminal (Shift + Right click inside the ADB folder and “Open Command Window Here”).
  3. Connect your phone to your PC via USB cable, and type into the ADB terminal:
    adb reboot bootloader
  4. Now we need to make sure that ADB can communicate with the phone in fastboot mode, so type into the terminal:
    fastboot devices
  5. You should see your phone’s serial number returned in the terminal prompt. If nothing appears, then try to re-install the USB drivers on your PC. But if your device is shown, type into the terminal:
    fastboot oem get_unlock_data
  6. Now the terminal should display a big string (like the screenshot). Copy the entire string with Right Click > Mark > highlight the string with Shift + mouse dragging to highlight, then copypaste into Notepad.
  7. Now we need to request an unlock key from Motorola. Go to the Motorola unlock request website, sign in with Google or Motorola ID, and paste the string from earlier into the text field. Now click “Can my device be unlocked?”
  8. You’ll get a “Request Unlock Key” button, so check “I Agree” and hit the request button. You will be emailed your unlock key. Once you have the unlock key, go back into the ADB terminal and type:
    fastboot oem unlock xxxxxx
    ^
    Replace xxxxx with your unlock key.
  9. Your bootloader will be unlocked, and your phone will be formatted during the process.

How to Install TWRP on Moto G5 and G5 Plus

  1. Since the phone was formatted during bootloader unlocking process, you need to re-enable USB Debugging and OEM Unlocking from the Developer Options. So remove your phone from your PC and do that, then connect the phone to your PC again.
  2. Reboot the device into bootloader mode once again (remember: “adb reboot bootloader”).
  3. Now assuming you downloaded the TWRP file from above and saved it on your desktop, it’s time to flash it to your phone. Move the TWRP file into your main ADB folder (where you right-clicked and opened the terminal earlier), and type into the terminal:
    fastboot flash recovery xxxxxxx.zip
    ^Replace xxxxx with the filename, e.g. twrp_cedric.zip for G5 and twrp_potter.zip for G5 Plus.
  4. Now, when it’s done flashing, do not reboot your device using the power button. Reboot directly into TWRP recovery using ADB command:
    fastboot boot recovery.img
  5. So once you’re in TWRP, go to the Decrypt/Data screen, hit Cancel, and “Swipe to Allow Modifications” when prompted. Now go to Wipe, and then “Swipe to Factory Reset”.
  6. Now to go TWRP main menu and press Reboot, then reboot to Recovery. Do not install SuperSU if asked.
  7. Your phone will reboot back into TWRP, so now we can begin the rooting process.

How to Root the Moto G5 and G5 Plus

  1. From inside TWRP, go to Mount and choose MTP. Copy the “no-verity-opt-encrypt-5.1.zip” and “Magisk-v11.6.zip” to your phone’s storage.
  2. Now go back to TWRP main menu and choose Install. Select the no-verity-opt-encrypt file and swipe to flash it, then Reboot to System when it’s done.
  3. After your phone is done rebooting, boot it again into TWRP recovery, and flash the Magisk .zip using the same procedure, then reboot into the system once again.
  4. Once you’re in the Android system, open the Magisk app and update it to the latest version when prompted. That’s it!

The post How to Root the Motorola Moto G5 and G5 Plus appeared first on Appuals.com.


How to Build a Custom ROM from Android Open Source Project

$
0
0

If you’re familiar with rooting your Android phone or downloading custom ROMs, such as the highly popular CyanogenMod or its successor Lineage OS, you may have wondered – how do people build these ROMs? How much work exactly goes into developing a customized ROM?

This guide will walk you through the basics of developing your own custom Android ROM. It should be noted that this is a massive undertaking – if you have zero experience in coding or fooling around in Linux terminals, you may want to get some knowledge under your belt before diving into this deep-end. But if you have at least a basic idea of those things, I will try to explain things as simply as possible, so you can follow along.

Basically what we’re doing is downloading the raw Android source code (AOSP) and modifying it to our liking. Because there are so many sources to choose from for different devices, this guide will simply reference the master source known as AOSP (Android Open Source Project).

Now the thing about the AOSP is that the pure source code does not include device-specific hardware proprieties. In layman’s terms, hardware like your camera and GPU will not work “out of the box” when developing with the AOSP. In fact, your device will not even boot without these hardware binaries.

If you’re developing for a Google-branded phone (Pixel, Nexus, etc) you can find the hardware binaries directly from Google, and this guide will walk you through obtaining and building them into your ROM. However, if you’re developing a ROM for a brand-name phone (Sony, Samsung, etc)… well, bless your heart, because you’re in for a ride.

Some manufacturers have their own open-source projects or release development tools for would-be developers, whereas other manufacturers keep a tight lid on their proprietary codes. Here’s a brief list of open-source projects from the more popular manufacturers:

Samsung Open Source Release Center
Sony Developer World
Lenovo Support
Huawei Open Source Release Center
Motorola Developers

With that out of the way, let’s continue under the assumption we are building a ROM for the most basic, vanilla Android experience, for a Google Pixel device. With this knowledge under your belt, you’ll be able to branch out on your own and start developing customized versions of specific manufacturer’s ROMs.

Requirements for this Guide:

  • Android Open Source Project
  • Pixel XL phone or an Android emulator for Linux
  • 64-bit Linux Operating System – Ubuntu or Linux Mint are the most newbie-friendly distros, whereas BBQLinux was developed specifically with Android developers in mind.
  • Python
  • A beefy computer (compiling code takes a lot of memory and space!)

Setting Up Your Build Environment

Let’s begin by setting up the Android emulator on your Linux machine. Whether or not you have a Google Pixel XL device, it’s always safest to try your new ROM on an Android emulator before flashing it to your device. My personal favorite is Genymotion, so I’ll walk you through installing that particular emulator. However, you can also check out this guide “Best Android Emulators for Windows in 2017”, as most of them also have Linux compatibility.

Head over to the Genymotion website, register an account, verify it through email, and download the executable to your Linux desktop.

Now open a Linux terminal, and type:

Chmod +x genymotion-xxxxx.bin (replace xxxx with the version number in the filename)
./genymotion-xxxxxx.bin

Press Y to create the Genymotion directory. Now type in the terminal:

cd genymotion && ./genymotion

Now it will ask you to begin the installation process, so just keep clicking Next until you get to the Add Virtual Devices window. Select “Pixel XL” under Device Model option, and then complete the installation. You can test the virtual device out if you want, it will basically be like having a Pixel XL phone on your desktop.

Let’s now set up Python:

$ apt-get install python

Now we need to setup the Java Development Kit on your Linux machine. Open the Linux terminal and type the following commands:

$ sudo apt-get update
$ sudo apt-get install openjdk-8-jdk

Now you will need to configure the Linux system to allow USB device access. Run the following code in the Linux terminal:

This will download the required 51-android.txt file that allows the aforementioned USB device access. Open the .txt file and modify it to include your Linux username, then place the .txt file in the following location: (as the root user). Now plug your device into your computer via USB for the new rules to automatically take effect.

Downloading the Android Source

The AOSP is hosted on Git, so we’re going to use a tool called Repo to communicate with Git.

First we need to setup a /bin folder in your Home directory. Type the following commands into the Linux terminal:

$ mkdir ~/bin
$ PATH=~/bin:$PATH

Now we will download the Repo tool, so type into the Linux terminal:

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

After Repo is installed, we must now create an empty directory to hold your work files. So type this into the Linux terminal:

$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY

Now we’ll configure Git with your name and email address – use a Gmail address that you check regularly, otherwise you will not be able to use the Gerrit code-review tool.

$ git config –global user.name “Your Name”
$ git config –global user.email
you@gmail.com

Now we’ll tell Repo to pull the latest master manifest of AOSP from Git:

$ repo init -u https://android.googlesource.com/platform/manifest

If done successfully, you’ll receive a message that Repo has been initialized in your working directory. You’ll also find a “.repo” directory inside the client directory. So now we’ll download the Android source tree with:

$ repo sync

Building  the Android Source

This is where the hardware binaries mentioned at the beginning of this guide come into play. Let’s head over to the AOSP drivers page and download the Pixel XL binaries for Android 7.1.0 (NDE63P). You want to download both the vendor image and the hardware components. These come as compressed archives, so extract them to your desktop and run the self-extracting script from the root folder. Choose to install the binaries to the root of the WORKING_DIRECTORY we created earlier.

Now type into your Linux terminal:

$ make clobber
$ source build/envsetup.sh

Now we’ll choose the target to build, so type:

$ lunch aosp_marlin-userdebug
$ setpaths
$ make –j4

There, we have now “built” an Android ROM from source. So let’s test it in the emulator, by typing into the terminal:

$ emulator

So play around in the emulator a bit. As you can see, a purely vanilla Android experience is quite minimal, and this is why manufacturers customize the AOSP to their needs. So you could flash this ROM we just built to your device if you wanted, but without adding any enhancements, a purely vanilla Android experience would be a very boring thing indeed.

So what manufacturers will typically do with the AOSP is fork it, add their own proprietary binaries, customize the UI, add a boot logo, etc. Manufacturer’s basically just paint over the stock Android ROM, and so that will be your next goal as well.

Stay tuned, as the second part of this guide will go through adding fonts, themes, and a boot animation to your ROM!

The post How to Build a Custom ROM from Android Open Source Project appeared first on Appuals.com.

How to Change Android System Font without Apps

$
0
0

Changing the default system font on an Android device should be the easiest thing in the world, yet on many devices it’s actually rather complicated. The issue stems from the fact that stock Android does not offer the ability to customize system font – this is something that some device manufacturers have built into their ROMs. Furthermore, while some device manufacturers (Samsung, HTC, LG, etc) offer a way to easily change font, it’s often through their theme store where you will need to purchase a new font you like.

Android users are likely familiar with the plethora of font apps out there – FontFix and iFont are two such examples. The drawbacks of these apps however is their potential to brick your device – while the developers of both of those apps have made them extremely user-friendly, accidents can happen, usually due to fonts not being given the correct system-permissions after installation.

What we’re going to do is change your system font through ADB, which is a bit more technically involved, but it significantly reduces risk to bricking your device.

Warning: You must only use TrueType font files (they will end in .ttf file extension).

Where to Find Fonts

Most of the font-changing apps pull fonts from online font directories. You can just as easily browse these directories on your PC and download the font files for pushing to your Android phone. Here are some of the best free font directories available:

Google Fonts
Font Squirrel
DaFont
Urban Fonts
1001FreeFonts

Requirements

ADB (see “How to Install ADB on Windows”)
A rooted phone (see Appual’s root guides)
[Optional] Auto Font Unbricker

How to Change Font on Android with ADB

Download the font you want to use to your PC desktop.

Place the font on your phone’s external storage via USB transfer. Rename it to Roboto-Regular.ttf – this is very important, because we need to trick the Android system.

Open an ADB terminal and type the following commands:
adb shell
su
mount –o remount,rw /system
cd /system/fonts

ADB is now inside the fonts directory of your Android device. Now, Android phones typically use Roboto font for the system, with variations of that font for menus, notification bar, etc. They are:

Roboto-Regular.ttf
Roboto-Bold.ttf
Roboto-Italic.ttf
Roboto-BoldItalic.ttf

So what we’re going to do is first replace the Roboto-Regular font, but you can also use this guide for replacing the bold, italic, and bold-italic versions of Roboto with those same versions of your chosen font.

Before continuing, let’s make a backup of the Roboto-Regular font incase something goes wrong. Type into ADB terminal:
mv Roboto-Regular.TTF Roboto-Regular.ttf.bak

Now we’re ready to replace it with your custom font. Type into the ADB terminal:
cp /sdcard/Roboto-Regular.ttf /system/fonts

And now we need to set the file permissions for the font, which is extremely important – this is where a majority of device bricks occur when using font-replacing apps.

Type into the terminal:
chmod 644 Roboto-Regular.ttf
exit

Now power on your Android device – you should see your new font being used for a majority of the system UI, such as the Settings menu, notifications bar, etc.

If Something Goes Wrong:

A lot of novice users panic when their device goes into boot-loop. Recovering from a boot-loop depends on what caused it, and luckily, recovering from a boot-loop caused by font tampering is as simple as restoring the original Roboto font to the Android system. Inside the ADB terminal, type:

Adb devices
su
mount –o remount,rw /system
cd /system/fonts
rm Roboto-Regular.ttf
mv Roboto-Regular.ttf.bak Roboto-Regular.ttf
chmod 644 Roboto-Regular.ttf
exit

Now power on your device, and it should be back to normal. In the rare example where this doesn’t fix a boot-loop after changing your system font, there is a tool available for exactly this problem, called “Auto Font Unbricker”.

Just download the Auto Font Unbricker to your PC, connect your device via USB, launch the program and follow the on-screen instructions.

The post How to Change Android System Font without Apps appeared first on Appuals.com.

How to Bypass SafetyNet Apps with Systemless Root

$
0
0

SafetyNet may add a sense of illusory protection to casual Android users, but it sends frustration through Android enthusiasts. Recent SafetyNet updates have made it so that certain apps such as Netflix, Pokemon GO, and Android Pay will refuse to work on rooted devices. In fact, some apps may even stop showing altogether on the Google Play store.

What happens with SafetyNet protected devices is when you root your device (or modify anything in the /system partition) SafetyNet will send out a red flag in its API to other apps that your device has been modified. These apps then refuse to run on your Android system, or hide themselves altogether on the Play store.

What you’ll need to do is systemlessly root your device using MagiskSU, but there are a few extra hurdles along the way if you’ve been adding modifications to your device for a long time. Short of performing a complete factory reset and/or flashing your device’s stock ROM, you’ll need to un-mod practically everything in your device.

Here is the full guide:

Requirements

TWRP Recovery for your device
Magisk Manager app
Verified Boot Signer

(for Google Nexus devices that received the May 2017 security patches – save to your external SD card)

The first step is to completely unroot your device. So if you’re rooted with SuperSU (the most common root method), you’ll need to head into the SuperSU manager app and tap “Full Unroot”, then agree to your stock boot image being restored. However, do not agree to replacing your recovery image.

You’ll also need to uninstall Xposed if it’s installed on your device, as well as un-modify pretty much anything you’ve done to your /system. This means boot animations, fonts, bloatware removal – if you’ve done a lot of modifications, you might as well flash a stock ROM and start with a completely fresh system.

Once you’ve un-modified your entire device (or flashed a stock ROM), you’re ready to install Magisk. Grab the Magisk Manager app from Google Play, and launch the app. Now click the “Download” button and reboot into TWRP recovery when it’s done.

Inside TWRP, click the Install button and find the Magisk .zip file that was downloaded to your phone. If you own a Google Nexus phone, you’ll need to tap “Add more zips” and choose the VerifiedBootSigner.zip file as well.

Now swipe right to flash the .zip (or .zips) and Reboot System when it’s done.

Once you’re inside your Android system, open the Magisk Manager app and go to the Settings menu. Now enable BusyBox, Magisk Hide, and Systemless hosts.  Go back to the main menu and verify that tapping the SafetyNet button shows “SafetyNet Passed”.

Now we need to clear the data for Google Play on your device – because there is a certification embedded that reports your device was previously rooted / modified. So just go to Settings > Apps > Google Play. Tap “Force Stop”, then go into Storage / Manage Space, and tap “Clear Data”. You should now be able to download and use the SafetyNet protected apps like Netflix and Pokemon Go, and your device is “rooted” in a sense of the word.

From now on you need to avoid installing any apps that modify the /system partition of your device, but luckily Magisk offers many systemless versions of those apps known as Magisk modules. There are modules for Xposed, Viper4Android, Dolby Atmos, Greenify, and many other apps.

Just navigate into Magisk Manager app, click the “Downloads” menu, and download the app of your choice – most of them will download a .zip file to your SD card, and you will then need to flash the .zip in TWRP recovery.

The post How to Bypass SafetyNet Apps with Systemless Root appeared first on Appuals.com.

How to Install a Complete Linux Distro on Android

$
0
0

For users who want to experience a complete desktop OS on their Android phone, especially tech-savvy people who don’t want to carry around a laptop or tablet, it’s entirely possible to install a fully-functional Linux OS on your Android phone.

You will need a rooted phone for this operation – you can search Appuals for a root guide for your device if you aren’t already rooted. Once you’re rooted though, the process is fairly simple.

Requirements

BusyBox
VNC Viewer
Linux Deploy

The first thing you’ll want to do is install BusyBox – either directly from Google Play store, or the Magisk BusyBox module if you’re rooted with MagiskSU.

If you install BusyBox from the Google Play store, you just need to download the app, launch it, and hit the “Install” button from inside the app.

If you’re rooted with MagiskSU, you need to launch Magisk Manager and go to Settings, then enable the “Enable Busybox” button, which will utilize Magisk’s built-in BusyBox for your device.

What BusyBox does is allow your Android system to use Linux commands normally not accessible to you – many root apps depend on this. With BusyBox installed, you’re now going to launch Linux Deploy on your device.

In the Linux Deploy menu, choose “Download”, and then you’ll be presented with an options menu. Here is where you’ll configure your Linux distro before it’s installed, and I’ll explain the important settings:

  • Distribution – Choose your Linux distro to install. There’s quite a large list, but the most user-friendly would be Ubuntu.
  • Distribution suite – Choose a version of the Linux distro you selected above.
  • Architecture – Do not change this, it is automatically selected based on your device.
  • Image size (MB) – The default is 512, but you should change this to a higher available number. Just don’t enter a number greater than 4095mb.
  • SSH Settings – You’ll need to change the default port of 22 here, but Android devices can only use ports about 1024. Most users would opt for port 2222.
  • Custom mounts – If you want to access your Android filesystem from within the Linux distro, go to “Mount points” and choose the ones you need. If you cannot enable the internal storage, change the default storage mount /storage/emulated/0 to /data/media/0.

You should set your username to “root” – this will give you permanent super-user access inside the Linux distro. When everything has been configured, press the Install button, and after it’s finished, you may launch the Linux distro with the Start button – but this will launch it in chroot, which is like a command-line terminal. So we need to access the GUI using the VNC Viewer tool.

Launch VNC and set the address to “localhost:5900” and enter your password. You now have a fully-functioning Linux desktop OS on your Android phone. You may want to begin installing Linux apps, which is done through the Linux terminal. Here are a few worth grabbing:

  • LibreOffice – apt-get install libreoffice
  • Firefox – apt-get install iceweasel
  • Python Idle – apt-get install idle
  • GIMP – apt-get install gimp
  • DropBox – apt-get install nautilus-dropbox

Also check out our guide on installing kali linux on android.

The post How to Install a Complete Linux Distro on Android appeared first on Appuals.com.

How to Completely Theme Android with Xposed Modules

$
0
0

Theming and customizing an Android device can be a disappointing experience with stock apps. Manufacturers’ theme stores often have a limited amount of available themes that change the entire system GUI, whereas you may want to only theme your notifications bar or Settings menu. Creating your own theme from scratch is a massive project that involves decompiling and editing files in the /system partition. So how can an average user completely customize their Android device as painlessly as possible?

The answer is within a combination of dedicated Xposed modules. Xposed is an overlay framework that can enable you to change nearly every aspect of your Android phone with modules (plug-ins), individually. There are even apps to customize and theme specific apps like WhatsApp, Facebook Messenger, and other apps that ordinarily would not allow the user to customize their experience.

This guide will walk you through installing Xposed via systemless root, and show the various modules to achieve maximum customizing potential for your device. Please note that Xposed is currently not available for Nougat, but the developers are working on a release for Nougat support.

Warning: Samsung devices running TouchWiz ROM should not install Xposed, but AOSP-based Samsung devices should be fine.
Some Sony devices may bootloop after installing Xposed due to a number of Sony ROMs being shipped with corrupted services.odex – the Xposed developer is unable to fix this.

Author’s Note: I did not include any modules for changing your system font in this guide, because Appuals has a comprehensive guide on the absolutely best way to change your system font without using any 3rd-party apps or modules. See “How to Change  Android System Font without Apps”.

Installing Xposed – Systemless MagiskSU Root Method (Android 5.1 – 6.0)

Xposed Material Design Installer

These steps assume you are already rooted with Magisk – if not, please search Appuals for an Android root guide for your device.

  • Launch the Magisk Manager and head to the “Downloads” section. Scroll down and install the Xposed Framework module for your device architecture. It will be saved as a .zip file on your SD card (or wherever you’ve set your download path in Magisk).
  • Download the Material Design Xposed Installer APK from the links above onto your device and install the app.
  • Reboot your device into custom recovery and flash the Xposed Framework .zip, then reboot your device.

Installing Xposed Modules for Customizing your Android Device

In the Xposed Installer app, first make sure that Xposed Status has a green checkmark. If so, you may continue.

Go to the “Download” section in Xposed Installer. You’ll be greeted with a huge list of available modules. However, there are a key few that we want for Android customization, and you can search for them from the search bar.

After downloading a module, you will need to head into the “Modules” section of Xposed Installer, tap the checkbox to enable it, and reboot your device. But you can enable or disable multiple modules at the same time before rebooting.

The most useful Xposed modules for Android customization

GravityBox

GravityBox allows you to customize a huge amount of things in your Android device, and in fact it is the most popular Xposed module for this purpose.

It allows you to customize the appearance of your lockscreen, statusbar, navigation bar, and many other useful features, like long-pressing your Volume buttons to skip or rewind music tracks.

Settings Editor

Settings Editor allows you to completely customize your Android Settings menu. You can add or remove icons and sections, change the background color, and change the amount of columns.

XStana

If GravityBox doesn’t offer enough statusbar and navigation button customization for you, XStana allows you to change those icons to ones from other manufacturers, and a few custom ones as well.

KMOD FWA for WhatsApp

This module allows you to customize WhatsApp appearance to your liking. It offers options for backgrounds, fonts, icons, and a direct access button to the module from within WhatsApp itself.

NoOverlayWarning

This isn’t necessarily a theming module, but it’s worth mentioning and highly useful if you are using a lot of theming modules. Often in Android, whenever you try to allow permissions for certain apps (Google Drive for example), you’ll receive a warning that you’ll need to disable screen overlay. You’ll then need to disable all of your app overlays (Facebook talking heads, blue light filters, etc) before you can grant the permissions to the app requesting them.

NoOverlayWarning will allow you to completely bypass this procedure, and thus its incredibly useful for any Android user that uses a lot of overlays in their apps and themes. There are no settings to adjust – you simply install it and forget it!

The post How to Completely Theme Android with Xposed Modules appeared first on Appuals.com.

How to Install Ultimate Performance Mod Engine for Android

$
0
0

Experimental users of rooted Android phones should already be familiar with the plethora of tools to fine-tune your device performance. There’s no shortage of apps or methods to adjust your CPU frequency, build.prop settings, GPU configuration, and numerous other methods of achieving a blazing-fast device.

Of course, it can be annoying to put together the right combination of apps to achieve that performance boost. That’s why more experienced users can turn to scripts – all-in-one packages that will make a variety of changes to your Android system for maximum performance. That’s what the recently updated “Ultimate Performance Mod” (UPM) promises, and it surely delivers.

The UPM itself is a combination of scripts and tweaks by various XDA users, neatly bundled into a single flashable .zip. Normally I’m quite skeptical of anything that promises to make your device run faster, save your battery, etc – for example, there are so many RAM cleaner apps available on Google Play, yet these can actually have a negative impact on your overall performance.

Requirements:

  1. A rooted Android phone (search Appuals for “how to root” guides)
  2. Custom recovery such as TWRP/CarlivTouch/CWM/etc.
  3. Init.d support in your kernel, or Universal Init.D from Google Play
    UPM V13 for Android 5.0 to 7.1
  4. Optional: UPM Uninstaller script (can be flashed in recovery)
  5. Optional: A nandroid backup (seriously, you should always have one)

So what exactly does Ultimate Performance Mod do?

It’s a combination of 4 popular performance engines for Android:

  • Pure Performance X
  • Broadcom Booster
  • Adrenaline Engine
  • Fly-On Mod

UPM’s features include:

  • Full memory management
  • Linux kernel tweaks to improve GUI / CPU performance and battery life
  • Automatic zipalign of apps in /system and /data every 24 hours, and zipalign on boot
  • Offsets the CPU workload to GPU rendering, and automatically scales the CPU frequency as necessary

There’s actually a huge list of features, but I’m writing a guide, not a detailed overview of UPM. If you’re still skeptical, it’s worth noting that the original post on XDA has 973 “thanks” in a thread of 1,215 posts.

So let’s install this thing!

How to Install Ultimate Performance Mod on Android

First you’ll need to check if your kernel has init.d support. The easiest way to check is to download the Universal Init.D app I provided in the Requirements links – simply install it and launch the app, then scroll down and press the “Test” button, reboot your phone, and open the app again.

If your kernel already has init.d support, it will tell you. If not, you can emulate init.d support from inside the app by pressing the On/Off switch at the top and rebooting your phone.

If that feels too simple, you can build init.d support into your kernel – but that’s a bit advanced and requires a guide itself. But if that’s the route you choose, I’ll wait until you come back.

Ready to continue?

Boot into your custom recovery and flash the ultimate_performance_v13.zip from the links above.

Now you can reboot your phone, and if all went well, go ahead and see how much of an impact was made on your performance. Launch your favourite resource-intensive apps, scroll around the web a bit, etc.

If you’d like to see what sort of tweaks were made to your system, you can open your build.prop with a text editor and scroll down to the #By PurePerformance X section to get a small idea of the tweaks made.

I would never write about anything or urge people to install something I haven’t personally researched and tested myself. Let me say, on my integrity as a tech writer, UPM made a huge difference in the overall performance of my phone, which is running 3GB of RAM and an Octa-core Mediatek Helio X20 processor, on Marshmallow 6.0. It’s already a fairly strong device, yet after flashing UPM, my games launch within seconds, scrolling webpages feels buttery smooth, and I’m fairly certain its added a couple hours of battery life in standby mode.

If something goes wrong…

If you run into a bootloop after flashing this script, simply boot into recovery and flash the uninstaller – it should completely remove the script and restore your original boot.prop file. Worst case scenario, flash your nandroid backup.

The post How to Install Ultimate Performance Mod Engine for Android appeared first on Appuals.com.

How to Replace KingoRoot with SuperSU

$
0
0

KingoRoot is well known as the “one click root solution” for Android users, especially those who cannot flash root through custom recovery. KingoRoot is unfortunately a necessary evil for some Android users – and I say evil because KingoRoot has well-known shady practices, such as uploading your IMEI to strange servers in China (taking your IMEI information is completely unnecessary for a rooting app).

Aside from KingoRoot’s shady practices, the KingoRoot SuperUser app is fairly buggy in comparison to the more trusted, stable SuperSU app. Of course, SuperSU depends on being rooted with a SuperSU.zip being flashed in recovery, which most KingoRoot users are unable to do – the good news is that a new method of replacing KingoRoot with SuperSU via scripts has surfaced.

In this guide, I will walk you through replacing KingoRoot with SuperSU on your rooted device. Please note this guide is for KingoRoot, not KingRoot. Don’t get confused.

The advanced method has been tested mainly on ARMv7 devices. ARM64/v8/x86 users proceed with caution.

Requirements

Automatic Method (Easy)

  1. There is a simple method that should work for many Marshmallow devices. If this method does not work, you’ll need to use the advanced method in the next section.
  2. First uninstall KingoUser app, but do not uninstall KingoRoot. Also do not reboot your phone after this step.
  3. Install the SuperSU .apk file that comes in the flashable SuperSU .zip
  4. Launch the SuperSU app and press “continue” then “normal” and wait while it finishes the process.
  5. Reboot your phone and completely uninstall KingoRoot.

Advanced Script Method

Use the CPU-Z app to check your kernel architecture – this is extremely important. Remember what architecture you have.

Download the flashable recovery .zip from SuperSU and extract it to your desktop. You’ll see 9 folders inside, which are:

  • META-INF
  • Common
  • Arm
  • Arm64
  • Arm7
  • Mips
  • Mips64
  • X64
  • X86

Copy the folder for your architecture and the common folder to your SD card, then open a root file explorer on your phone.  We’re going to do a bit of operating on your Android /system, so get your surgical gloves ready and follow my steps extremely carefully.

Navigate to /system/app/ and create a folder called Superuser. Change the folder permissions to 755 (drwxrwxr –x) by long-pressing on the folder you just created.

Now copy the superuser.apk from the common folder you extracted earlier and place it inside /system/app/superuser. Change the .apk permissions to 644 (-rw-rw-r–).

Make sure when you are replacing files, you set the permissions for the files as the same permissions on the old files.

Now reboot your phone, and SuperSU will ask to update the binaries. Choose “Normal” mode and after the update is complete, reboot your phone again. KingoRoot should now be successfully replaced with SuperSU.

The post How to Replace KingoRoot with SuperSU appeared first on Appuals.com.


How to Enable Camera2 API and Shoot RAW on Android

$
0
0

Though Camera2 API was introduced to Android Lollipop in 2015, a majority of phone manufacturers in 2017 have still not implemented the Camera2 API in their cellphones. Only a handful of premium devices have full Camera2 API support, despite the fact that Google has deprecated the legacy Camera API and urged developers to implement Camera2 since its release. It seems like manufacturers are using the features of Camera2 API, like RAW format capturing, as a selling-point for their premium devices, rather than the universal upgrade Google intended it to be.

The bad news is that it’s not possible to simply flash your stock ROM with the Camera2 API – you’d have to rebuild the ROM and add Camera2 API support yourself, or flash a custom ROM with the API built in. The good news is that there are a few tricks to enable Camera2 API if it was left in your ROM but disabled by the manufacturer. There’s also a native way to take RAW format photographs with Mediatek devices. I will show you these tricks below.

What the Heck is RAW Format and Why do I want Camera2 API?

If you’ve stumbled upon this guide and have no idea what RAW format is, it’s basically a lossless image format – think of it like video or music bitrates. You know the difference between 120kbps, 320kbps, and FLAC music files, right? Or watching Youtube videos in 320p vs 1080p? It’s basically the same thing for JPEG vs RAW, sort of.

RAW format will capture photos in completely lossless glory, meaning zero image compression (but much larger file sizes). These RAW images are much better for manipulating in image software – because just like the filetype name implies, they are completely RAW image data. If you compare a JPEG to a straight out of camera RAW photo side-by-side, the JPEG may appear to have brighter colors or other visual enhancements – this is because JPEGs are post-processed by the camera software and built into the image data.

Thus, an un-edited RAW may appear uglier than a JPEG in side-by-side comparison. But for image manipulation enthusiasts, the lack of “post-processing” by camera software is exactly what you need. The post-processing is entirely in your control. This means that RAW photos can be enhanced to a much greater degree than JPEG files, because you’re not fighting against the camera software’s post-processing “magic” applied to JPEG files.

Enable Camera2 API in Build.Prop

Warning: Always create a backup of your build.prop in case something goes wrong.

This method has a 50/50 chance of success, but it’s worth a try. It seems that some manufacturers have Camera2 API built into the ROMs, but disabled it for some reason – by simply adding a line to the build.prop in the /system partition of your Android device, you can enable the Camera2 API functionality.

See also: How to Edit the Android Build.Prop with Essential Tweaks

First you’ll need a rooted phone, and a method of editing your build.prop file. You can either use a root file explorer app (like ES Explorer) to navigate to the /system partition on your phone and open build.prop with a text editor, or you can use a dedicated build.prop editor like JRummy BuildProp Editor.

 

Once you’re inside the build.prop, search for this string:

persist.camera.HAL3.enabled=0

Change the 0 to a 1, save and exit the build.prop, then reboot your phone. If that string it not found in your build.prop, try manually adding persist.camera.HAL3.enabled=1 to the bottom of your build.prop file, save and reboot. You can then test if it worked by launching a third-party camera app like Open Camera or Camera FV-5 and checking in the Settings menu if you can enable Camera2 API mode.

Enable Camera2 API in Terminal Emulator

An alternative method to the above is to try and enable Camera2 API through Terminal Emulator. Simply launch the terminal and type the following commands:

su
su persist.camera.HAL3.enabled 1
exit
exit

Reboot your phone and check if it worked with a third-party camera app like Open Camera or Camera FV-5.

Shoot RAW Photos in Mediatek Engineer Mode

If you have a Mediatek-chipset device, there is a way you can shoot RAW photos even without Camera2 API enabled, via the Engineer Mode. There are a handful of methods to access Engineer Mode:

Open your phone dialer and type this number: *#*#3646633#*#*

Alternatively, you can install an app like MTK Engineering Mode to always have a shortcut icon on your home. You can also install Xposed and the GravityBox module (see: How to Completely Theme Android with Xposed Modules), which will also have a launcher into Engineer Mode.

In any case, once you’re inside Engineer Mode, simply scroll right to Hardware Testing > Camera. This is a testing mode for the camera hardware, but you can enable all kinds of camera options, including RAW format, and take photographs.

When you shoot RAW photos in Engineer Mode, two files will be saved to /DCIM/CameraEM/ directory – A JPEG for previewing the photo, and the actual RAW file, which cannot be previewed on the Android phone. You will need to export the RAW file to your PC and use image-editing software like Adobe Photoshop to manipulate the RAW image, and you may also need to convert it to a universal RAW format rather than what your phone outputs.

The post How to Enable Camera2 API and Shoot RAW on Android appeared first on Appuals.com.

How to Root Oppo F1s

$
0
0

The Oppo F1s Selfie Expert is a mid-range phone marketed to selfie takers. Its main selling point is a 13M selfie camera with face-detection technology and LED flash. Oppo is a Chinese brand that continuously battles for top position with other Chinese manufacturing giants Huawei, Vivo, and Xioami.

In this guide, I will show you how to root the Oppo F1s without a custom recovery or unlocked bootloader for the A1601 firmware. I will also show how to update to the A27 firmware without losing root.

Many people believed the Oppo F1s was impossible to root, because there was a certain glitch in the official KingoRoot method – the root .zip I am providing for A1601 firmware has an altered script that addresses this problem.

Requirements:

  1. Oppo F1s (A1601) Root .zip
  2. Terminal Emulator from Google Play

First you’ll need to install the Terminal Emulator for Android onto your phone. This will allow you to use various Linux-based system commands from inside your phone.

Now extract the .zip I provided above to your desktop PC – inside the folder, you’ll see “KingoRoot.apk” and a folder named “rmkingo”. Copy both of these to your phone’s internal storage via USB.

Open your phone’s Settings > Security and enable “Unknown sources – Allow installation of apps from unknown sources”. Now open a file explorer and find the KingoRoot.apk, then install it.

Inside KingoRoot, press the “One Click Root” button and let it go through the process.

When root is succeeded, launch the terminal emulator and type the following command:
su

Grant Superuser access to terminal when prompted, and continue to type the following commands:
button and let it go through the process.

You might receive an error about infinite loop scripts, just proceed with this guide. Do not close the Terminal emulator or the script, leave them running in the background.

Open the SuperUser app that was installed on your phone by KingoRoot, and press “Remove Root”. This will unroot your phone but leave important files behind so we can achieve a better root method.

Your phone will reboot after being unrooted, so now you can install SuperSU from Google Play. Launch SuperSU app and choose to “Update SU Binary File” in Normal mode, it will go through a process that takes a few minutes. When it’s done, reboot your phone.

Rooted Oppo F1s A16x Firmware Upgrade to A27 Without Losing Root

Requirements:

Flashify
Carliv Image Kitchen
Oppo F1s TWRP 3.0
Sign OTA Package

Official firmware package .zip from Oppo Downloads – www.oppo.com/xx/downloads/ (change the “xx” to your country code, i.e. PH = Philippines, NZ = New Zealand, IN = India, etc)

Note: These steps should only be followed if you rooted the A16x firmware and want to update to A27x without losing your root access.

First you need to flash the modified TWRP image to your Oppo device, using the Flashify tool. Simply install Flashify on your phone, copy the TWRP .zip to your phone’s SD card, and flash it from inside Flashify.

Next we are going to modify the full update package – this is a bit technical, so follow carefully.

Extract the update package .zip to your desktop, and then extract the image file inside.

Delete the file called “recovery-from-boot.p” and use a tool like CarlivImageKitchen to rebuild the image with the option to re-calculate the sha1 value. Write down the new sha1 value.

Open the updater-script with a text editor like Notepad++, and replace the old sha1 value. Repack everything into a new .zip file and sign the .zip with the Sign OTA Package tool provided above.

Copy the update .zip you just made to your phone’s SD card, boot into TWRP recovery, and flash the update .zip. Finally, you can flash SuperSU or Magisk after flashing the firmware upgrade. When you’re all done, reboot your phone.

The post How to Root Oppo F1s appeared first on Appuals.com.

How to Unlock Huawei Modem and Pocket WiFi Devices

$
0
0

Huawei is a leading manufacturer of modems and pocket wifi devices – in fact, your carrier-branded pocket wifi is most likely a Huawei device with your carrier’s logo painted onto it, and locked to your carrier’s SIM cards. You could just buy an open-line Huawei modem directly from Huawei, but if you’ve bought a carrier-locked modem and want to stick your finger at the corporations, read on.

In this guide, I will show you how to unlock your carrier-locked Huawei modem to accept other carrier SIMs.

How to Unlock Huawei Modem / Pocket WiFi Devices

Navigate to your modems homepage (usually by entering an IP address such as 192.168.8.1 into your browser address bar) and go into the Advanced Settings > Device Information. Write down your IMEI number. Alternatively, you can look inside your device, underneath the battery.

Now depending on your device’s IMEI, you’ll need to use one of the below:

  1. For IMEI numbers beginning with 35-, use Huawei Unlock Code Calculator v1
  2. For Imei numbers beginning with 86-, use Huawei Unlock Code Calculator v2
  3. For Huawei routers, use Huawei Unlock Code Calculator v3

Enter your IMEI code into one of the above calculators, press “Calculate”, and copy down the code you receive.

Now turn off your Huawei modem device and insert an “invalid” SIM. Turn it on and go back to the device homepage. Navigate to Advanced Settings > SIM Settings > Unlock Device.

In the box asking for an unlock code, enter the code you received from the unlock calculator, and click “Apply”.

How to Flash Upgrade Huawei Modem Firmware and Dashboard

If you’ve locked yourself out of your Huawei modem by tripping the unlock counter, you’ll first need to reset the unlock counter. So download the Huawei Modem Unlocker and extract it to your desktop.

Run the .exe file from the Huawei Modem Unlocker and connect your Huawei device to your PC via USB. Press the “Refresh” button and your device should automatically be detected.

Enable the checkboxes for “Auto-Calc Code” and “Auto-Unlock Modem”. Now press READ MDM DATA, and then press UNLOCK. Finally, press “Calculate” and write down the flash code you’re given.

Note: If this software does not work for your device, try using the Huawei Flash Code Generator, which will ask for your device’s IMEI.

Next, you’ll need the official firmware for your particular Huawei device. You can normally them on Huawei Firmwares – there are too many available to offer them directly through Appuals. Make sure you download both the firmware update and the dashboard updates.

Unzip the firmware to your desktop, and with your Huawei device connected to your PC, run the .exe file from the firmware folder. Follow the instructions on your screen. You’ll be prompted for a flash code, which you should have from the previous steps of this guide. Some devices may also request a hash code, which can be obtained here.

Finally, and most important, even after you’ve unlocked and flashed your Huawei device, it’s more than likely that the carrier’s dashboard will still prevent you from using another carrier’s SIMs. So you’ll need to flash the dashboard to the generic Huawei dashboard instead of your carrier’s themed version.

Extract the dashboard update .zip you downloaded earlier to your desktop, and follow the same procedure as you did for flashing the firmware update.

That’s it! Your Huawei device should now accept SIM cards from any carrier.

The post How to Unlock Huawei Modem and Pocket WiFi Devices appeared first on Appuals.com.

How to Start Developing Android Apps in Visual Studio 2017

$
0
0

Android enthusiasts, especially programmers, know that there’s no shortage of software to create Android apps – whether it’s Android Studio, tools for creating a hybrid apps like PhoneGap, or the “no coding experience necessary” WYSIWYG app-builders like Tiggzi. Because Android is an open-source, Linux-based OS, some might not realize that Microsoft’s Visual Studio has had Android development support for quite a while – but only now is Microsoft starting to become more vocal about it.

A slew of updates to Visual Studio in just recent weeks has added Linux and Mac compatibility – and Microsoft also launched Xamarin Live, a tool for testing and debugging Android apps without an emulator. This could prove to be a major leap forward for Windows-based Android developers.

Compared to other IDEs (integrated development environment), Visual Studio has its own pros and cons. Visual Studio offers remarkable cross-platform development support for C++ programmers, and being a native Windows IDE, it’s certainly less troublesome for non-Linux enthusiasts to get up and running. The drawbacks would be its over-abundance of GUIDs, and slower debugging compared to other IDEs. But if you’re interested in developing CPU-intensive apps in C++, Visual Studio is an IDE worth its price.

How to Install Visual Studio on Windows

Requirements:

Visual Studio 2017
Xamarin Live [Optional]

Download the Visual Studio installer package and when you launch it, you’ll be asked which components you want to install. For Android development, look under “Workloads” and choose “Mobile development with C++”, then choose “Android development”.

Visual Studio will install the Visual Studio editor, C++ debugger, various Android build tools, compilers, and some other necessary resources. You can also optionally install the Google Android Emulator from inside the Visual Studio installer, but Xamarin Live is worth considering – it’s an app that runs on your Android phone, and can hook into your Visual Studio resources to allow live previewing and debugging of your Visual Studio apps directly on your Android phone.

Android C++ Development with Visual Studio

Launch the Visual Studio editor and navigate to File > New > Project > Visual C++ > Cross Platform > Android. Give your app a name and press “OK”.

 From here you can choose the template you want to work with – there’s a bunch of them to choose, but most graphic-intensive apps will go with the Native-Activity Application (Android) template.

You’ll be presented with the Solutions Explorer menu – there’s two projects available here, which are:

MyAndroidApp.NativeActivity – This contains all the references and glue code you need for running your app as a native Android activity.

MyAndroidApp.Packaging – This contains the AndroidManifest.xml and build.xml, and will package your app into an .apk file for installing on Android devices.

I’m not going to walk you through coding an app, but after you’ve created a project, you can navigate to the Solutions Platform menu and choose the device architecture you’re compiling for, then press F5 to run the app in the emulator you’ve connected to Visual Studio, or send it to Xamarin Live on your device for previewing and debugging there instead.

Editing and Debugging Java Code

If you’re aiming for a Java-based app instead of C++, you’ll need the Visual Studio Java Language Service for Android – this will enable a text-editor that colorizes your Java strings. When you’re done editing your Java code, you can go into the Visual Studio debug menu and choose “Java Only” from the Debug Type menu.

Connecting Xamarin Live to Visual Studio

If you’d rather preview and debug apps directly on your Android phone instead of an emulator, Xamarin Live is for you.

First you need to install the Xamarin Live app from Google Play onto your Android device. Then grab the Xamarin Updater for Visual Studio 2017 and install it on your PC.

Now you’ll need to create your Android app as a Xamarin project, and you’ll be prompted to pair your device via QR barcode on your screen.

When you want to send your app to Xamarin Live for testing on your device, simply choose the “Run” button from inside Visual Studio and choose one of the following options:

Start Without Debugging: This lets you edit the app directly on your device, and the app will be restarted whenever code changes are made and saved.

Start Debugging: This allows you to inspect your app’s variables and breakpoints, but code cannot be edited.

Live Run Current View: Here you can edit the app inside Visual Studio and see the app changes on your computer screen. Basically it streams the Xamarin Live app window to your desktop.

That’s all for this guide! Short of holding your hand and walking you through coding an app, there’s isn’t much more to add. You may be interested in the following Appuals topics though:

How to Create a Basic Android App in Phonegap
How to Build a Custom ROM from Android Open Source Project | Pt. 2

The post How to Start Developing Android Apps in Visual Studio 2017 appeared first on Appuals.com.

How to Add Custom Lockscreen Widgets to Android

$
0
0

Many Android users often wonder how they can add widgets to their lockscreen – this was a feature in Android 4.0, but was removed in Lollipop. Thus, some users download 3rd-party lockscreen apps. This puts the user at a massive security risk, because 3rd-party lockscreen apps are highly unstable and can be easily disabled without any hacking.

The default Android lockscreen is the most secure, yet it does not offer all the “bells and whistles” of a 3rd-party lockscreen – hence we will bend it to our will!

In this guide, I will show you how to add widgets to the stock Android lockscreen, and show you how you can easily create your own customized widgets. Let’s get our hands dirty!

Requirements:

  1. A rooted phone (search Appuals for Android root guides)
  2. Xposed Framework (see “How to Completely Theme Android with Xposed Modules”)
  3. Lock Screen Widgets (Xposed module)
  4. KWGT Kustom Widget Maker (Play Store app)
  5. Some photo-editing skills (PhotoShop, GIMP, etc)

Getting Your Phone Ready

First thing you need to do is install Xposed Framework. The link in the requirements takes you to a guide for installing Xposed using Magisk Manager (systemless root), but the steps may vary depending on your device, so search for an Xposed Framework guide for your device if you’re uncertain.

When you have Xposed running, search the modules for Lock Screen Widgets, or download the module directly from the link above and save it on your phone. Enable it and reboot your phone.

Install KWGT from Play Store and launch it. KWGT is a custom widget maker that runs on your Android phone, it provides many easy-to-use resources and functions for building awesome widgets using a type of “drag-and-drop” interface.

In KWGT, go to the Settings menu. Change them to your liking, but most importantly, you want to change “Preferred Music Player” – I personally use Spotify, and will provide string code for displaying album artwork from Spotify later in this guide.

Now I’m going to walk you through creating a music controller for your lockscreen. It will contain album artwork, artist, song title, and Next / Previous / Play / Pause buttons. See screenshot below of my own custom lockscreen widget created with KWGT.

Launch Xposed and open the Lock Screen Widgets module

These are entirely up to you, but if you want a lockscreen widget that takes up the entire screen, enable the following checkboxes: Hide clock, Hide date, Hide owner, Never show next alarm, Hide the status bar, Update widgets. Press Apply.

Now press the green + icon in the bottom right corner to create a new widget. In the “Choose Widget” menu, scroll down until you see the list of KWGT widget sizes, and choose KWGT 4×4 (it will use the entire screen, but you can choose another size if you want to deviate from this guide).

Now at the bottom of the Lock Screen Widgets app, you will see a gray box that says “Click to Setup or Long Press to Resize” – this is what KWGT widgets always appear as before you customize them. Go ahead and press it. It will take you to the Widget Configuration menu. You’ll see the same gray box, but do not press it here.

Under “Size and Gravity”, change Width to “Match parent” and Height to “Min height”. Then scroll down and enable “Make the widget clickable”. Finally, press the Green checkmark.

Now, turn off your phone’s screen and turn it on again to activate your lockscreen. You should see the same gray box with “Click to Setup or Long Press to Resize” on your lockscreen now, so go ahead and press it and then unlock your screen. As soon as you unlock your screen, it will open the KWGT app for customizing the widget.

Now just for fun, I’ll provide the Appuals logo as the basis of our widget artwork, but ideally you have your own artwork – you can create artwork in software like PhotoShop or GIMP, just remember to save as .PNG for transparency.

Also as an added note, you can use your own custom font in KWGT. Simply place .TTF fonts inside /kustom/fonts/ on your phone’s storage. For artwork, you can put it pretty much anywhere on your phone, for example /Pictures/Kustom_Art/ on your SD card if you wanted.

Inside the KWGT app, you’ll see two widget elements (Items) have automatically been added, two separate text items for time + date. You could delete them, but let’s go ahead and edit them for our purpose. Press the first text item and it will open the Item configuration menu.

Press the first menu item (a-z Text) and it will open a formula editor. Go to “mi” which contains most of the formulas for displaying information about your currently playing music.

Change the formula to the option for “Current Artist”, then go back to the Item configuration menu and edit the text’s appearance to your liking. You can change the font type, size, position, and even use an image as the texture.

Now do this same process for the second text item in the main KWGT screen, but this time under “mi” in the formula options, change it to “Current Track Title”.

PS: If you’re playing music while you’re customizing this widget, it will update itself as you play with the settings, so you can preview the widget’s appearance with different artist + song title lengths to see if your font size exceeds the screen width when the track title is too long, etc.

You can also change the background of the preview window in KWGT, and set it to your desktop wallpaper, or a solid color.

Now let’s add some artwork. Press the + icon in the top right of KWGT, and choose “Image”, then press the new image in the Items menu. Next to “Bitmap”, press “Pick Image” and it will launch your gallery.

I’m going with the Appuals logo, but you can add whatever you want. You can resize it and position it to your liking.

Now, KWGT works like layers in PhotoShop – on the main screen, you can drag layers in front of or behind eachother. So here you can see I have placed the text below the image, so the text appears over the image.

Now let’s add album artwork – the formula for updating album artwork from Spotify is not provided in KWGT, so I am providing it here – however, you can also just use the normal album art formula in KWGT if you use a stock media player, like Google Play Music.

$if(mi(state) = playing & mi(package) = com.spotify.music, mi(cover))$

So add a new Shape item. You can change the shape if you like, but any shape besides square will crop the album artwork.

Now go to the “FX” tab, and change the texture to “Bitmap”. Press the checkbox next to “Bitmap – Pick Image”, and then press the calculator icon in the top right corner. This will allow you to add a formula as the texture for the shape, and so you will add the Spotify formula I provided above, or choose “Current Cover Image” under the “mi” tab if you’re using a stock media player.

Finally, let’s add our buttons for controlling the music. Go ahead and add three new shapes – 2 triangles and a square. Or you can add your own artwork if you’ve designed your own buttons. Edit their appearance to your liking, but go to the “Touch” tab on each one individually. Press the + icon in the top right corner of KWGT, and set the touch actions to Music Controls > Play/Pause, Next, and Previous respectively.

Go ahead and customize whatever else you want, or start entirely from scratch now that you have a basic idea of what to do. But first, let’s see what our widget looks like on the Android lockscreen!

The post How to Add Custom Lockscreen Widgets to Android appeared first on Appuals.com.

Viewing all 342 articles
Browse latest View live