> Attention!

We strongly recommend to readRules section "Android - firmware"

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



Jiayu G4 - Unofficial firmware (OS 4.4.x)



Rep: (1676)
Jiayu G4 - Unofficial firmware (OS 4.4.x)
PictureJiayu G4 Advanced, JiayuG4 High Edition
Description | Discussion пїЅ | Purchase пїЅ | Official firmware пїЅ | Unofficial firmware (OS 4.2.x) пїЅ | MIUI firmware пїЅ | Unofficial firmware (OS 4.4.x) пїЅ

Important information!
1.Instruction for the transition from 4.2 to 4.4 via FT read here

2.If you show instead of 1GB, 2GB - 512MB, then the solution is alsohere

3. SP Flash Tool errors (under the spoiler. Information on SP Flash Tool errors and solutions found). here
Drivers and Utilities


SP Flash Tool v3.1316.0.150
SP Flash Tool Driver Auto Installer
Dravera for firmware
ADB drivers
SN WriteTool

Mobileuncle MTK Tools - installation of the recovery, the entrance to the engineering menu and much more
MTK Droid Root & Tools - Program for root, backup and create recovery
QtADB - Smartphone control via PC
Firmware
vredniiy mod
Silentntod
LG G3 Edition
HTC One
VibeUI
Emotion ui
Samsung
iOcean x8
ColorOS
Lewa
AOSP Google
CyanogenMod11 B2.6
Paperui
Doogee OS ROM
Slim refresh
Jiayu G5S Stock jiayu.es
Dexp
MERE
Acer Liquid e3 v1
Wind rum
Cyanogen-kat
Freeme os
Maxi Mini
LegenD Rom V11 Android L Edition ART
GidGat в„ў Ultimate ART EDITION
Miui_4.4.2_G4 / G5
Alice project | Overview
YandexKit_for_Jiayu_G4
COLORKAT OS
Port with Lenovo S820 in the style of Sony Xperia Z3
Heve
Android 4.4.2 Beta2
unverified
Recovery
TWRP 3.0.2 Attached Image
TWRP 2.8.5.0with the ability to backup section SEC_RO
dingdong recovery V1.1.0
TWRP 2.8.5.0for firmware throughcustom recovery
TWRP 2.8.4.0
TWRP 2.8.1.0for firmware throughcustom recovery
philz-touch-6.58.9-061114for firmware through custom recoveryStandartandAdvanced
Cannibal Open Touch Recovery
Patches
miscellanea
Instructions
Firmware instructions
Install CWM / TWRP

To enter the CWM / TWRP, you need to hold the volume up, connect the USB cable to the computer or connect to the charging and press the button on - after the Jiayu logo appears, release the buttons


Access to Clockwork Mod Recovery on G4
Installing recovery through the terminal
Installing CWM through the Jiayu app - is recommended
Install CWM / TWRPthroughSPFlashTool(withnotes)
CWM installationthroughMTKDroidTools
Install CWM / TWRPthroughMobileUncleTools(easy and fast)
IMEI
Modifying and Porting

If the auto turn does not work!
How to remove the modem from the firmware
How to find out how much RAM in the device through ADB
THE CONTINUATION OF THE BATTLE WITH A DEEP SLEEP OF IT SAME SLEEP OF DEATH (SOD)
Deep Falling Asleep when idle and Recovering Bricks
Past polls
Attached Image

Attached Image


There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.


Post has been editedsnekt - 26.02.17, 21:54
Reason for editing: SilentMod_2.5 Full dump for Standart



Rep: (630)
Vibe UI 2.0 Port update ver0.1
Changes in the firmware itself
Camera libraries
Sound libraries
Vendor

bugs
1.kataysky labels safely remove
2. does not work in firmware auto brightness
3. reversed in places external memory and internal

Pro core
Work continues

Screenshots
Attached Image
Attached Image

Attached Image
Attached Image

Attached Image
Attached Image

Attached Image
Attached Image


link

Patches

Acknowledgments
a - x93-07 Worked together on the core
vo-1 Prompted a solution to the problem with OTG
and
Rules section "Android - firmware"
3.5. It is forbidden to post links to "Electronic Wallets". In addition to the section Commercial Services.
Profile posting is allowed.


Make backup

Post has been editedsnekt @ - 18.09.14, 07:57
Reason for editing: NFC



Rep: (24)
LG G3 Edition v1.0

KitKat 4.4.2



So I decided to make a port, maybe someone will be interested.
Firmware in the style of LG G3, as for me, it is somewhat similar to Android L

Information:
Core froma - x93-07 (for which he is grateful), taken from beta2 , shoals the same as there :)
Maybe something else will come out, but so far I have not noticed other problems, I will check and update more ...
If something is wrong, do not judge strictly, just learning)


Screenshots:
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image


Download

Post has been editedbenzodm - 14.09.14, 23:25



