> Attention!

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Modifications of software and decorations for ZTE V5



Rep: (252)
Modifications of software and decorations for ZTE V5

Description | Discussion | Firmware | Forum Rules

Rules of conduct in the topic, recommendations on the design of posts. Read a must.

  1. Before making a message with decorations, it is recommended to check whether widgets, icons, live wallpapers, wallpapers, etc. have already been placed on our forum.
    If this is already on the forum, give a link to the profile topic.
    In the case of a replay, the files will be deleted.
  2. If you want to share files that are absent from the forum (Launchers, icons, widgets, programs, wallpapers, live wallpapers, etc.), do this in profile topics and sections.
    In this thread, leave only the link to the file posted.
  3. Offtopic and flood prohibited and punishable!
  4. Widget search is conducted inFinding Themes, Widgets, Wallpapers, etc.
  5. Search programs are conducted inSearch for programs for Android OS
  6. Wallpaper looking inScreen wallpaper


Patterns of modifications and other decorations
Copy the content into your message and fill

Template for modifications:
>> One screenshot, and the rest under the spoiler.
>> For your modifications, put a MOD mark indicating changes
>> When updating the content, reload the file in the existing post, and with the new post we write: "Update: [Theme] Theme. 11/11/1911." (the title should be a link and lead to relevant content)

[CENTER] [SIZE = 3] [B] [COLOR = royalblue] Here we write the name of the mod [/ COLOR] [/ B] [/ SIZE] [/ CENTER]
[CENTER] Insert the main screenshot here [/ CENTER]
[COLOR = blue] [B] Author [/ B] [/ COLOR]: Specify the author
[COLOR = blue] [B] Firmware [/ B] [/ COLOR]: Specify the version / number, code / deodex
[COLOR = blue] [B] Description [/ B] [/ COLOR]: The most complete description of the mod
[SPOILER = Extras. screenshots] If there are additional screenshots, then insert it here [/ SPOILER]
[COLOR = blue] [B] Installation [/ B] [/ COLOR]: Specify the installation method / method
[COLOR = blue] [B] Download [/ B] [/ COLOR]: Attach files to download


Template for other decorations (themes, icons, widgets, programs, etc.):

[CENTER] [SIZE = 3] [B] [COLOR = royalblue] Here we write the name [/ COLOR] [/ B] [/ SIZE] [/ CENTER]
[CENTER] Insert a screenshot here (if any) [/ CENTER]
[COLOR = blue] [b] Posted by: [/ b] [/ COLOR] if there is
[COLOR = blue] [B] Description [/ B] [/ COLOR]: Full description
[COLOR = blue] [B] Download link [/ B] [/ COLOR]: Give a link to download
[COLOR = blue] [B] Installation instructions [/ B] [/ COLOR]: Write the instructions here



Jewelry catalog
Topics

Embellishments

Icons
  • ...
  • ...
  • ...
  • ...

Modifications

Bootanimation

Instructions, useful links


Remember:
Everything you do - you do at your own peril and risk!
The authors of the modifications and the Administration of the forum is not responsible for the performance of your devices!


Be mutually polite! On our forum, it is customary to express gratitude by raising the reputation of a particular participant. If you want to thank the user for the published decoration, clickPicturenext to his reputation. If you do not have 15 helpful posts, ask the moderator to raise the reputation of the person who helped you through the buttonPicture


Post has been editedfil - 25.03.17, 11:07
Reason for editing: Splash screens by rammist



Rep: (204)
* axelvo, * Nyc-2008 * DEMONTER007,
Most applications are identical for all nubia) so modification techniques suitable for everyone, but with ready modes may have problems ..

Post has been editedIvvaNGrigO - 09.01.15, 09:16



Rep: (0)
It is very important, and how to make settings in dark colors?



Rep: (373)
Turning off the signal when switching the volume and turning off the safe volume warning

e.forester
Tested onX9180_1.16_rus , But the manual is suitable for other firmware
Installation via custom rekaveri CWM / TWRP
Ready for PatchX9180_1.16_rus
Attached filemod_framework-res_for_v1.16.zip(8.28 MB)
Manual
Parse "fraemwork-res.apk" and file "framework-res.apk \ res \ values ​​\ bools.xml" change settings "config_safe_media_volume_enabled" and "config_useVolumeKeySounds" to "true" to "false". Putting it. Put in folder "\ system \ framework". Reboot. Profit.


