Hi guys!
Since I didn't find any review to the "A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet" offered in the (german) cect-shop, I was wondering whether someone already bought and tried it. Specs are quite nice, IMHO and videos on youtube look promising. Can someone share his experience with that tablet?
Thanks in advance.
Rena3 Reply
Hi,
I personally have the device and the experience so far has been good using the device.
There is a whole bunch of information over at slatedroid page where there is a group of active users.
Sorry but my post is very little so you have to head over at slatedroidpage, please replace the dots with "."
www dot statedroid dot com/forum/204-rena/
Perhaps someone wants to start a thread over at this page? Hopefully some XDA developer over here owns the device and we can get things started
overall the device has received 3 firmware upgrades so far and the community is hopeful for gingerbread to be released for this. We do have the kernel source codes for this product but do not have any developers to help us out with getting gingerbread out yet for this.
also replace statedroid with "slatedroid"
I also don't purchase this tablet, but i purchase flytouch 3 from a china site,called mcbub.com,i find they have the A9 NEC renesas tablet, here is some review in their site:
http://www.mcbub.com/customer-revie...GB-Bluetooth-HDMI-MID-black-CN101769--136318/
hope this can help you.
nullandvoid said:
Hi guys!
Since I didn't find any review to the "A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet" offered in the (german) cect-shop, I was wondering whether someone already bought and tried it. Specs are quite nice, IMHO and videos on youtube look promising. Can someone share his experience with that tablet?
Thanks in advance.
Click to expand...
Click to collapse
There are a lot of discussions on A9 NEC RENESAS EMMA V2 Dual Core Android 2.2 Tablet at tabletrepublic forum too http://tabletrepublic.com/forum/cortex-a9-renesas-ev2/
full root for Rena 3
Greetings, comrades!
All the usual, lazy engine of progress. Tired of doing manually as rooting and rebuild the firmware for Rena, i am wrote a script that works like a flash, but flash itself is not working, just do it root! =)
Thus, the universal root for any firmware Rena 3:
Install:
Unzip all the files and qroot directory to root SD card.
Turn off the device.
Turn on, hold VOL+ POWER.
Wait until the message "Well done. Root complete."
Reboot device, enjoy.
The necessary files and directories:
install.sh
uImage4
ff4
cramfs4
sdboot.bin
uboot-sd.bin
and directory /qroot
NOTE!
The update does not repartition and reformat the partitions do not.
Is provided as is, no guarantees and responsibility.
Everything you do, you do at your own risk.
for download - depositfiles.com/files/gdx84ktmo
Hi All, I have a Asus TRIO TX201LA intel x86 z2560 soc (AKA TX201LAF, french). I device so obscure almost no one knows it even exists on XDA. Owners of this device are so rare most are dead or locked away with no internet access. Ok all joking aside its pretty rare device with little to no support for it anywhere. Asus never gave it 1 update. Its on android 4.2. It has MANY asus clones including but not limited to the following: Zenfone A450CG/A500CG, FonePad 7 FE375CG/CGX, Asus Memo Pad 7 ME176C/CX, Asus Memo pad 10 me302c. As for devices that share the soc thing include the Galaxy Tab 10.1, Dell Venue 7 and probably more. I think there are more asus devices out there also.
What I want to figure out is this. Which method that I have found to unlock the boot loader is best for me to try to avoid a brick. Here are a list of methods:
1. This method comes from the memo pad 7: https://forum.xda-developers.com/memo-pad-7/help/help-me176c-fastboot-123-screen-t3713930
2. This method also comes from the memo pad 7: https://forum.xda-developers.com/memo-pad-7/general/asus-me176c-cx-unlock-bootloader-t3315603
3. This method comes from the dell venue 7: https://forum.xda-developers.com/showthread.php?t=1787620
4. There is an official method from the Zenfone 4 A450CG which is involves an unlock tool provided by asus. Its called: Unlock_Tool_A400_v8.1.apk. I've explored this the most (tried v7 &7.5) but have been unable to get it to work. This apk installed and gives me the warning about unlocking and losing warranty but then says the my "device model is not supported". I figured an edit to the APK may allow this to work on my bootloader. see: https://www.asus-zenfone.com/2014/11/download-official-unlock-bootloader-tool-zenfone4.html?m=1
5+ there are actually a few more unlock methods I've found mostly for the zenfone 4/5 but they involve flashing here is 1. https://forum.xda-developers.com/zenfone-5/general/guide-how-to-unlock-bootloader-safely-t3562640 & another: https://www.asus.com/zentalk/thread-39834-1-1.html
Due to no support from asus no bootloader unlock will ever be released for my device but I believe one of the above methods either could work "as is" or may need a small edit to work. So can someone help me unlock my bootloader? After this I plan to build a rom using my kernel source here: https://rebyte.me/en/asus/86392/file-543531/ to build a Bliss rom.
Hope that the Unlock_Tool_A400_v8.1.apk can be edited as I see it this maybe the best and easiest to avoid a brk..
Anyone?????
Come on.. this is a simple task for any dev, i should think.
DANG, to many devices not enough devs.. It was all so different before 2010. RIP how it used to be.
son of a snake bite
madhits45 said:
Come on.. this is a simple task for any dev, i should think.
DANG, to many devices not enough devs.. It was all so different before 2010. RIP how it used to be.
Click to expand...
Click to collapse
Yeah man I hear you.. it was once so much better, just to many dang devices now..
Bumpy boompop shazam.. Hello Atoms not DEAD yEt.. https://www.pcworld.com/article/315...m-chip-in-panasonics-2189-android-tablet.html
ompa lumpa bumity bump
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Alando123 said:
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Click to expand...
Click to collapse
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with an assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
First of all, it depends on whether the stock source code is available for your device, if there is no stock source code available to the public(no, I'm not talking about the stock firmware file), then you will not be able to build a custom ROM from source for your device, which means that you won't be able to build anything like LineageOS because setting up the device tree requires the stock source code. No source code=no device tree, no device tree=no LineageOS or AOSP ROMs. Devices that do not have a source code available can only get ROMs if someone chooses to port a ROM from a similar device with similar hardware, that is the only way to get a ROM without stock source code. The stock firmware would be required in order to port a ROM from a similar device, if the stock firmware is not available, you can't port a ROM.
Sent from my LGL84VL using Tapatalk
Droidriven said:
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Alando123 said:
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Click to expand...
Click to collapse
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery such as TWRP(which you'd probably have to build for yourself, which is yet another task to learn in development along with learning to build a ROM, not to mention learning how to get the kernel right) in order to flash a LineageOS custom ROM or any other ROM that is not based on stock, TWRP is easier to learn how to build than a ROM, but still a task in itself. Modified stock ROMs can be customized and flashed without root or custom recovery but they aren't "true" custom ROMs, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Droidriven said:
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery in order to flash a LineageOS custom ROM or any other ROM that is not based on stock. Modified stock ROMs can be customized and flashed, but they aren't custom, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Alando123 said:
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Click to expand...
Click to collapse
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools. I also just stumbled upon the link to the LineageOS page about blobs right before you replied ?
Alando123 said:
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools
Click to expand...
Click to collapse
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Alando123 said:
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Click to expand...
Click to collapse
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Alando123 said:
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Click to expand...
Click to collapse
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't think that any camera app would have helped.. I replaced libcameracustom.so from a different device, and front camera works, but no both cameras have a blue hue on them
I am having problems with building lineageOS for my "Unsupported" Device I have made themed ROMS, Themes for cyanogenmod, Themes for substratum, basic apps for my ROM, and customized recovery and ported ROMS to my device but I need a small headstart to actually "Build" lineageOS for my device. Thats It
Regards
Manav Harsana
PROBLEM:
1. I need to find a forum where I can learn about rooting in a general way, not just a phone specific way. There are too many overlapping problems with my phone and issues that I am too undereducated to pinpoint. I thought learning how to root and flash stock-roms might be the best place to start. Book references or YouTube channels would also be wonderful.
2. I would also like to be pointed in the direction of what the problem might actually be if I am out in left field, and where to find that on this site as well.
HERE'S SOME OF WHAT I WANT TO LEARN IN THE FORUMS:
What is the difference between Rooting and Unlocking the Bootloader? Are they the same thing?
Will re-locking the bootloader resolve the certification issue like I read?
How do I lock the bootloader again?
Can you fix UI crashes by re-flashing a phone's stock ROM?
How is a Factory reset different from a fresh stock-rom flash?
If factory reset doesn't stop the UI Crashes, will re-flashing the stock rom have a different effect?
Etc.
DETAILS:
I purchased a Razer 2 Phone and unlocked the bootloader but it was a long time ago and I don't remember what I did. I did some research and it looks like when I did that my Google Play Store lost its certification. I think that it is causing app bugs and failures but I am not sure because the phone's UI sytem, bluetooth and Wi-fi have been crashing before I tampered with anything when I first bought the phone online. Bluetooth and Wi-fi don't stay on and toggle themselves off. There is also no Bluetooth or Wi-Fi address in the system info. It makes me think that my Door Dash app bugs might be more than one thing.
I work for Door Dash and it's my main income so I need my app to work and I think that the bad certification is causing problems with my Door Dash App. But the Razer also needs a software repair.
Pernilex said:
PROBLEM:
1. I need to find a forum where I can learn about rooting in a general way, not just a phone specific way. There are too many overlapping problems with my phone and issues that I am too undereducated to pinpoint. I thought learning how to root and flash stock-roms might be the best place to start. Book references or YouTube channels would also be wonderful.
2. I would also like to be pointed in the direction of what the problem might actually be if I am out in left field, and where to find that on this site as well.
HERE'S SOME OF WHAT I WANT TO LEARN IN THE FORUMS:
What is the difference between Rooting and Unlocking the Bootloader? Are they the same thing?
Will re-locking the bootloader resolve the certification issue like I read?
How do I lock the bootloader again?
Can you fix UI crashes by re-flashing a phone's stock ROM?
How is a Factory reset different from a fresh stock-rom flash?
If factory reset doesn't stop the UI Crashes, will re-flashing the stock rom have a different effect?
Etc.
DETAILS:
I purchased a Razer 2 Phone and unlocked the bootloader but it was a long time ago and I don't remember what I did. I did some research and it looks like when I did that my Google Play Store lost its certification. I think that it is causing app bugs and failures but I am not sure because the phone's UI sytem, bluetooth and Wi-fi have been crashing before I tampered with anything when I first bought the phone online. Bluetooth and Wi-fi don't stay on and toggle themselves off. There is also no Bluetooth or Wi-Fi address in the system info. It makes me think that my Door Dash app bugs might be more than one thing.
I work for Door Dash and it's my main income so I need my app to work and I think that the bad certification is causing problems with my Door Dash App. But the Razer also needs a software repair.
Click to expand...
Click to collapse
Welcome to XDA,
I would recommend this>
1. Type your desired device for rooting
2. Hit search
3. Once located your device, head to Upgrading and Modifying sub section
4. Be prepared to read a loooot!
5. Practice in your device (try not to brick it)
6. Done!
For this questions there is no general rule you can apply, it will always depend on the device you try to root
What is the difference between Rooting and Unlocking the Bootloader? Are they the same thing?
Will re-locking the bootloader resolve the certification issue like I read?
How do I lock the bootloader again?
Can you fix UI crashes by re-flashing a phone's stock ROM?
How is a Factory reset different from a fresh stock-rom flash?
If factory reset doesn't stop the UI Crashes, will re-flashing the stock rom have a different effect?
Enjoy your stay
Pernilex said:
I need to find a forum where I can learn about rooting in a general way, not just a phone specific way.
Click to expand...
Click to collapse
@Pernilex
Regarding your request. There're quite a few tutorials available like e.g. the ones of @AlaskaLinuxUser. Just use the search function:
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
[Guide][Video Tutorial] Intermediate to Advanced Custom Rom and Kernel Building
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it is helpful to you in your Android career! Praise God...
forum.xda-developers.com
[Video Tutorials] XDA Etiquette, Compiling Custom Roms/Kernels
Praise God! A video tutorial about XDA etiquette! These videos express my personal opinion, and are not necessarily the opinion of XDA. I am not speaking on their behalf. This is just a video series that I put together based on a recommendation...
forum.xda-developers.com
or
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
NOTE: THIS GUIDE WILL WORK ANY ANDROID DEVICE BUT HAS FEW EXTRA PRE-SUGGESTED LINKS FOR GALAXY ACE PLUS USERS. Special Thanks to - dsixda for his awesome kitchen. Please Hit Thanks button for him. inspired by isidromxz's thread. Please kindly...
forum.xda-developers.com
The XDA University might also be helpful:
XDA-University
Tutorials, How-To Guides and More. Learn about mobile phone development, hacking, flashing, rooting and many other topics!
forum.xda-developers.com
Regards
Oswald Boelcke
Senior Moderator
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.