Rep: (6)
Via the terminal, enter the command:
Su (to get a super user) Then:
To create only the image of the / dev / nvram partition, you can use the command:
dd if = / dev / nvram of = / sdcard / nvram.img bs = 5242880 count = 1d
5242880 is the partition size for devices on platforms 6577-6589. As a result, the nvram.img file will be created on the sdcard path. We keep it in a safe place. This is despite the fact that if imei is not damaged. Then it makes no sense to make an image dev / nvram.img

Through the terminal we enter:
How to restore the erased partition / dev / nvram?
The easiest way to copy the previously saved file to the device’s memory is to type the following command:
dd if = / sdcard / nvram.img of = / dev / nvram
The result of the successful development of the command line will serve
10240 + 0 records in
10240 + 0 records out
5242880 bytes transfered in ... ..

Post has been editedBzzzz3 - 16.09.14, 13:42
Reason for editing: Combined posts.



Rep: (1676)
Why should I move from 4.2 to 4.4 via FT?
First of all, a new markup in which the system, boot and recovery sections are increased. For 4.4, you should use new recovery, which does not always fit into the old markup. In addition, firmware based on my cores are now suitable for both G4 and G5, and this may cause unnecessary problems when flashing from the recovery based on core drain.

How to flash?
There are small differences from the drain during the firmware process, this is due to the fact that I assemble different cores for different batteries in order to minimize the likelihood of a charge failure. + in the archive is two recovery (TWRP and CWM) to taste.
I will not describe the firmware process itself, I think it’s clear to everyone. I will describe only the changes.
  1. Backup NVRAM . How to make it read here
  2. Immediately after downloading the scanner to the Flash tool, you need to select the ones you need.preloader , boot and recovery . To do this, click first on the inscription "PRELOADER" and select, depending on whether you have G4 or G5, then select "BOOT" one of 4 bottles (how to read the type of battery we read here ), and finally on the inscription "RECOVERY" - here there are 2 options for CWM and TWRP, we choose to taste.
    Screenshots
    Attached Image
    Attached Image

  3. Make sure you choose what you need and click Firmware.>upgrade.It is this button that will otherwise get a markup incompatibility error. .
    Screen
    Attached Image

  4. After loading the system on advanced, we format the phone's memory through the settings, and then disable it at all on the standard (Settings->Special abilities).

Immediately after, you can boot into the recovery (vol + and power) and flash another firmware / update from above.

vredniiy mod v4.0.3 FT


Changes
  • New markup (if there is a lot of dissatisfied, then I can redo)
  • Kernels for all batteries
  • Slightly increased the volume of conversational dynamics
  • Date in a curtain in two lines, when pressed, the clock opens and not the time settings.
  • % charge in battery
  • Went through auto brightness, thanks for the help michu.
  • Replaced gaps
  • A small part of the software demolished.
  • Fixed some minor shoals.


Download

Post has been editedvredniiy - 27.01.15, 07:33



Rep: (24)
* a - x93-07,
Ie, if I go with FT, will it be possible to flash large firmware? for example, I installed beta2 and I want to install the full package of gaps to 223mb, and it says to me that there is not enough space



Rep: (1)
I just right away with 3.2.
Through FlashTool you can immediately.
Impressions are very positive.
Testing further



Rep: (13)
* a - x93-07, how to disable the internal drive?



Rep: (1676)
* aniktarov, settings ->special opportunities.

Post has been editeda - x93-07 - 02.01.15, 01:35



Rep: (1428)
a - x93-07 What are the sizes of the boot, recovery and systems in your scatter? I just have a redevelopment, I want to compare with yours.



Rep: (999)
Here is another way to save nvram, boot, uboot, system, userdata, recovery, logo.
http: //forum.china-iph…t1089223.html#p1089223



Rep: (1676)
why even move from 4.2 to 4.4

If you ask this question, then I do not think that you need it. Although it is right!
For me personally, + this is more correct operation of bluetooth (I haven’t really checked it yet) and access to applications for the notification shutter + API enhancement that gives access to some previously unavailable applications (few people will notice) I really did not have enough of this on 4.2. Well, as a developer + is that almost all the firmware in the source code.

Posted 09/17/2014 10:12:

I want to compare with yours.

Difficult to open, since you want to compare like that? ~ 16 MB. The point is that this size is registered not only in the markup, but also in UBOOT. Byte to byte.

Post has been editeda - x93-07 - 17.09.14, 10:19



Rep: (1)
Auto-brightness works, but as it is very sharply changes the brightness and dark, goes to look closely .... turned off ...........

Post has been editedNiknaimen - 17.09.14, 11:18



Rep: (746)
Question - according to the scatter, the internal memory is 4GB, after installation, respectively. Internal memory 1.4GB - after formatting on advanced becomes 25.
So - what about the markup itself and the PMT file?



