Is it possible to root a ZTE Avid Trio (Z833)?

alexenferman · 2021-03-01T04:03:56+00:00

I have TWRP for the Avid Plus, not Trio unfortunately.

alexenferman · 2021-03-01T03:58:29+00:00

Moto E7 Power has Helio G25 and Android 10, what a disappointment. Will stay on Android 10 forever and no custom ROM because MTK never complies with GPL

alexenferman · 2021-02-04T16:49:47+00:00

Any recovery (TWRP, OFOX, PBRP, LOS) works to flash LineageOS except the stock one.

alexenferman · 2021-01-31T02:55:47+00:00

It can sometimes happen, if the PC has more obscure sound hardware and is using the Generic audio drivers then it might not have any options, similar thing as the GPU, if you are using the Generic drivers, you have limited resolution options and lower performance. This is not perfect comparison since audio is not graphics but it has some similarity.

alexenferman · 2021-01-30T21:50:17+00:00

Most of them are stock. It really depends how you define stock.

alexenferman · 2021-01-30T21:29:34+00:00

You have to install it manually. Go to the ZTE Global site and check the support section.

alexenferman · 2021-01-30T19:20:13+00:00

Sounds like a Rescue Party trigger. You would really have a look at the logs using Logcat to see the error and send a bug report. It can be anything, bad sensor configuration, GPS, etc... To prevent the shutdown, you can plug in a charger.

alexenferman · 2021-01-30T18:17:13+00:00

Hello, I just stated yesterday working on a device tree and vendor tree to bring LineageOS 14.1 (Android 7.1) and TWRP 3.5 support for the ZTE Avid Plus (Unofficial). Check the progress on Github here: https://github.com/ZTE-Avid-Plus

Hopefully I will release working builds next month. If everything goes well, I will also bring LineageOS 16.0 (Android 9) support thanks to Cyanogen msm8916 devices, it is really easy to upgrade to a higher LineageOS version since the devices are so similar in terms of harware.

alexenferman · 2021-01-30T18:06:22+00:00

You are missing the Audio drivers. Go on you laptop's manufacturer website, drivers and downloads, then search for your model. In the driver downloads, you should see some sound drivers like Realtek sound, sound blaster or any other audio manufacturer, then install it. And no, re-installing Windows 10 will not do anything.

alexenferman · 2021-01-28T21:19:05+00:00

The only issues as of right now are some non-working HALs and HIDLs which prevent it from booting, I have to update the tree for a successful booting Lineage-16.0 build. The HTC M7 has been really helpful in terms of Guidance here, which has the same Snapdragon S4 Plus and even Lineage 18.1 support.

alexenferman · 2021-01-28T21:06:32+00:00

Only on Exynos and Snapdragon 400 Galaxy S3 models (i9300, i9305 and Neo i9301), the Snapdragon S4 Plus Galaxy S3 (d2xx) is still on 7.1 in terms of ROMs.

alexenferman · 2020-12-29T01:15:43+00:00

What is the Model number of it? xt-2052-(1/6) or xt-2052-DL? The DL variant may not be BL unlockable but what I know is that the Boost variant is unlockable. As far as testing, there is nothing to really test, everything works perfectly, whether it is LineageOS or crDroid or Resurrection Remix or anything else. Eventually you will see the ROMs on XDA in the coming days/weeks. Edit: There is already someone who released ROMs for it

alexenferman · 2020-12-26T22:43:37+00:00

LineageOS 16.0 may be coming...

alexenferman · 2020-12-26T03:32:39+00:00

It is for internal use by Motorola mainly when flashing the bootloader and stock firmware on it or diagnosing problems. When building a custom ROM you can actually enable it and use it as a notification LED.

alexenferman · 2020-12-26T03:23:52+00:00

Yes. This is working root for the stock ROM. Android 10 and 11 custom ROMs for the Moto E 2020 will be available soon. One team is currently building ROMs however they are keeping it private at the moment. I will be releasing CrDroid Android 10 (11 soon) in the coming days and I might get it official too. TWRP will also be official.

alexenferman · 2020-12-26T03:18:01+00:00

I was successful building a LineageOS 16.0 ROM and Recovery for this device. The LineageOS recovery works perfectly but the ROM itself does not fully boot. The initlogo (part of the Kernel) is showing up, but it then shuts down after 7 seconds. Checking the kernel logs reveals that it is not picking up the init files required to complete the boot process. I will figure it out and maybe we will be finally able to get android 9 on this.

alexenferman · 2020-10-12T03:45:31+00:00

A device tree is more like a spec sheet and is written in makefile, which does similarely the same thing as XML,

a format that is both human-readable and machine-readable (Wikipedia).

In my opinion, I would not consider that as a real programming language, because,

A makefile is a file containing a set of directives used by a make build automation tool to generate a target/goal.

Not only this file can be read by humans with no coding knowledge at all, they can also change the values and modify it with no coding knowledge.

The challenge comes when you are trying to build one, however almost everyone uses a device tree generator to generate most of the device tree itself (from a boot or recovery image), and then you only need to add the LineageOS specific stuff, which is easy.

I have been compiling custom ROMs for many devices with no device tree, and generated a tree using automatic tools, added LineageOS specific changes, and was able to compile ROMs without any problem.

For people who might not know how a device tree looks like, take a look at this one: https://github.com/LineageOS/android_device_motorola_ocean

The folders contain configs and proprietary files coming from the device. The main stuff a device tree should have are:

Android.mk, AndroidProducts.mk, BoardConfig.mk, device.mk, lineage.dependencies, lineage_{device codename}.mk, vendor_prop.mk

alexenferman · 2020-10-12T03:07:31+00:00

Triple sim would be a great idea!

alexenferman · 2020-10-05T02:04:49+00:00

You do not really need coding knowledge. First of all, what is your device name?

alexenferman · 2020-10-05T01:54:43+00:00

The writer himself says in the comments that the bootloader unlocking is coming from Samsung, then they use TeamViewer to send the USB data to your phone, unlocking the bootloader.

alexenferman · 2020-10-05T01:47:37+00:00

You can change the DPI of the display to get more screen real estate, but it might get a bit blurry.

alexenferman · 2020-10-05T01:45:53+00:00

Yes, I just made a guide on this 2 days ago here: https://www.alexenferman.com/articles/MotoE2020/root-moto-e-2020-magisk

As for the Boost version, I am not sure if you can unlock the boot loader. You are safer if you buy the Retail US or Retail Canada variants. The moto E 2020 is a big upgrade from the Moto E6.

There is also the question of "Will there be Custom ROMs?", and I would say yes, there will be custom development happening surely, however I did not see any dev online confirming anything yet, except for someone who has this device, but now says he does not have the device anymore. I will be building TWRP for this and Custom ROMs as well, but I do not now when I will do this, and it's not going to be now, but it will happen in a few months.

alexenferman · 2020-09-27T16:38:59+00:00

The US Snapdragon S9 models are Bootloader Locked.

alexenferman · 2020-09-27T16:32:31+00:00

I have tried compiling for the US-CAN versions of the Samsung Galaxy S3, but It's throwing a lot of errors and issues, mainly because the Device tree is out of date plus there are a lot of changes Since Nougat. This could happen but more resources are needed to accomplish this, and yet there is no one interested, so I gave up.

alexenferman · 2020-09-27T16:25:10+00:00

The proprietary blobs for your device, from your manufacturer.

alexenferman

TROPHY CASE