[X]Assistant

[morerator-bot]

Lenovo Vibe B - Development and porting of cores and firmware
A2016a40, al732row
Description | Discussion пїЅ | Firmware пїЅ | Kernels пїЅ

Drivers and Utilities

Drivers for connecting the phone to the PC
FlashTool to install firmware
FlashTool Drivers

Instructions

пїЅ Driver Installation Instructions
пїЅ How to add SWAP / Z-Ram to the core
пїЅ How to add your LMK value to boot
пїЅ How to disable forced encryption in the boot

Kernels

Sources

пїЅ Device tree
пїЅ Official stock kernel sources from the official site
пїЅ Sources of stock kernel on GDrive

miscellanea

••• FIXES AND PATCHES
пїЅ Fix sound volume

For questions about filling caps, please contactskittels15in QMS.

Post has been editedskittels15 - 05.03.19, 00:12

Reason for editing: Kernel sources

[Skyrimus]

sunk851,device is a tree for building firmware from sources ... Custom, but not stock, Ito has nothing in this archive in device ...

Post has been editedSkyrimus - 07.03.19, 23:18

[sunk851]

Skyrimus, and I did not say about the stock)

[Skyrimus]

Where is the progress? I already hachu install Androed 30 !!! :)

[San4es7724]

Skyrimusi'm toz

[San4es7724]

Why no news?

[morerator-bot]

San4es7724because this phone is obsolete: D

[San4es7724]

morerator-botno reason

[morerator-bot]

San4es7724... and nobody does it. Those who were engaged in firmware have already changed (and maybe more than once) phones.

Nobody will collect anything further than the outdated nougat.

Post has been editedmorerator-bot - 10.04.19, 20:44

[San4es7724]

morerator-bot, So what. Not so ancient.

Attached images

[morerator-bot]

San4es7724All claims to lenovo. They do not comply with the requirement of Google to update the firmware. And in general, they (lenovo) already produce moto (formerly Motorola), but lenovs no longer produce and will not be updated and are not going to. Accordingly, there are no new sources on which you can normally assemble the firmware without dancing with a tambourine.

And the original source curves, if that. And the phone itself is not interesting to anyone in terms of development. On my current phone, firmwares are actively being released and updated, and officially (well, not officially, but fromsource codes), and not self-made ports ports and port ports. And the source is constantly updated and fixed. And the vibe has no changes since 2016. And on the githaba, I have not seen a single official repository for the vibe.

And lenovo threw garbage on the site and are not going to fix bugs, citing the fact that "who needs to be fixed"(as they like to say on 4pda)

P. S. By the standards of the modern mobile market, three years is already outdated.

Post has been editedmorerator-bot - 10.04.19, 20:57

[Skyrimus]

morerator-bot,so yes, I agree, but you can breathe new life into any old model, for example TCL 5015D or TCL 5010D, it was worth doing and now, they are back in service and in demand, although the 2015 models :) There is still interest, how the opportunity to install the Treble firmware was opened, and this is essentially the official support from Google and fellow phhusson and a bunch of other Treble developers, and this is the last thing that can be done for any phone model, and the latter in the sense of more cannot be done )

[morerator-bot]

Skyrimus @ 04/10/19, 10:00 PM

Treble firmware, and this is in fact the official support from Google

Custom does not google. And ordinary people

Posted 10/04/2019 22:12:

Skyrimus @ 04/10/19, 10:00 PM

for any phone model

but not vibe

And 32-bit firmware without a vendor is almost absent in the subject line. And if it were possible to implement this chip on the vibe, most functions simply will not work

Post has been editedmorerator-bot - 10.04.19, 22:14

[Skyrimus]

morerator-bot,Treble then Google came up with: D A custom on the Treble can even collect a child, and even more so, and what's the problem to have a vendor? There are ALPS sources, there are basic drivers and info on the phone, yes, no one can do this, but it is realizable

[Skyrimus]

morerator-bot @ 04/10/19, 22:12

most functions just won't work

Where such confidence? For example, in my topic Sparks also trumpeted that the x32 core and firmware could not be implemented and that many tried, but nothing worked, but it turned out :) All functions depend on the core and system part, in general, the mtashny vendor is universal a number of processor models, in the source code of the vendor of edits at least - cameras, sound, codecs, the rest at the kernel level

[morerator-bot]

Skyrimus @ 04/10/19, 22:28

nobody will do it

Here is the answer to the question of why there is no custom

Skyrimus @ 04/10/19, 10:35

cameras

On the month of vibe, the camera could not start

Skyrimus @ 04/10/19, 10:35

sound

So far, the sound on BT does not work without fixation

Skyrimus @ 04/10/19, 10:35

kernel dependent

which is no newer stock

Post has been editedmorerator-bot - 10.04.19, 22:38

[grisha2002]

morerator-bot @ 04/10/19, 20:48

original source curves

Who said ?

Attached images

[Skyrimus]

morerator-bot @ 04/10/19, 22:36

On the month of vibe, the camera could not start

It's one thing to start on ports from 6735 to 6735m, yes, it is almost unreal, since the implementation of cameras and the support of api cameras for these processors are different, in fact, like the challahs in the system and editing in frameworks, but when building from ALPS sources, the situation is completely different , it is possible to assemble a vendor under your platform, reflow stock challah cameras and use it during assembly and voila, profit

[morerator-bot]

grisha2002In the conversation, I followed all the source code manipulations. One lantern week wound up: D

[Skyrimus]

morerator-bot @ 04/10/19, 22:36

BT sound does not work without fix

The fix is ​​to edit a single file, just then: D

[grisha2002]

morerator-bot, then the question is, why write about the kernel, if there is 3.18.19 custom (not curved)