S7 прошивки. Обсуждения. Решения проблем.

zmey2010, а я ща как раз еще один вариант потестирую, ну а потом решим в конце концов че и как надо делать))

Inferno66, ага будет неплохо)

Сюда гляньте

http://forum.onliner.by/viewtopic.php?p=26103569#26103569

скажите что осталось протестировать, вечером поставил лайфовский бут

4aka, да там одна ссыль на пониженную частоту. Я тещу последнюю на основе лайфовской. Пока полет нормальный! Из игр и дельфина не выкидывает, интерфейс не тормозит, в общем я доволен. Прошивка у меня австралия.

4aka, на прошлой странице ссылка, я ж ее и тещу!

4aka, чем попугаев считаешь? Я мерил "квадратом" получилось 646, 654, 659.

Всем привет. Блин подскажите нормальный бут с 998 метрами. я задолбался уже. ставлю 998, опера вылетает, ставлю 768 все работает.

zmey2010, А ты лайфовскую ставил? http://freespace by/download/f426ccbaab

Вот

Main language tool python, two sub-versions of the source file bootimg.py.gz (7.11 KB), and the executable file under windows exe bootimg.exe.gz (2.27 MB), content and usage is entirely consistent.

This is the updated version 2010.11.02.2.

Run method:

In the cmd file is located under the cd to the directory, enter "bootimg.exe function parameters" (in the words of the source file is bootimg.py)

Currently supports the following features:

- Repack-ramdisk, ramdisk generation

- Unpack-ramdisk, ramdisk unlock

- Repack-bootimg, generate bootimg (including boot.img and recovery.img)

- Unpack-bootimg, unlock bootimg

- Unpack-updata, unlock updata.app

- Unpack-yafffs, unlock yafffs (including data.img and system.img)

ps: The following do not understand these parameters, even if it does not matter, we can not add a small u parameter, the direct use of default on the line, as if to unpack updata.app input bootimg - unpack-updata like.

The following parameters in the function of setting them.

- Unpack-updata [file]

[File] is empty, the default UPDATA.APP

Solved, there will be four documents, boot.img, recovery.img, system.img, userdata.img

These are the flashing may need.

- Unpack-bootimg [file]

[File] is empty, the default boot.img

Solved, there will be two files, kernel, and ramdisk.gz

Also, pay attention to output, such as base, cmdline, name, etc.

- Repack-bootimg [base] [cmdline]

[Base] is empty, use the 0x200000

[Cmdline] is empty, use mem = 211 console = null androidboot.hardware = qcom

Generated bootimg, it uses kernel and ramdisk.gz (if ramdisk.cpio.gz, priority), generated boot.img

Updated:

- Repack-bootimg [base] [cmdline] [page_size] [padding_header] [padding_kernel] [padding_ramdisk]

Please note that the specific unpack the parameters of the original parameters of the time.

- Unpack-ramdisk [file] [Contents]

[File] is empty, use ramdisk.gz

[Directory] is empty, use initrd, (please make sure that the directory does not exist)

Output: cpiolist.txt, initrd files in a directory

- Repack-ramdisk [cpiolist]

[Cpiolist] is empty, read cpiolist.txt
According to generate ramdisk.cpio.gz cpiolist.txt
cpiolist.txt format
1). File
file path of the target system target system path to the current system privileges
2). Directory
dir directory path to the directory system permissions system
3). Soft links
slink directory system path to the target system privilege link path

- Unpack-yafffs [file] [Contents]
[File] is empty, use userdata.img (uh, this ratio system.img small)
[Directory] is empty, except use the file. Img outside the other content, such as the use of userdata userdata.img
Note: The directory must not exist
Unlock the file to the directory will continue
Note: windows system does not support soft links and hard links, may report a warning message