Rep: (1676)
* michfood, But did not notice that the drain is also on the scanner 4 and pmt does not lie? Or on g5 otherwise?

Post has been editeda - x93-07 - 17.09.14, 11:06



Rep: (364)
Mod 4.0.3 can I sew with 2.6.3 right away? Or first beta2?
Anticipating the remaining questions - is it possible with MIUI, LeWa, etc. - VM 4.0.3 firmware for FT is complete, i.e. contains images for ALL the partitions to be flashed and has its own body memory markup. You can sew withany current firmware with any markup. And even raise a brick.

I made NVRAM backup, I can use the Flash tool, the only thing that worries me is how to get it back if I don’t like it? I now have vredniy mod v 2.6.3 + carliv touch recovery + I also did redevelopment, so that under the proposals there would be 4.9 GB (I don’t remember which way).
* teenpsb, Before flashing you can do the following:
1.1. Save current markup (MBR, EBR1, EBR2, PMT, scatter).
1.2. Make nandroid backup from recovery, including sections nvram, uboot, logo, sec_ro (I don’t remember anymore, but I didn’t add sec_ro backup to CTR)
1.3. Save on the BB data from the internal flash drive (if any)

If redevelopment was done only for USRDATA, then for rollback to VM 2.6.3
2.1. you sew through the October October FT, replacing the markup files from section 1.1 (MBR, EBR1, EBR2, scatter) and recovery.img from section 1.2 or the one from which you set yourself CTR.
2.2. Loads in recovery, format / data and / emmc
2.3. You recover in recovery from backup (p. 1.2.)
2.4. Pouring data from the BB to the internal USB flash drive (if any)

A - x93-07, what are the sizes of boot, recovery and systems in your scatter? I just have a redevelopment, I want to compare with yours.
For everyone who is interested in markup in VM 4.0.3 and too lazy to download all the firmware
Memory Markup in VM 4.0.3
Attached Image

root @ JY-G4 \ G5: / # cat / proc / dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000600000 0x000000000000000000 2 / dev / misc-sd
mbr 0x0000000000080000 0x000000000000000000 2 / dev / block / mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 / dev / block / mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 / dev / block / mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 / dev / block / mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 / dev / block / mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 / dev / block / mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 / dev / block / mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 / dev / block / mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 / dev / block / mmcblk0
bootimg 0x0000000001000000 0x0000000002180000 2 / dev / block / mmcblk0
recovery 0x0000000001000000 0x0000000003180000 2 / dev / block / mmcblk0
sec_ro 0x0000000000600000 0x0000000004180000 2 / dev / block / mmcblk0p4
misc 0x0000000000080000 0x0000000004780000 2 / dev / block / mmcblk0
logo 0x0000000000300000 0x0000000004800000 2 / dev / block / mmcblk0
ebr2 0x0000000000080000 0x0000000004b00000 2 / dev / block / mmcblk0
expdb 0x0000000000a00000 0x0000000004b80000 2 / dev / block / mmcblk0
android 0x0000000048000000 0x0000000005580000 2 / dev / block / mmcblk0p5
cache 0x0000000007e00000 0x000000004d580000 2 / dev / block / mmcblk0p6
usrdata 0x0000000081e00000 0x0000000055380000 2 / dev / block / mmcblk0p7
fat 0x000000066f980000 0x00000000d7180000 2 / dev / block / mmcblk0p8
bmtpool 0x0000000000000000 0x00000000ff9f00a8 2 / dev / block / mmcblk0
Part_Name: Partition name you should open;
Size: size of partition
StartAddr: Start Address of partition;
Type: Type of partition (MTD = 1, EMMC = 2)
MapTo: actual device you operate


Post has been editedlion567 - 17.09.14, 13:15



Rep: (861)
Another way to piggy bankBackup NVRAM .
2 batch file - one backup, 2nd - restores.
ZY For those who have problems with the terminal.



Rep: (345)
Is it not easier to backup NVRAM in recovery?
TWRP does it. I made a separate backup nvram there.



Rep: (861)
* zmeeus
It is better to save in several ways.



Rep: (0)
* a - x93-07
After installing 4.0.3:
1. Titanium has stopped restoring backups - just hangs a window with 0% progress
2. When creating a backup, it writes - not enough space

Plz tell me what can be cant

P.S. Internal memory formatted



Rep: (5)
there is only a couple of problems
1. Does not restore TitaniumBackUP
2. Does not patch Lucky Patcher writes:
SU Java-Code Running!
com.chelpus.root.utils.custompath
Custom patch not found. It's a problem with root. Dont have access to SD card from root.
Please update SuperSU and update binary file su from SuperSU.

SuperSu installed checked access there
what a garbage I do not understand ....

Post has been editedLifan777 - 17.09.14, 15:09


Full version    

Help     rules

Now: 07/10/19, 19:20