In another thread, someone mentioned installing the cyanogenmod google apps on top of a ROM. The apps I am referring to are here:
http://wiki.cyanogenmod.com/index.ph...on#Google_Apps
I had a few questions on this:
1) Is this a good place to find the most up-to-date google apps for my phone? More up-to-date than those generally included with a custom ROM?
2) Is it safe to flash these apps over any custom ROM, or does that depend on the particular ROM involved?
3) Do ROM developers generally make changes to these apps to improve performance or compatibility with the HTC Hero that I would lose by overwriting them with these?
I purchased outright this Moto E 4G LTE from Staples.
It's not locked to any single carrier and I more than likely will use it as a pocket computer, rather than a talk and text phone.
The details from within the phone are as follows:
Model Number - Moto E (2nd Generation) with 4G LTE
Hardware SKU - XT1527
Android Version - 5.0.2
Baseband version - M8916_200608.08.02.58.15R SURNIA_RETCA_CUST
Kernel version - 3.10.49-gb86829a [email protected] #1 Tue Aug 4 14:44:21 CDT 2015
System version - 22.46.8.surnia_retca.retca.en.CA retca
Build number - LXI22.50-53.8
This is my first plunge into the world of unlocking, rooting, and flashing Android OS.
So far I've been able to gather that cybojenix and squid2 have highly regarded threads and downloads related to the Moto E 4G LTE but the high volume of custom roms, TWRP files, modem files, gapps, patches to fix issues with the camera and patches to eliminate a warning message that warns of a rooted bootloader, etc have left me somewhat overwhelmed lost. I am in need of a short list of what I absolutely need to do what I want to do, and some hints of what extras would work best with my phone in terms of custom roms or whatever relevant.
I'd like to root my phone so that I can run a specific app not related to xdadevelopers. My needs are mostly related to security and anonymity because in my professional life I conduct social research with vulnerable populations and the ethics of my profession dictate a strict code of conduct in this vein.
[As an aside --The app I use unobtrusively requests root access and I fully trust the app since I am very familiar with its history and development to date. The app is found found at f-droid if anyone is interested in checking out f-droid's offerings.]
My questions are these:
What version of twrp-surnia-3.0.0-r*.img will my Moto E work with?
Motorola says my Android Version 5.0.2 is fully up to date when I try to use the in-phone System Updates feature from the About Phone tab in Settings. However I've read in XDAdevelopers that this version of Android can run into problems when using a later version of TWRP.
Can I install a flavour of CM13 straight from Android Version 5.0.2 or do I need to somehow install an Android Version of 5.1 as a first step?
What flavour of CM (Custom ROM) works best with this phone?
I recognize this thread is a bit long winded but I hope to have provided all the necessary details required to seek help from the many expert coders, programmers, and operators dedicated to xda-developers.
Thank you for taking time to read this, and many more thanks if you happen to contribute to any of the solutions that might follow.
Have a wonderful evening.
lostcelt said:
I purchased outright this Moto E 4G LTE from Staples.
It's not locked to any single carrier and I more than likely will use it as a pocket computer, rather than a talk and text phone.
The details from within the phone are as follows:
Model Number - Moto E (2nd Generation) with 4G LTE
Hardware SKU - XT1527
Android Version - 5.0.2
Baseband version - M8916_200608.08.02.58.15R SURNIA_RETCA_CUST
Kernel version - 3.10.49-gb86829a hud[email protected] #1 Tue Aug 4 14:44:21 CDT 2015
System version - 22.46.8.surnia_retca.retca.en.CA retca
Build number - LXI22.50-53.8
This is my first plunge into the world of unlocking, rooting, and flashing Android OS.
So far I've been able to gather that cybojenix and squid2 have highly regarded threads and downloads related to the Moto E 4G LTE but the high volume of custom roms, TWRP files, modem files, gapps, patches to fix issues with the camera and patches to eliminate a warning message that warns of a rooted bootloader, etc have left me somewhat overwhelmed lost. I am in need of a short list of what I absolutely need to do what I want to do, and some hints of what extras would work best with my phone in terms of custom roms or whatever relevant.
I'd like to root my phone so that I can run a specific app not related to xdadevelopers. My needs are mostly related to security and anonymity because in my professional life I conduct social research with vulnerable populations and the ethics of my profession dictate a strict code of conduct in this vein.
[As an aside --The app I use unobtrusively requests root access and I fully trust the app since I am very familiar with its history and development to date. The app is found found at f-droid if anyone is interested in checking out f-droid's offerings.]
My questions are these:
What version of twrp-surnia-3.0.0-r*.img will my Moto E work with?
Motorola says my Android Version 5.0.2 is fully up to date when I try to use the in-phone System Updates feature from the About Phone tab in Settings. However I've read in XDAdevelopers that this version of Android can run into problems when using a later version of TWRP.
Can I install a flavour of CM13 straight from Android Version 5.0.2 or do I need to somehow install an Android Version of 5.1 as a first step?
What flavour of CM (Custom ROM) works best with this phone?
I recognize this thread is a bit long winded but I hope to have provided all the necessary details required to seek help from the many expert coders, programmers, and operators dedicated to xda-developers.
Thank you for taking time to read this, and many more thanks if you happen to contribute to any of the solutions that might follow.
Have a wonderful evening.
Click to expand...
Click to collapse
The basic steps you need to follow are:
Unlock your bootloader
Flash the XT1527 RETUS 5.1 modem (see http://forum.xda-developers.com/moto-e-2015/help/moto-e-2015-modems-t3296044)
Flash the latest TWRP (my 3.0.1-r1 build as of this moment, see http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649)
From TWRP, go into advanced wipe and erase system, data, cache, and dalvik
Flash CM13 + gapps together in TWRP
Apart from the modem, you don't have to upgrade anything else.
I choose to avoid Cm after reading up on it.
I prefer to use the Stock ROM etc
BUT!
I Root it with SuperSU then make my own Bootlogo + Animation
Then i use Squid's Kernel + Squid's TWRP and No-frills CPU Control (to use some of the options Squid's kernel has)
I believe my setup is cleaner and has more stable support and easier to do learn etc.
I checked on what features CM offers and none of it sound like anything i wanted.
I also don't want to have to fiddle around with Gapps or whatever.
I also seen some drawbacks before with some features on the stock Rom that do not work on CM.
I think most people use it simply because it's popular.
Evaluate your options and choose what is right for you.
First thing you want to do is check if you can unlock your bootloader.
Since your from Canada i bet you can.. i did on mine.
Squid's stuff plus Stock Android is good.. in my opinion better than CM.
squid2 said:
The basic steps you need to follow are:
Unlock your bootloader
Flash the XT1527 RETUS 5.1 modem (see http://forum.xda-developers.com/moto-e-2015/help/moto-e-2015-modems-t3296044)
Flash the latest TWRP (my 3.0.1-r1 build as of this moment, see http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649)
From TWRP, go into advanced wipe and erase system, data, cache, and dalvik
Flash CM13 + gapps together in TWRP
Apart from the modem, you don't have to upgrade anything else.
Click to expand...
Click to collapse
Thank you for responding to my questions, squid2. I am very much honored to have had you taken the time to write on my behalf, this is certainly something to which I feel very privledged.
For the sake of clarity and accuracy I will quickly repeat the steps I just took after reading your answer to this thread. If you do not write into this thread a second time I will assume the steps I just took are indeed the correct ones.
1. I went to http://forum.xda-developers.com/moto...odems-t3296044 as you directed and downloaded only the one folder titled Modem, ignoring the larger file that includes another three folders in addition to the Modem folder (the larger file containing all the four files is 25.79GB, whereas the single Modem folder is just 561MB).
2. I then unzipped the Modem folder and selected the SURNIA-RETUS_5.1.zip, ignoring the SURNIA-RETUS_5.1_new.zip which is also in the Modem folder. (The newer SURNIA-RETUS_5.1_new.zip file is two days newer than the other SURNIA-RETUS_5.1.zip file, but since they are both in the same Modem folder I am taking that to mean I should follow your original instructions precisely as directed. Both files are about the same size, except that the newer file is slightly smaller than the other.)
Again, thank you. Your instructions were vital in enabling me to move forward on this task. We need a bitcoin tip jar for people who take time to help others.
xpmule said:
I choose to avoid Cm after reading up on it.
I prefer to use the Stock ROM etc
BUT!
I Root it with SuperSU then make my own Bootlogo + Animation
Then i use Squid's Kernel + Squid's TWRP and No-frills CPU Control (to use some of the options Squid's kernel has)
I believe my setup is cleaner and has more stable support and easier to do learn etc.
I checked on what features CM offers and none of it sound like anything i wanted.
I also don't want to have to fiddle around with Gapps or whatever.
I also seen some drawbacks before with some features on the stock Rom that do not work on CM.
I think most people use it simply because it's popular.
Evaluate your options and choose what is right for you.
First thing you want to do is check if you can unlock your bootloader.
Since your from Canada i bet you can.. i did on mine.
Squid's stuff plus Stock Android is good.. in my opinion better than CM.
Click to expand...
Click to collapse
Thank you, xpmule. I had been wondering whether it was a good idea to install CM or to use a stock Rom. From what I've been reading the Moto E version of Android is fairly bloat-free and since I really only need a rooted phone there is no real need for CM.
I've learned more than once that messing around with unfamiliar OS can be a recipe for disaster after foolishly timing updates of a Linux or BSD OS when I have papers due or exams to study for.
I'll take some more time to research the other options you recommended and then follow your lead with respect to this phone.
Again I'd like to thank both squid2 and yourself for helping me on this, and may I suggest that people who provide meaningful assistance such as this put a bitcoin wallet addres in their signature so that people like me can show our gratitude .
I Support Bitcoin and i think i said that to Squid before too LOL
But i have before refused some for helping people more than once.
My help is not as much as Squid's though.. he puts in effort for his public projects LOL
I don't think you will see him giving advice too much either.. at least i haven't.
So Squid.. GET a Bitcoin address man
OP good luck.. i think Moto's Android is fairly bloat free.. The stuff Moto put on there is good.
Like the twist the phone to activate the camera app or the app that tweaks the notifications.
I am happy myself just modding the stock firmware.
Thank you squid2, I followed your directions exactly as prescribed and I am now rocking the lastest nightly build of CM on my Moto E. It was fairly easy and I can confirm that everything works just fine.
And thank you as well, xpmule. I was going to follow your instructions too but when I got to a certain point in my process and my phone asked if I was sure I wanted to reboot even though there was no OS installed, well I had one of those moments.
Thank you, thank you, THANK YOU!!
Now it's time to explore this CM OS and see what all the fanfare is really about. )
Hello Guys after trying many roms I felt like making one for communtiy
But I didnt want to make it from scratch when google is already doing a great job
of directly proving system.img
So what I did was collected Best of all vendor and major required files for booting. Including Always on Display my favourite.
And made a Flashable Zip of that specific files, images,patches etc.
So yes this best vendor can be used on any GSI FILES which you may want to boot.
This is basically a best Suitable vendor for major roms and specific for all Google Android Roms, I will be updating it when needed
For now,
All you need to do is Install this Zip
Flash System.img (whichever you like generic or Pixel or Other Oem)
Mount system and Vendor
Flash Patch 1 & 2
Reboot System, setup everything
Install latest gms as and when available
Connect to PC (optional) and give commands provided. For best results.
Hope this is exhaustive guide
Download Links
Major Boot Vendor Files
https://drive.google.com/file/d/1GqXP2ddv1DTJ8at_nSZR2_rhRs9iJBhy/view?usp=drivesdk
Q. Why didnt you give whole rom.zip instead of such pieces
A. Because this is only for advanced users , noobs stay away. This is specially made to cater this user who will flash latest GSI images from google and dont have to wait for other Devs to make rom for them. Basically you have PixelUI with minimum bugs.
Q. Can I use other GSI With this vendor
A. As per my research and flahsing experience with this vendor I can say major boots so dont know about others.
Q. Will you support This Project
A. Yes I will and since its not difficult to flash gsi when available theirs no support needed
Q. I want support in sense how to flash and bugs
A. Youre idiot If you ask so since already said this is GSI not Rom bugs are from GSI you flashed so we cant solve. Though patches will be released when available
Special thanks to my group Tester/Fixer
https://t.me/joinchat/E1XkwhvIsDgznr0dMrxzXQ
Havoc OS DEVELOPER, major vendor files are from it including updater script.
Erfan gsi for providing system images at earliest
And you all guys for support
Youtube Video on Latest GSI
HTTPS://youtube.com/JigneshJain
Updated with latest links and vendor
I want to install crdroid vanilla custom rom. I want to know whether microg is device specified like custom roms. I have a redmi note 10. Is there any specified micro g for redmi note 10 or can i install any mciro g. Also please suggest which is better from microg, nanodroid, nikgapps. I am also curious to know its pros and cons.
crdroid is unfortunately discontinued as vanilla build ( I still wonder why.. ) you better stick with other vanilla ROMs then.
however, getting Signature spoofing working on vanilla LineageOS is currently a mess and very tricky (as long as there is no official microG version), so many ways that worked before don't work anymore. nanodroid isn't working, the spoofing is not working. you have to manually extract framework files, deodex files, repack, upload again etc.. cumbersome.
if you have a vanilla ROM that supports signature spoofing out of the box, the best way seems to be having Magisk and installing the unofficial MinMicroG.zip with it. That was the only option that worked for me now on Android 11.
there is also no device specific MicroG version. To get a working MicroG installation it depends on 2 factors:
1. MicroG itself. the current version is kinda buggy on Android 11
2. the way it is installed and bound into the system (priv-app, userapp, as system installation or magisk module)
both need to work hand in hand, that means there are many combinations available that might work and might not work, and it's changing everyday (like, microg community updates fixes and adjusts the code, then google releases next update and nothing works anymore)
again: if your chosen ROM supports signature spoofing out of the box, installing microG is a piece of cake (if you know the right combinations that currently work, f.i. A11+magisk+minmicrog, or (currently not) nandroid, official microG apks only, etc.)
otherwise it's a lot more difficult, because there is currently nowhere a working one-click-solution to add signature spoofing.
(oh, and that's at least my experience so far, if anybody knows better, feel free correct me or add infos, I'm eager to hear)
Hello, so this is a developer oriented thread, so please refrain from answering if you aren't well informed on the subject matter as to avoid cluttering it up.
I've been wanting to ask what the reason of using FBEv1 still in most ROMs is instead of FBEv2 (Starting Android 11). FBEv1 is less secure and is no longer recommended by Google starting 11. Most ROMs are AOSP based anyways, so preserving compatibility with the stock MIUI ROMs in my opinion isn't a valid excuse. Lineage has shown that FBEv2 works just fine on the device. This also creates segmentation between user groups as now part of people are on FBEv1 ROMs and the other part is on v2 making any simple transition impossible without a wipe and making recovery compatibility hell.
Shouldn't we be adopting the newer more secure standard on any non MIUI based ROM for obvious reasons? Especially since going further, newer and newer android versions will eventually leave FBEv1 deprecated.
I'm not meaning to attack or defame anyone here with this, moreso raise the question and hopefully get some developers to switch to FBEv2 in their next release.
+1 I have the same question too. Why not adopt FBEv2?