Related
hii
i am new to this world of upgrading and flashing . i rooted my samsung galaxy grand i 9082 yesterday and seeking to upgrade it to kitkat 4.4.2 .. I read some in the forums about some stability issue and also dual sim feature will no longer be avalable. please tell me are these true.
please guide me step by step how to upgrade and solve the issues. i really dont know what is cm11 ,what is cynogem mod.. please spoon feed me or provide a link for the same.
regards
CM 11 = CyanogenMod..
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
Features supported by CyanogenMod include native theming support, FLAC audio codec support, a large Access Point Name list, an OpenVPN client, an enhanced reboot menu, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and other performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as wi-fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. CyanogenMod does not contain spyware or bloatware. In many cases, CyanogenMod may increase performance and reliability compared with official firmware releases.
CyanogenMod is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code.
Source: CyanogenMod Wiki
Click to expand...
Click to collapse
Please tell me how to get a 4.4.2 version. And also please tell how to take a backup of my original firmware if I wish to rollback to original firmware in case
Regards
Sent from my GT-I9082 using XDA Free mobile app
umang2792 said:
hii
i am new to this world of upgrading and flashing . i rooted my samsung galaxy grand i 9082 yesterday and seeking to upgrade it to kitkat 4.4.2 .. I read some in the forums about some stability issue and also dual sim feature will no longer be avalable. please tell me are these true.
please guide me step by step how to upgrade and solve the issues. i really dont know what is cm11 ,what is cynogem mod.. please spoon feed me or provide a link for the same.
regards
Click to expand...
Click to collapse
You should better read/ask in your phone's section.
Here is a short preview of the "advanced" android world :
- In order to backup your phone data you need a recovery.
- The most known recoveries are CWM and TWRP (in most phones you get into recovery pressing power and volume buttons while the phone is off).
- From the recoveries you can install a new ROM (firmware) to your phone, make a backup/restore or flash zip files (that run commands and move files)
- Cyanogenmod / Cm is a famous ROM with different versions for many phones. Cm11 is the Cyanogenmod kitkat version (10 jellybean, 9 icecream etc)
I hope you got the main idea
Sorry I am not getting the backup and restore option in my cwm as it shows in the videos
Welcome.
Very short about me: Most of you know me as ieatgravity, I ported TWRP Recovery a little less than a year ago and was able to achieve root on the Life One X2. Since then I have developed guides, auto rooting tools, roms, and I maintain BLOX2.com a dedicated site for all Life One X2 and Mini Development. I apologize for the long absence. However it seems as if this community has really bloomed from where I left off. I want to thank EVERYONE who has supported this development for our phone over the last year, whether it be financially, simple encouragement, thanks, prayers, or you even helping develop something new. I tried my best to credit everyone involved, though many have come and gone we hope YOU will take an interest and try your hand at developing!
As of now we have all been using the first thread we had for our device as a catch all for development, apps, support, general q&a's. Though it has worked for us up until now, a few of us have decided that we should have a dedicated thread to development ideas, topics and questions to keep everything organized.
For now this thread will support both the X2 & Mini. So when you post, please specify the device.
Table of contents:
List of current development to date
Great "How To's" and Guides
With all of that said, here is a consolidated list of all development to this date. If you don't see something on here please let me know and I will update it.
Roms
X2:
Stock - ieatgravity
Blox2core - ieatgravity
Lineage OS 13 - srgrusso
Drax - Draco
X2 Mini:
Stock - papacharlieecho
Minicore - papacharlieecho
Lineage OS 13 - srgrusso
Drax Mini - ieatgravity
Kernels
X2:
Butter Kernel - Draco
X2 Mini:
N/a
Apps:
Both:
Ultra Power Saver - Draco
CRAB-Custom Recovery Automated Backup- Draco
Similar devices
X2:
Redmi 3s
X2 Mini:
Yu Black
Wiko U codeFeel Prime
Source:
X2:
Source
Device Tree
X2 Mini:
TBA
In the next post I will go over methods we have used to create everything. If you have any recommended methods on porting or how to do something feel free to add them. I will be updating and adding to this OP as new things come to light. Feel free to use this thread to post questions about or to show off your new development.
as always, Happy modding
-ieatgravity
Reserved for how tos and guides
Reserved
Another Reserve
Yet another reserved
Hi ieatgravityI have a question for you, I think you can help me. I have one wiko Ufeel prime and I rooted the phone blox2 or with drako auto-root tool wen it hade marshmallow Android. Do you no if this works in nougat 7.1.1? My thanks in advance ?
alex moymoy said:
Hi ieatgravityI have a question for you, I think you can help me. I have one wiko Ufeel prime and I rooted the phone blox2 or with drako auto-root tool wen it hade marshmallow Android. Do you no if this works in nougat 7.1.1? My thanks in advance ?
Click to expand...
Click to collapse
Personally I haven't tried. As I'm still running on marshmallow, but from what I gathered from the wiko thread i started months ago the auto root tools were not successful. So for the time being there is no root for 7.1.1
I confirm we can't flash anything in fastboot mode on ufeel prime 7.1.1.
We are looking for since September. Impossible to root.
foxyone0809 said:
I confirm we can't flash anything in fastboot mode on ufeel prime 7.1.1.
We are looking for since September. Impossible to root.
Click to expand...
Click to collapse
Has anyone attempted using Kingroot.apk (NOT KINGOROOT) to root then use a root flasher like flashify, rashr, official twrp app, to flash the custom recovery. From there root using magisk manager patch the boot.img, reboot into twrp then flash the patched_boot.img to boot partition. While still in TWRP, navigate to the kingroot.apk location within /system/app. Delete the kingroot.apk and reboot. At this point you should have a working systemless root without the sketchiness of using kingroot.
If anyone has the time to test this out let me know the results please.
ieatgravity said:
Has anyone attempted using Kingroot.apk (NOT KINGOROOT) to root then use a root flasher like flashify, rashr, official twrp app, to flash the custom recovery. From there root using magisk manager patch the boot.img, reboot into twrp then flash the patched_boot.img to boot partition. While still in TWRP, navigate to the kingroot.apk location within /system/app. Delete the kingroot.apk and reboot. At this point you should have a working systemless root without the sketchiness of using kingroot.
If anyone has the time to test this out let me know the results please.
Click to expand...
Click to collapse
I have try wit kingroot from pc with USB, but not with apk
Kingroot apk doesn't work
Hi ieatgravity ? about yours drax rom, does it work on wiko U Feel Prime? Maybe it's a dummy question but I have my doubts so it's better to ask you (OP) I think ? thanks in advance
Hi guys. I tried another thing in my Ufeel. One week now I have it with Red Wolf custom recovery and Viper_garlic rom 7.1.2 both for Yureka Black running. Everything works fine only with the recovery not. It's working but not 100%? I'm not a developer and I don't have the knowledge and tools for see what can do to better working. I thing sharing this with you guys it's important. And maybe someone with the knowledge (and time) want to see it. I try to get logs from the problems.
ps. Sorry for the bad English ?
New OTA update in France this morning. Version V39, always android 7.1.1. No bugs anymore with delay for unlock phone at reboot. Now fastboot devices is detected but always impossible to unlock. All commands says "unknown command"
Hi guys ? I found one thread for another wiko and it have the same problem but they found a way. I think maybe works for we to but I have no time ( work and new family member ?) maybe someone want to try
https://forum.xda-developers.com/android/help/root-how-to-root-wiko-view-t3740005
Ps- I tried the "Tinno" code in another wiko in nougat and it worked. Hope this is useful
Hello everybody, I just got the BLOX2 Mini and wanted to start working with it. I can see this thread hasn't been updated and that the blox2.com web is down. Can anyone direct me to the best resource available in order to unlock, install TWRP, root, etc. in the Mini, either in XDA or elsewhere? I noticed there's a long thread on the regular sized BLOX2 but I am not completely sure if what is available there will work in the mini.
Thanks!
Lineage 16 for Blu Life One X2 Mini?
Hi ieatgravity,
Are you still out there?
I'm wondering if Lineage 15 or 16 is also available for the Blu Life One X2 Mini?
Best daraabi
X2 is dead.
Guide to restore to stock and add TWRP/root is here: https://forum.xda-developers.com/showpost.php?p=77932487&postcount=6
Mediatek MT8173 & MT8176 development
Hi folks, after I've long been working on my device and only made little progress in building LineageOS for my Xiaomi Mi Pad 3 I decided to look for other developers with similar devices.
My Mi Pad 3 (codename: cappu) is a tablet based on a Mediatek MT8176 SoC. It was launched in April 2017. The tablet comes with a 7.9" display with a resolution of 2048 pixels by 1536 pixels at a PPI of 326 pixels per inch. It is powered by a 2.1GHz/1.7GHz Hexa Core processor ( 2 x 2.1GHz Cortex A72 + 4 x 1.7GHz Cortex A53 ) and it comes with 4GB of RAM. The tablet packs 64GB of internal storage that cannot be expanded. It was shipped out with Android 7.0 (Miui) and is still on this version).
Two months ago Xiaomi finally released Kernel Source Code for my device. It was broken, but I fixed most of the conflicts, streamed the kernel up to latest linux-stable and added some features. I also tried to build LineageOS & AOSP trees, but I have to admit, I'm starting to get desperate. For this specific SoC - even it's predecessor MT8173 - there is no activie development. And that is what I am looking for!
I collected some devices that either use MT8176 SoC, or the older MT8173 SoC. Some of them have Kernel Sources, which I listed and linked below.
All questions, requests for help, suggestions, ... are welcome. If you own any of the listed devices feel free to write and help. This thread is also on Reddit.
MT8176
Xiaomi Mi Pad 3
GPD XD+
Chuwi Hi9
Teclast Master T8
Teclast Master T10
Asus Zenpad 3S 10
Acer Iconia Tab 10 A3-A50
Alfawise Tab
MT8173
ALLDOCUBE Freer X9 (Cube Free X9 (U89))
HITSAN Onda V10 Pro
Pegasus JDTab J01
Acer Chromebook R13 CB5-312T-K8Z9
Amazon Fire HD 10 2017
Lenovo N23 Yoga
Lenovo Flex 11
Xiaomi Mi Box 3 2016
Amazon Fire TV (sloane)
Firmwares & Source-Code:
Chuwi Hi9
https://www.needrom.com/download/chuwi-hi9/ (Firmware)
Acer Iconia Tab 10 A3-A50
https://github.com/Goayandi/android_kernel_acer_titan
https://snlookup.com/acer-iconia-tab-10-a3-a50-tablet-p104780 (Firmware & Kernel-Source)
Xiaomi Mi Pad 3
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cappu-n-oss (Kernel-Source)
https://github.com/Goayandi/android_kernel_xiaomi_cappu/tree/3.18.108 (Kernel-Source)
http://en.miui.com/a-234.html (Firmware)
https://multirom.me/index.php?m=app&a=view&id=81&app=roms (Firmware)
Teclast T10
https://www.needrom.com/download/teclast-t10-e3c5/ (Firmware)
Teclast T8
https://www.needrom.com/download/teclast-t8-e8c1/ (Firmware)
GPD XD+
https://github.com/Goayandi/android_kernel_mt8176_common (Kernel-Source)
https://github.com/skelton/android_kernel_mt8176_common (Kernel-Source)
https://droidbox.co.uk/how-to/flashing-gpd-xd-plus-firmware/ (Firmware)
http://www.gpd.hk/news.asp?id=1519&selectclassid=002002 (Firmware)
Asus Zenpad 3S 10
https://github.com/Goayandi/android_kernel_asus_z500m (Kernel-Source)
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Zenpad/Z500M/Z500M_V13_6_10_15_kernel.zip (Kernel-Source)
https://www.asus.com/us/Tablets/ASUS-ZenPad-3S-10-Z500M/HelpDesk_BIOS/ (Firmware)
Onda V10 Pro
https://www.needrom.com/download/onda-v10-pro/ (Firmware Android)
http://onda.cn/Tablet_Supports.aspx?id=371 (Firmware Phoenix OS)
http://onda.cn/Tablet_Supports.aspx?id=370 (Firmware Phoenix OS)
Pegasus JDtab J01
https://www.needrom.com/download/jdtab-j01/ (Firmware)
Amazon Fire TV 2015 (sloane)
https://github.com/Goayandi/android_kernel_amazon_sloane (Kernel-Source)
Amazon Fire HD 10 (7th Generation)
https://fireos-tablet-src.s3.amazon...PR/Fire-HD10_7th_Gen-5.3.6.2-20180315.tar.bz2 (Kernel-Source)
https://kindle-fire-updates.s3.amaz...wyB/update-kindle-40.6.0.5_user_605485120.bin (Firmware)
ALLDOCUBE Freer X9 (U89)
http://51cube.com/services?_search=U89 (Firmware)
https://www.leakite.com/2017/10/cube-stock-firmware.html (Firmware)
First thanks for your initiative! And I am very interested in obtaining a Custom ROM for my Teclast T10 E3C5 device with the aforementioned MTK8176 Chipset. I cannot help you with development but are open to test it and report bugs.
Hi Goayandi,
I'm not sure how many experienced ROM developers you will get. (I'm not one of them. I have compiled and modded existing ROMs, but never ported one.) I've heard several people say they will look into building a custom ROM for mt8163 or mt8173. But that's always as far as it gets. They never come back with any results. So I was just curious, what are you getting stuck on?
As far as I can tell, one major problem with porting to Mediatek is that they modify a lot of Google's OS code like frameworks and libraries. I do see that you already have some MTK customized repositories in your github library. You may have to do some reverse engineering of the stock ROM to confirm that the MTK changes are the same ones you have in your repos. Yes, that's a huge pain. It's also likely that MTK's patches for mt81xx and mt67xx, which is probably what you have, are pretty different.
One suggestion I want to make is to start out with a ROM that's as close to stock as possible. That means building a plain AOSP build NRD90M. This will reduce as many trouble-causing variables as possible. That's how I would do it. If you accomplish that, it will be easy to move on to higher Android versions or LineageOS, etc.
I would also use the prebuilt kernel for now. There is not much point to compiling your own for the same reason I just mentioned. A lot more variables would enter the equation. (Unless maybe you can test it independently with the stock FW.)
Any chances of giving TeamMAD access to one of these devices?
I have a Teclast T8 stuck in fastboot mode. No recovery, no system. adb cannot see the device. Is there a way to recover from that?
xivxivxiv said:
I have a Teclast T8 stuck in fastboot mode. No recovery, no system. adb cannot see the device. Is there a way to recover from that?
Click to expand...
Click to collapse
In T10 thread I have heard of same kind of issue. Disconnect battery (solder) or wait for device to die, then charge and it should be fine
BiG_FooT said:
In T10 thread I have heard of same kind of issue. Disconnect battery (solder) or wait for device to die, then charge and it should be fine
Click to expand...
Click to collapse
I tried that. That would work if recovery were bootlooping, and system were intact. In my case, my T8 cannot get to system. The Teclast Logo goes through its animation on startup, then gets stuck there. Holding volume up and power gives me 3 choices: recovery, fastboot, normal. Recovery and Normal are both broken. Fastboot is the only one I can do. How to recover from that?
xivxivxiv said:
I tried that. That would work if recovery were bootlooping, and system were intact. In my case, my T8 cannot get to system. The Teclast Logo goes through its animation on startup, then gets stuck there. Holding volume up and power gives me 3 choices: recovery, fastboot, normal. Recovery and Normal are both broken. Fastboot is the only one I can do. How to recover from that?
Click to expand...
Click to collapse
You need to reflash firmware/rom with the sp flash tool.
fastmix said:
You need to reflash firmware/rom with the sp flash tool.
Click to expand...
Click to collapse
You should flash stock firmware on your tablet with SPflash tools. Search for Mediatek SPflash + your device name in Google. Flash procedure should look like this:
FLASH Mediatek device
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT8173_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Download Only" or if upgrade "Firmware upgrade"
- Turn off your phone (and don't turn on the phone).
- Press “Download” button to start
- and connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on.
So you should look for your ROM/FIRMWARE and than flash it. Key step for you is to turn of the tablet, push download button in SPflash tools, and then connect USB to the tablet. Flash will then start!
But Google for instructions on how to use SPflash
Thank you, BiG_FooT and fastmix! Leaving it in power off state before SP flash was the missing step. I don't know how I missed that in previous Google searches. Fully working tablet now.
I now have two of these things. If you (or any others interested in developing this Mediatek) want me to use one of my Teclast T8s for testing for you, let me know.
Has anyone successfully flashed the firmware??
The system.img for all the ROMs is corrupt
Hi! I have an Alfawise Tab (rebranded JDTAB 01) with MT8173 chipset and android 6.0.
I managed to find the stock firmware and recovery, so i tried to port this TWRP recovery: https://forum.xda-developers.com/mi-pad/development/recovery-twrp-3-2-1-0-mi-pad-3-cappu-t3744185 unsuccessfully, maybe because of the different android versions(?)
I don't know....
Does anyone know how to port- build a custom recovery for these chipsets (mt8173-76)?
Or know if there is a working TWRP based on android 6.0 and these chipsets?
So, is there still any development? Where kernel-sources for Teclast devices can be found?
What an utter failure. Of both the manufacturers and the community.
It's fairly clear that the problem is hardware fragmentation. There is just too much diversity in Android hardware platforms, even too many different ARM-based CPUs, and too few users on many of those to justify a major development effort for any of them.
The moral of the story must be: if you want your tablet to remain useful for more than a couple of years, don't buy a cheap Chinese generic one made by a company that isn't a famous global brand. Stick to hardware that has sold in the millions.
ralphclark said:
What an utter failure. Of both the manufacturers and the community.
It's fairly clear that the problem is hardware fragmentation. There is just too much diversity in Android hardware platforms, even too many different ARM-based CPUs, and too few users on many of those to justify a major development effort for any of them.
The moral of the story must be: if you want your tablet to remain useful for more than a couple of years, don't buy a cheap Chinese generic one made by a company that isn't a famous global brand. Stick to hardware that has sold in the millions.
Click to expand...
Click to collapse
What we really need to do is reverse engineer a few roms already built for these chipsets, then see what they all have in common. This will help us figure out what needs to be done to the kernel, and what firmware we need.
Any news? Has anyone tried to flash GPD firmware on one of the other tablets with the same chipset? I have a Chuwi Hi9 with MTK 8173 and I would love to be able to change the ROM, the default one sucks big time. I actually bought it because it had the same chipset as one of the GPD devices.
Where To Start??
Goayandi said:
Mediatek MT8173 & MT8176 development
Click to expand...
Click to collapse
Hi,
If I were you I would start by having a really good look through the MTK_X20_BASE_AOSP open source code here https://github.com/archermind/MTK_X20_BASE_AOSP
In that you will find all the required mtk binary's and documented associated google dependency's and stock mtk app's needed. Dig through all the make files and compare your project_confg which should be in your system/data/misc on 6.0 and vendor/data/misc 7.0 with the one in that source to see whats built.
Because it's mediatek it's messy and things are all over the place but after days of reading it you can kinda start follow the rabbit eventually :laugh:
Take what you need and assemble it into a nice logical fashion using a experienced dev's work as a example and try a AOSP build if that works then try Lineage.
When you have things stable follow others who have stepped up in firmware version.
Most things should work if you have a working kernel.
Best place to start would be HERE it's invaluable :good:
There are other places and make's for BT WiFi GPS etc etc so ensure to explore it well.
Obviosly get the blobs from your own device if poss else pinch them form that source and give them a try it's all trial and error.
If I ever find the time I may join you one day to build a rom for the Lenovo Tab2 mt8165 please note most of these mt8xxxx have a equivalent mt67xx/mt65xx see my sig below for a example.
Good Luck and Happy building :fingers-crossed:
bigrammy said:
Hi,
If I were you I would start by having a really good look through the MTK_X20_BASE_AOSP open source code here https://github.com/archermind/MTK_X20_BASE_AOSP
In that you will find all the required mtk binary's and documented associated google dependency's and stock mtk app's needed. Dig through all the make files and compare your project_confg which should be in your system/data/misc on 6.0 and vendor/data/misc 7.0 with the one in that source to see whats built.
Because it's mediatek it's messy and things are all over the place but after days of reading it you can kinda start follow the rabbit eventually :laugh:
Take what you need and assemble it into a nice logical fashion using a experienced dev's work as a example and try a AOSP build if that works then try Lineage.
When you have things stable follow others who have stepped up in firmware version.
Most things should work if you have a working kernel.
Best place to start would be HERE it's invaluable :good:
There are other places and make's for BT WiFi GPS etc etc so ensure to explore it well.
Obviosly get the blobs from your own device if poss else pinch them form that source and give them a try it's all trial and error.
If I ever find the time I may join you one day to build a rom for the Lenovo Tab2 mt8165 please note most of these mt8xxxx have a equivalent mt67xx/mt65xx see my sig below for a example.
Good Luck and Happy building :fingers-crossed:
Click to expand...
Click to collapse
Hello!
Do I have a chance to do this with my teclast T8 device if I don't have even kernel-source code? For now I've ported most of firmwares different from my stock ROM (MIUI, ZenUI etc). But I would like to upgrade android version ( Nougat to Oreo) if it possible. Since not so long new device ( alldocube X) was released on same chipset (mt8176) with installed android Oreo, maybe this may help some way?
Sword900 said:
Hello!
Do I have a chance to do this with my teclast T8 device if I don't have even kernel-source code? For now I've ported most of firmwares different from my stock ROM (MIUI, ZenUI etc). But I would like to upgrade android version ( Nougat to Oreo) if it possible. Since not so long new device ( alldocube X) was released on same chipset (mt8176) with installed android Oreo, maybe this may help some way?
Click to expand...
Click to collapse
Hello To All
I have a Teclast M89 That I rooted with Magisk and have a working TWRP for backing up.
I am very interested in Testing Kernels and new Roms.I have already wiped and reflashed device a couple times -now Everything for testing,flashing, and booting has been verified.
@Goayandi
Just stopping by to say thanks for this, used some stuff from here for lineage-12.1 on Fire HD10
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677
Hi,
I am using a TCL 20Y, and it's UI is boring and also it runs android 11.
I want to experience the android 13 with a a custom rom like project elixir or ricedroid or pixelplus ui, so can anyone please let me know wheather I can do that.
Like most manufacturers TCL uses different chipsets in different models. I believe your device uses a Mediatek MT6762D. TCL has some snapdragon based phone that have fastboot. TCL Mediatek phones can be rooted and flashed with mtkclient.
This thread documents installing Android 13 in another TCL phone using the same series of Mediatek chipset (P22)
Thank you for the reply,
I am an Android newbie so I don't understand most of those complicated stuff.
If possible could you send me a step by step guide on how to add an custom ROM.
Also I couldn't find any custom ROMs for this device.
Newbie advice: Web search and use the forums search function. There are many, many web pages and videos , maybe even in your native language, that will walk you through this. Before starting you need to have android tools and mtkclient. These are available for Windows, Linux and MacOS.
The first 2 pages of the thread I provided are complaints about how hard TCL made this and unsuccessful attempts to hack. Starting w/ page 3 post #42, @malfuncion first documents how he installed a custom rom.
@malfuncion also provides downloads of all the files that worked for him.
In post #73 I provide copy/paste instructions for mtkclient.
The ROM's I used in the thread are GSI (Generic System Images). I used the ones from TrebleDroid which were fairly stripped down and based on the most recent AOSP code base.
@malfuncion used a CherishOS rom and provides it, repacked as linsuper.bin, on his download site. This may not work as it repacks a vendor.bin which may be different on your TCL model.
On my TCL A30, using the latest TrebleDroid Android 13 rom, the following works: phone, messaging, sim, wifi, camera, gps, brightness. Headphone jack works with alternate Phh jack settings. I successfully provisioned VOLTE using these instructions.
I had issues with apks not being fully functional when installed directly from F-Droid (specifically Geometric Weather widgets did not appear). Installing the apks using "adb install" fixed Geometric weather widgets.
Thanks a lots.
I just bought a Motorola Moto E22 and want to install a custom ROM to get rid of google stuff.
It seems Lineage does not support this phone yet, but I found this LineageOS22 guide which I have no idea it is reliable or if it has anything to do with the official Lineage project.
Any clarification or suggestions for alternative privacy respecting ROMs that work on Moto E22 would be much appreciated.
First of all, don't do these before completing 1 year of buying. You will lose warranty for unlocking bootloader.
Second thing is, if any official rom is not supported, you can definitely use unofficial version from xda. Developers try their best to fix issues with unofficial roms. If you don’t know if it’s reliable or not, read the comments to learn about bugs, issues and positive sides.
Don't be afraid of trying roms built for your model. Because by chance if you don’t find the rom good, you can revert back to stock rom using rescue & smart assistant tool (official software from lenovo/moto)
And before getting started, take note of your model number. Also you have to install device info hw app & click on system there. There you have to find what is your device called in developments. The name will be written beside "device" title (not sure). For example, my moto e5 is called nora in development.
N.B. Dont use any unofficial rom from outside of xda!
Tawsif999 said:
First of all, don't do these before completing 1 year of buying. You will lose warranty for unlocking bootloader.
Second thing is, if any official rom is not supported, you can definitely use unofficial version from xda. Developers try their best to fix issues with unofficial roms. If you don’t know if it’s reliable or not, read the comments to learn about bugs, issues and positive sides.
Don't be afraid of trying roms built for your model. Because by chance if you don’t find the rom good, you can revert back to stock rom using rescue & smart assistant tool (official software from lenovo/moto)
And before getting started, take note of your model number. Also you have to install device info hw app & click on system there. There you have to find what is your device called in developments. The name will be written beside "device" title (not sure). For example, my moto e5 is called nora in development.
N.B. Dont use any unofficial rom from outside of xda!
Click to expand...
Click to collapse
Thanks for the quick response.
Privacy is a greater concern than warranty, so much so that I would have got the PinePhone if I could, but the best I can do is try to mitigate the damage made by stock android spyware and Motorola bloatware.
I'm more than willing to test unofficial roms, the problem is that there doesn't seem to be any available for my model here on xda, not even an official thread yet.
The LineageOS20 for Moto E22 link I found does seems a bit suspicious as there is nothing about it here on the forum.