Post has been editede.forester - 15.01.15, 06:53
Reason for editing: manual, registration



Rep: (141)
e.forester @ 14.01.2015, 13:42*
I made a small patch for X9180_1.16_rus.
What is done:
- I turn off the alarm when you change the volume,
- disabled warning about safe listening.
mod_framework-res_for_v1.16.zip (8,28 MB)

and is suitable for 1.15?



Rep: (373)
Jia150 @ 14.01.2015, 19:53*
and is suitable for 1.15?

in a patch modified framework-res.apk. I do not know, it was changed from version 1.15 or not. you can try to sew a patch after making a backup.



Rep: (410)
Porting TWRP recovery

The first thing you need to find the device identical to the one on which we will port rekaveri. I found this Xiaomi Redmi 1S. Often, if the body is identical processors should succeed. Screen resolution Number of RAM, etc. not very important, but the phones are more like the greater the chance that everything will go smoothly.
Next swing rekaveri from off sitehttp://techerrata.com/browse/twrp2/armani(We were lucky to Xiaomi Redmi 1S on off site there are always straight from the tin rekaveri to other devices to look for in the vast inieta.)
Now a little theory. Rekaveri - it's too Suteev core with the same ramdikom but ramdisk set of utilities and binaries rekaveri interface. Should abstain from this that we need to dismantle rekaveri from a similar device to fix ramdisk and fasten our core. Well, sort of task is clear.
All use the same tool as for the disassembly of the nucleussoftware modifications and embellishments for ZTE V5 (Post # 36404731)
And so we assort our core. We assume that sorted out. Directory with the kernel parsed call \ Android Image Kitchen_stok_boot. Everything described heresoftware modifications and embellishments for ZTE V5 (Post # 36404731)(We need it especially for \ split_img - this is our core without a ramdisk.)
Create a new folder with the utility to disassemble and dismantle the core openrecovery-twrp-2.8.4.0-armani.img. Will work as long as strictly to that folder.
Here we have a new folder with the utility
Android Image Kitchen_TWRP_recovery
android_win_tools \
cleanup.bat
repackimg.bat
unpackimg.bat

Next, put it openrecovery-twrp-2.8.4.0-armani.img and rename it boot.img
And understand. All the same as heresoftware modifications and embellishments for ZTE V5 (Post # 36404731)
Now work with the \ ramdisk
Go along the path \ Android Image Kitchen_TWRP_recovery \ ramdisk \ etc \ recovery.fstab here spelled mount points, they can also learn from recovery.fstab only rekaveri for our unit.We will change nothing because Forums Xiaomi Redmi 1S is identical sections ZTE v5.Not exactly the same. Internal Memory s1 - the directory / data / media so the / sdcard mounted / data / media is displayed and section / data size. Therefore recovery.fstab you have to edit.
Here is an example of the edited
recovery.fstab
/ Boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/ System ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/ Data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/ Cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/ Recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/ Emmc vfat /dev/block/platform/msm_sdcc.1/by-name/grow flags = display = "Internal SDcard"; storage; wipeingui
/ External_sd vfat / dev / block / mmcblk1p1 / dev / block / mmcblk1 flags = display = "External SDcard"; storage; wipeingui; removable
/ Usb-otg vfat / dev / block / sda1 / dev / block / sda flags = display = "USB-OTG"; storage; wipeingui; removable
/ Splash emmc /dev/block/platform/msm_sdcc.1/by-name/splash flags = flashimg = 1; backup = 1; display = Splash

/ Efs1 emmc / dev / block / mmcblk0p13 flags = backup = 1; display = OEM
/ Efs2 emmc / dev / block / mmcblk0p14 flags = backup = 1; subpartitionof = / efs1
/ Efs3 emmc / dev / block / mmcblk0p15 flags = backup = 1; subpartitionof = / efs1

/ Modem emmc / dev / block / mmcblk0p1 flags = backup = 1; display = Radio
/ Persist emmc / dev / block / mmcblk0p22 flags = backup = 1; display = Persist
/ Aboot emmc / dev / block / mmcblk0p6 flags = backup = 1; display = Loader
/ Fmwr1 emmc / dev / block / mmcblk0p2 flags = backup = 1; display = Firmware
/ Fmwr2 emmc / dev / block / mmcblk0p4 flags = backup = 1; subpartitionof = / fmwr1
/ Fmwr3 emmc / dev / block / mmcblk0p8 flags = backup = 1; subpartitionof = / fmwr1
/ Fmwr4 emmc / dev / block / mmcblk0p10 flags = backup = 1; subpartitionof = / fmwr1

Here you can see the description of "flags"http: //forum.xda-devel...owthread.php? t = 1943625
C so recovery.fstab be displayed
Internal storage - / data / media (until he could disable)
Intarnal SDcard - Internal memory
External SDcard - SD-Card
You can make backup and restore:
OEM - (sections fsg, modemst1, modemst2)
Radio - (section modem)
Persist - (section persist)
Loader - (section aboot)
Firmware - (sections rpm, sbl1, sdi, tz)
Splash - (section splash)
And it will be possible to flash the image splash.img
Then we go along the path \ Android Image Kitchen_TWRP_recovery \ ramdisk \ res \ here are resources to display TWRP menu. Downloading source TWRPhttps://github.com/Tea...m-Win-Recovery-Projectextract the archive and go along the path \ Team-Win-Recovery-Project-twrp2.7 \ Team-Win-Recovery-Project-twrp2.7 \ gui \ devices \ and seek permission for our system (for example, we need a directory named \ 720x1280 ) and copy the contents of the replacement \ Team-Win-Recovery-Project-twrp2.7 \ Team-Win-Recovery-Project-twrp2.7 \ gui \ devices \ 720x1280 in \ Android Image Kitchen \ ramdisk \ res \. We will change nothing because screen resolution Xiaomi Redmi 1S is identical ZTE v5.
Now edit \ Android Image Kitchen_TWRP_recovery \ ramdisk \ default.prop like this (replace every where there is mention of another unit, in this case, "Xiaomi", "armani", "S1" on the "ZTE", "X9180". Examples take from build.prop)
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id = KTU84P
ro.build.display.id = X9180 4.4.4 KTU84P eng.dees_troy.20150113.055236 test-keys
ro.build.version.incremental = eng.dees_troy.20150113.055236
ro.build.version.sdk = 19
ro.build.version.codename = REL
ro.build.version.release = 4.4.4
ro.build.date = Tue Jan 13 05:53:10 UTC 2015
ro.build.date.utc = 0
ro.build.type = eng
ro.build.user = dees_troy
ro.build.host = ded1.ktechnology.net
ro.build.tags = test-keys
ro.product.brand = ZTE
ro.product.board = MSM8226
ro.product.cpu.abi = armeabi-v7a
ro.product.cpu.abi2 = armeabi
ro.product.manufacturer = ZTE
ro.product.locale.language = en
ro.product.locale.region = US
ro.wifi.channels =
ro.board.platform = msm8226
# ro.build.product is obsolete; use ro.product.device
ro.build.product = X9180
ro.product.model = X9180
ro.product.name = X9180
ro.product.device = X9180
# Do not try to parse ro.build.description or .fingerprint
ro.build.description = X9180 4.4.4 KTU84P eng.dees_troy.20150113.055236 test-keys
ro.build.fingerprint = ZTE / X9180 / X9180: 4.4.4 / KTU84P / eng.dees_troy.20150113.055236: eng / test-keys
ro.build.characteristics = default
ro.omni.device = X9180
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim = true
ro.com.android.dataroaming = true
ro.com.android.dateformat = MM-dd-yyyy
ro.carrier = unknown
ro.ril.hsxpa = 1
ro.ril.gprsclass = 10
ro.adb.qemud = 1
persist.sys.dalvik.vm.lib = libdvm.so
ro.kernel.android.checkjni = 1
net.bt.name = Android
dalvik.vm.stack-trace-file = / data / anr / traces.txt

And finally, we go along the path \ Android Image Kitchen_TWRP_recovery \ ramdisk \ init.rc and correct ven-id and dev-id is to adb driver picked up and displayed correctly in the machine system devices. We have, I have not changed since we are registered with Google aydishniki devices.
write / sys / class / android_usb / android0 / idVendor 18D1
write / sys / class / android_usb / android0 / idProduct 4EE2

With \ ramdisk all.

Now remove from \ Android Image Kitchen_TWRP_recovery directory \ split_img and copy the same directory from \ Android Image Kitchen_stok_boot.
All collected. Again, we turn to postsoftware modifications and embellishments for ZTE V5 (Post # 36404731)
Well, the image-new.img rename it twrp_for_v5.img
Sews in any convenient manner. dd, fastboot or doing the zip file with the patch.

P.S. Get a job working with TWRP 2.8.4.0 mtp as a normal drive mounting. Installed five times the firmware patches are no glitches compared to 2.8.0.0 and 2.8.1.1

To install over rekaveri events
Attached fileTWRP_2.8.4.0_signed.zip(9.61 MB)

Now sets the firmware verification device !!!

I express my gratitude for the promptproDOOMmanandfazergoo

Post has been editedroky_rs - 05.02.15, 17:06
Reason for editing: Corrected spelling errors



Rep: (37)
Bootanimation ZTE Installation of recowery
Attached Image

Attached fileZTE__Bootanimation.zip(4.74 MB)


Post has been editedMidst @ r - 08.02.15, 14:57



Rep: (37)
Integrate the drain in the keyboard firmware Android L (Root is needed)

InstallAttached filecom.google.android.inputmethod.latin.apk(18.08 MB)

We go into the system \ app and drag LatinIME.apk on the memory card
the same operation is performed with the system \ lib \ libjni_latinime.so
All this reserve anywhere in the folder, if you want to return it back (and a backup has not been canceled))
Now we go to the root of the data \ app file system and transfer the file to the com.google.android.inputmetod.latin.apk system \ app
We go to data \ app-lib \ com.google.android.inputmetod.latin and drag libjni-unbundled_latinimegoogle.so in system \ lib
Reboot, go to Settings - Language & input, and set up our new keyboard.
Now it will look like this:
Attached Image



Rep: (37)
Apparent Power off button in the status bar, in addition to thispost # 36798436, Dismantle SystemUI.apk (already modified from AMSUser), we put in res / drawable folder icon with an attached file, there are 2 variants, red and white, and in the files res / layout / msim_status_bar.xml and status_bar.xml do so:

<FrameLayout android: layout_width = "wrap_content" android: layout_height = "fill_parent">
<ImageView android: layout_gravity = "center" android: id = "@ id / battery" android: layout_width = "wrap_content" android: layout_height = "wrap_content" />
<com.android.systemui.statusbar.policy.BatteryLevel android: textAppearance = "@ style / TextAppearance.StatusBar.Battery" android: textSize = "12.0dip" android: textstyle = "bold" android: layout_gravity = "center" android: id = "@ id / battery_level" android: paddingLeft = "1.0dip" android: paddingBottom = "1.0dip" android: layout_width = "wrap_content" android: layout_height = "wrap_content" android: singleLine = "true" />
</ Framelifeout>
</ LinearLayout>
<com.android.systemui.statusbar.policy.Clock android: textAppearance = "@ style / TextAppearance.StatusBar.Clock" android: textSize = "18.0dip" android: gravity = "left | center" android: id = "@ id / clock "android: paddingLeft =" 0dip "android: paddingBottom =" 2.0dip "android: layout_width =" wrap_content "android: layout_height =" fill_parent "android: singleLine =" true "/>
<com.atx.siyang.PowerKey android: id = "@ id / back" android: paddingRight = "0.0dip" android: layout_width = "wrap_content" android: layout_height = "fill_parent" android: src = "@ drawable / ic_sysbar_lock" android : layout_toRightOf = "@ id / recent_apps" android: contentDescription = "@ string / accessibility_back" systemui: keyCode = "26" systemui: keyRepeat = "false" systemui: glowBackground = "@ drawable / ic_sysbar_highlight" androidundefinedrientation = "vertical" />
</ LinearLayout>
</ LinearLayout>
<LinearLayout android: orientation = "horizontal" android: id = "@ id / ticker" android: paddingLeft = "6.0dip" android: animationCache = "false" android: layout_width = "fill_parent" android: layout_height = "fill_parent">
<ImageSwitcher android: id = "@ id / tickerIcon" android: layout_width = "@ dimen / status_bar_icon_size" android: layout_height = "@ dimen / status_bar_icon_size" android: layout_marginRight = "4.0dip">
<com.android.systemui.statusbar.AnimatedImageView android: layout_width = "@ dimen / status_bar_icon_size" android: layout_height = "@ dimen / status_bar_icon_size" android: scaleType = "center" />


We find this place, and copy all of here with a replacement. SystemUI.apk collect and copy it to the system / priv_app, are putting right the letter D (644) and get the result:
Attached Image


button, red and whiteAttached fileicons_power.zip(2.68 KB)

Ready SystemUI.apk (only for drain 116 and mods based on it!)Attached fileSystemUI.apk(4.53 MB)

P.S does not work to make sure that a button was next to the clock, without any gaps, if somebody remake will be quite good.



Rep: (37)
The effect of the old TV when you lock the smartphone.
dismantle framework-res.apk, open res \ values ​​\ bools.xml
I use Notepad +++. We look for the line
<bool name = "config_animateScreenLights">true</ bool>

change as follows:
<bool name = "config_animateScreenLights">false</ bool>

Putting it back and get:
Attached Image

Ready framework-res.apk, suitable for a drain 116 and mods based on it, change to the original, the right to expose the letter D, restart your phone.
Attached fileframework-res.apk(10.82 MB)


Post has been editedMidst @ r - 25.01.15, 14:21



Rep: (150)
Piece of cake theme

Attached Image

author : deadmaus5
Firmware : NubiaUI
Description : Making a theme for your firmware now decided to collect separately, global. It changes all that is shown in the screenshots, in addition to network status and hours in the status bar. Dynamic clock and calendar.
Add. screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image

Installation : Unpack and as a regular subject.
Attached filePoC.zip(37.83 MB)


Post has been editeddeadmaus5 - 25.01.15, 19:43



Rep: (37)
Found on the Xda colored keyboard, I pulled onYandex Disk
In the screenshots folder you choose your favorite keyboard, remember the name, go to the keyboard folder, looking for the title and downloading.
How to install: First freeze \ rename \ delete \ backup native keyboard in the system \ app we called it LatinIME.apk, other models may be another example in its nazvanie.pereimenovyvaem LatinIME.apk1, set the pre-downloaded keyboard (optional transfer it in) and reboot.
Here is a screenshot with the established ShaftaFire:
Attached Image

Additional screenshots:
Attached Image

Attached Image



Rep: (410)
Remove the system update (I still do not use)

Attached Image

First of all remove SystemUpdate_v1.1.apk
then we go along the path \ Settings \ smali \ com \ android \ settings \ DeviceInfoSettings.smali and search method
.method public onCreateView (Landroid / view / LayoutInflater; Landroid / view / ViewGroup; Landroid / os / Bundle;) Landroid / view / View;
.registers 7
.param p1, "inflater" # Landroid / view / LayoutInflater;
.param p2, "container" # Landroid / view / ViewGroup;
.param p3, "savedInstanceState" # Landroid / os / Bundle;

.prologue
.line 235
const v1, 0x7f040047

const / 4 v2, 0x0

invoke-virtual {p1, v1, p2, v2}, Landroid / view / LayoutInflater; ->inflate (ILandroid / view / ViewGroup; Z) Landroid / view / View;

move-result-object v0

.line 236
.local v0, "view": Landroid / view / View;
invoke-direct {p0, v0, p2}, Lcom / android / settings / DeviceInfoSettings; ->initView (Landroid / view / View; Landroid / view / ViewGroup;) Landroid / view / View;

move-result-object v1

return object v1
.end method

And delete it completely.



Rep: (13)
The menu button is also useful for fast system update reboot into bootloader rekaveri and there can make them like that on the menu?



Rep: (410)
warrean @ 30.01.2015, 07:03*
The menu button is also useful for fast system update reboot into bootloader rekaveri and there can make them like that on the menu?

You can, but I do not have enough knowledge in editing smali, so I currently do not do. A climb through the settings to be loaded in or rekaveri fastbut I consider pointless.



Rep: (37)
* warrean

Yuzayte separate program that's pulled and shifted from one Chinese fashion

Attached filereboot.apk(14.45 KB)


Attached Image
Attached Image


Post has been editedMidst @ r - 30.01.15, 21:21



Rep: (1)
* roky_rs, a program to edit?

Post has been editeduhon - 02.02.15, 10:20



Rep: (37)
* uhon,

All infohere



Rep: (5)
Splash red bull

Attached Image

brooklife
Another spleshskrinov phone to download
Attached filesplash.zip(428.57 KB)

on the sd card zip file, go to rekaveri, instal and select the file.

Post has been editedbrooklife - 02.02.15, 17:17



Rep: (4)
whether it is possible to put on a headband one image, and on the lock screen of another, without changing the launcher? searched in the settings are not found


Full version    

Help     rules

Time is now: 18/05/20, 3:19