yashsingh1/xdaforums huggingface dataset:
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
I'm in the process of compiling an Aroma installer containing the correct blobs, apns-config.xml, eri.xml, telephony.db, NON.HLOS.bin, fsg.mbn, ssd.img, and other fixes needed for full 4G/LTE data connectivity with custom ROMs. The Aroma menu gives carrier options for Sprint, Boost Mobile, Virgin Mobile, FreedomPop, and TextNow Wireless. I have the Virgin Mobile xt1766 so once I have the settings ironed out for my carrier, I should be able to implement the fixes for the other Sprint MVNOs. I'd love to have user input on this. The Aroma installer itself is fully working, and I'm now configuring the data fixes for each carrier. [MENTION=8947538]Goose03[/MENTION], what are you thoughts on this? I see that you've been doing some nice development for this E4.
[Moto E4 Guides, News, & Discussion] madbat99:
That will be a much appreciated addition. I'm on virgin mobile as well. I had lte on aokp with the apn fix zip given to me in the e4 telegram group. But haven't tried any others.
[Moto E4 Guides, News, & Discussion] Goose03:
I'm not sure how well this will work, considering what I know about this issue, but it's worth a try I guess. From what I've seen, you know what your doing with that type of stuff. The dev for lineage for the E4 Plus has done some amazing work getting things working for that device mainly, but has also done some work for this device. He is a programmer and amazing with coding. But is pretty new to playing with Android. Maybe the two of you can collaborate and get this issue squared away. He's trying to actually fix the problem properly and not just do a hack job fix like what was done for Surnia. It would be really nice to see all things working for everyone. I just hope when we finally get Oreo trees, this problem doesn't start all over again like it seems to with CDMA devices for every new android version.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
I appreciate your encouragement and, believe me, I fully understand any skepticism you have. Yes, custom ROMs for these CDMA Moto devices have given us all headaches on data connectivity and telephony for many a year now. Like you, I'm hoping the Oreo trees do not give rebirth to this nuisance. As you recommended I will try and collaborate with a couple of the knowledgeable devs on this subject. I'm having really no problem maintaining consistent 3G data on custom builds. It's getting & maintaining the LTE that's proving tough. Thanks. And I will keep you posted.
[Moto E4 Guides, News, & Discussion] Goose03:
If you skim through he last few pages of this thread: https://xdaforums.com/moto-e4-plus/development/rom-lineageos-14-1-moto-e4-plus-qualcomm-t3734197

and look at the device trees, you'll see what he did. He is really close to having provisioning working exactly like it does on stock with some blobs taken from the Moto Z Griffin. The only similar device known of that uses Chameleon provisioning. He rewrote a lot of code and there was only one thing not working right. He's really close to getting provisioning working perfectly. All the work he's done can easily be used for Perry also because the firmware is almost identical, and I'm sure he was planning on getting this working for both devices. You should definitely get in touch with him.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
I'm going through the red-tape process of getting permission to read the actual mobile service provider manifests, which are kept and filed by Motorola Mobility, and give an exact blueprint of each carrier's telephony & provisioning manifests as applied to each variant of the device. For example, these show the exact distinctions between each branded carrier variant, such as Sprint, Verizon, Boost, Virgin, AT&T, etc. There's something I'm missing here, and these manifests will provide answers if I can get access to them. Motorola has given access to these in past years, as long as doing so doesn't violate any contractual provisions between Motorola and the service provider, and as long as neither the provider nor Motorola deem the manifests as sensitive security work product information.

By the way [MENTION=8947538]Goose03[/MENTION], I did read over and am very familiar with [MENTION=4136656]SeanStar[/MENTION]'s work & progress on this. I consider him the utmost authority on carrier provisioning. He's extremely knowledgeable. I'm trying to take a shortcut basically and figure out what's missing by taking a direct look at Motorola's build manifests. Thank you very much for taking the time to help me and give input on this. Much appreciated.
[Moto E4 Guides, News, & Discussion] SeanStar:
If you get those manifests, that would be an instant solution if it really shows the exact provisioning details. We could rewrite everything from scratch, and include it in lineage if we wanted to as open source. The only reason I haven't completely rewritten this yet is because half of the code is locked away in the binaries.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Oh ok. That's good to know -- that you can confirm LTE data connectivity on AOKP. In theory, the fix should work on other custom ROMs. That's the goal of my fix -- a universal flashable zip that will fix data on all custom ROMs, as well as provision TextNow functionality for perry users who want to use TextNow on their device. Thanks for your feedback. This is looking more & more possible as I go.

---------- Post added at 05:13 AM ---------- Previous post was at 05:05 AM ----------

Yes, it is indeed locked away. That's been my drawback as well. That's where the carrier manifests will solve our problems. I was able to get access to the Moto E LTE xt1526 manifests back in 2016, and with them fix data connectivity on the Virgin Mobile & Boost variants. My guess is, partitions like /pds and /cid will contain answers within their binary. This was the case with the xt1526 and the Moto G3 xt1548. I will be more than happy to share this info when (and if) I get access. I'm an RF Systems Analyst for Motorola Mobility, but it doesn't get me special favors in terms of work product information. I'm still required to fill out the requests and submit them to the brass. But wish me luck. And thank you for your reply. Good to make your acquaintance sir.
[Moto E4 Guides, News, & Discussion] Az Biker:
* * * Thread Cleaned * * *

The discussion of bypassing the payment requirement and receiving app features or premium services that require payment, is not permitted on Xda and violates Forum Rules.

6. Do not post or request warez.

If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used.

9. Don't get us into trouble.

Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.

This will be the only warning given in this thread. Members who violate this rule, and/or continue this/start another discussion, will have their accounts reviewed for restriction or removal.
[Moto E4 Guides, News, & Discussion] InterfaceNode:
Rule 6 doesn't even apply since I was talking about an App available on the Play store and still didn't post it.

Rule 9 doesn't apply because I didn't post methodology

But none of this changes the fact that in this world might makes right, so you're exactly within your power.

Thank God you're a mod and not a Judge I'd hate to have my future in reality riding on your casual glance and summarized understanding.

It takes almost no time to actually read and you weren't even willing to do that
[Moto E4 Guides, News, & Discussion] Az Biker:
I read enough of your words:

"An unlimited LTE exploit does exist for this device right now, it's possible to use unlimited LTE without paying for it on a device that is not registered with Boost.

IE: The phone can still use LTE despite not being active due to never being activated or being unpaid.

I don't want to detail it too much here because of lawsuit potential though but I can't believe the cool things I find when I put my mind to it.

I would be open to telling people who meet the following conditions how to do it:"

Rule 6: ..........or other means of avoiding payment, can be obtained or used.

Rule 9:........ or do other things which will obviously lead to legal trouble.

If you have an issue with my Moderation, feel free to contact any Senior Moderator and explain how what you're doing is not in violation of the rules, and what I'm doing is.
[Moto E4 Guides, News, & Discussion] InterfaceNode:
Yeah I guess you're right, when I consider it from your POV thats loose
[Moto E4 Guides, News, & Discussion] hitokage004:
There are basically two different versions of this phone - one with a Qualcomm chipset and one with a Mediatek chipset. The Mediatek version as far as I know is the international version, with the Qualcomm being the US version. The firmware is NOT interchangeable between the two.

If you have the XT1768 Qualcomm version and an unlocked bootloader, you can flash the carrier unlocked retail version of the firmware that will work with US GSM carriers. This may or may not give you access to other GSM bands used elsewhere. Here is the US Motorola specification page (the full specs are near the bottom) that show what is officially supported.

If you have the XT1760 Mediatek version and an unlocked bootloader, you can flash the carrier unlocked retail version of the firmware, and should be good with any GSM carrier in any country.
[Moto E4 Guides, News, & Discussion] apinkshidae:
Thank you for your reply, as far as i know, the moto e boost mobile doesnt have the fingerprint scanner, but its the same Qualcomm chipset as the unlocked U.S version, i know the mediatek firmware is not compatible with the Qualcomm phone, but i wanted to know if the difference in hardware made it impossible to flash unlocked u.s firmware in boost mobile version, or if, using the same boost mobile firmware is possible to use different gsm bands outside the u.s without needing to flash a different region firmware
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Yup. Just swapped to the E4 Today. Wtf y'all? XD we keep shifting to the same direction XD

---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------

Rn I have an E4, J7, and a Volt
[Moto E4 Guides, News, & Discussion] :
Boost?
[Moto E4 Guides, News, & Discussion] DeadJenkins:
Anyone know what the XT---- version number is for the Boost Moto E4?
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Always lol. I had an issue last night bc the TWRP does this Mount Decrypt Storage upon initial boot (found a fix, yet got stopped at the Google Wizard Setup)... so i just do the temp twrp boot and I got Magisk and a Stericson Busy box on this. debloating is very baaaad if you try to fix the Password glitch.... so... Just simple flashing is fine. who knows... someone might make a recovery rom for now to skip the headaches... >_> <_<

---------- Post added at 08:00 AM ---------- Previous post was at 07:35 AM ----------

https://www.androidfilehost.com/?fid=673368273298943737

BusyBox-1.26.2-Stericson-Stable.zip flashed via TWRP is the most stable to use, If you are using apps that require busybox, as the main busybox app doesn't work to install the files properly.

[MENTION=8454248]zoofie666[/MENTION] can you add this as a heads up to your install list?
[Moto E4 Guides, News, & Discussion] BucketHeadFan:
Boost Moto E4 Model#

Yes Sir, The Boost Moto E4 is XT1766
[Moto E4 Guides, News, & Discussion] :
If you could get me that backup that someone else said they'd give me and never did, I can have one done in a few minutes. I already made one for Sprint. Just haven't posted it because the kernel source wasn't released yet and with my luck, it'll just get taken down even though no body else posts sources with stock ROMs like they should. I planned on making one for all the Qualcomm variants. If you could, can you try to use adb or a terminal and pull the radio and OEM.imgs? Or at least while in recovery, copy the OEM partition to external SD and zip it up and upload that for me? I would be very greatful for your trouble.
[Moto E4 Guides, News, & Discussion] CodyF86:
[MENTION=5768732]amarc78[/MENTION]

XT1766-Nougat71-System-Stock-Rooted

I run the server hosting that url, so it's already available to download and should be good to go.

Don't be alarmed when/if your browser complains about the SSL cert. Wasn't going to pay $100 for a company to sign mine when I can sign it myself, ha!. I can provide FTP access also if need be, just let me know.

Sorry about that. Here is the system and kernel nandroid of the updated xt1766 stock nougat rom although it's already been rooted and dm-verity disabled, but that's probably a good thing / it can be undone.

I also included /oem although I already went to town and had removed some Amazon crap.

On a side note I threw this together in a few hours. Give me a week and if someone doesn't beat me to it I should have lineage-15.0 booting. The repos are far from done so don't get your hopes up of it building just yet. :)

https://github.com/codyf86/android_device_motorola_sperry

https://github.com/codyf86/proprietary_vendor_motorola_sperry
[Moto E4 Guides, News, & Discussion] :
Awesome. Thank you! I'll have a rom for Boost done later. I've been working on lineage also. I got a build finished, but doesn't boot yet. One thing I noticed in your device trees is in sperry.mk vendor/cm is now vendor/lineage for 15.0.

Edit: never mind that, I'm trying to build 15.0 for surnia and was thinking about vendor/lineage for that. Trying to do too many things.
[Moto E4 Guides, News, & Discussion] SykkNyzz:
I would.... If it didn't give a headache with a Mounting system storage password issue.
[Moto E4 Guides, News, & Discussion] :
You shouldn't have a problem with that. If you format data and reboot twrp you should be able to just skip that putting in a password part and go to mount and make sure the mount system partition read-only option is not checked.
[Moto E4 Guides, News, & Discussion] :
Here's a link to a Boost stock rooted twrp flashable rom. https://www.androidfilehost.com/?w=files&flid=208049 If someone wants to test it. Just install phh's superuser apk from the play store and it should be good to go. Busybox from here seems to work ok: https://www.google.com/amp/s/xdafor...ng/tool-busybox-flashable-archs-t3348543/amp/ [MENTION=5337314]CodyF86[/MENTION] I'm getting a f/c from google play services and can't sign in with the backup you gave me. I think it's just because I flashed the sprint carrier, fsg and modem imgs. When you have a chance or if someone else with Boost rooted stock can pull the modem.img, carrier.img and fsg.img. If you don't know the commands just open the terminal, type su and grant su pemissions then type: dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.img and the same for the other imgs just replace modem and modem.img with carrier and carrier.img etc. Please and thank you!

Edit: added link
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Then it goes back to the wizard for me lol and since I tried debloating prior... I got headaches. XD btw All you gotta do is Extract that rsd file and swap the recovery with the TWRP and reflash lol

---------- Post added at 02:07 PM ---------- Previous post was at 02:01 PM ----------

And flashify is perfect after rooting.
[Moto E4 Guides, News, & Discussion] :
If I find out after all this time the sprint NCQ26.69-33_cid50 firmware is Boost I'm going to freak out. I assumed it was the original sprint firmware. I just flashed it and I think it is. I assumed the boost firmware would say boost like it has for every other Motorola I've had, not sprint. If only I could get the update to flash.

Edit: I just realized when I first got this phone, it had sprint apps like my sprint instead of boost didn't it?
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Fxck Boost Mobile & Amazon Apps... Omfg they are a pain XD

---------- Post added at 03:09 PM ---------- Previous post was at 03:08 PM ----------

Is yours Sprint? Bc Sprint apps change based on the phone company. Like sprint VVM turns into boost if on a boost device.
[Moto E4 Guides, News, & Discussion] :
No, it was boost when I bought it. I don't remember any of the apps being boost apps though. I haven't activated it yet either.
[Moto E4 Guides, News, & Discussion] SykkNyzz:
That why. If it wasn't activated...
[Moto E4 Guides, News, & Discussion] :
I don't think that is boost firmware. I'm pretty sure it's the original sprint firmware. This is why I wanted someone with boost to pull those imgs for me. I want to activate the phone, but not sure if it will go OK on sprint firmware.

Edit: I'm about to just buy another one. I'll figure it out. I wanted to get my wife one anyway.
[Moto E4 Guides, News, & Discussion] :
Well. I said screw it and activated it. RIP surnia. Not building 18 ROMs for that anymore now. Now I've got a ridiculous amount of crap on my phone to remove. It works though. Now I need build some ROMs.
[Moto E4 Guides, News, & Discussion] ATTACK:
Ok... I haven't work with Android in quite some time, so bear with me.

I've been reading through several threads, but i'm confused as to where custom recovery, root and so on stands. Please let me know if I have this correct.

// UNLOCKING THE BOOTLOADER - Same as always, Moto's website.

// CUSTOM RECOVERY - TWRP for Moto G4 (Qualcomm) Correct Recovery? Title says "G4", so it kinda throws me off, Typo maybe. Do I flash this like normal, or is my only option to boot it?

// ARE THESE STEPS CORRECT?

_• Flash TWRP

_• Factory Reset/Reformat

_• Reboot TWRP

_• Flash DM Verity zip

_• Flash PHH's Superuser

_• Boot to OS

// RESTORING TO FACTORY NEW - Same as always, RSD Lite. Is the Sprint firmware listed in the OP correct?
[Moto E4 Guides, News, & Discussion] :
Sounds about right to me. Just know that as far as I know, the Sprint firmware is Sprint not Boost but it works and I don't know yet if there will be actual Boost firmware released at some point or if they figured out how to just use the one firmware for both.
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Just be careful if you get that data protect issue
[Moto E4 Guides, News, & Discussion] :
Did you still not get your problem figured out?
[Moto E4 Guides, News, & Discussion] SykkNyzz:
I have an answer but it is impossible to do if you are trying to back up the data as well. XD
[Moto E4 Guides, News, & Discussion] :
New Magisk 14.0 installs and seems to be working.
[Moto E4 Guides, News, & Discussion] kartik verma:
is there any way to make it working with mediatek variant. as far as i know SuperSU unable to create path and failed to root. during magisk it failed to mount magisk.image outside the /data.
[Moto E4 Guides, News, & Discussion] :
Don't know, did you try it? I couldn't get previous versions to work.
[Moto E4 Guides, News, & Discussion] kartik verma:
i got my moto e4 today from service center and they install a firmware from different software channel before it was "Retin" and now "Retapac".

for now i am not going to unlock bootloader.

need a tester who can test the new magisk version on mtk variant.
[Moto E4 Guides, News, & Discussion] :
My problem installing Magisk before was it failed to mount /data/magisk.img I'm willing to bet it should work for you now.

Edit: I can't get modules download to even try to install from within Magisk manager. They start downloading then I get a toast saying "process error", but it will download and re-install Magisk just fine.

Edit: I cleared the repo cache in Magisk manager settings, rebooted and installing modules works fine.
[Moto E4 Guides, News, & Discussion] andMego:
Your no longer need a custom recovery to install magisk, just an unlocked bootloader.
[Moto E4 Guides, News, & Discussion] kartik verma:
:eek:
[Moto E4 Guides, News, & Discussion] andMego:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 in the first post it explains how
[Moto E4 Guides, News, & Discussion] kartik verma:
:silly:
[Moto E4 Guides, News, & Discussion] kartik verma:
which one you use ?

the beta one or from the main thread.

:confused:
[Moto E4 Guides, News, & Discussion] :
https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

14.0
[Moto E4 Guides, News, & Discussion] CodyF86:
I've got a kernel built from source to boot but hangs displaying the N/A which is actually the signature the kernel is signed with, but since it doesn't need to be signed it just shows n/a. Before it was falling back to the bootloader failing. Using the extracted device tree dts. Got me that far. Going to try and throw the stock ramdisk back in to see if it's just an init file I'm missing or if it's some other voodoo.

http://www.github.com/codyf86
[Moto E4 Guides, News, & Discussion] :
Nice work man. I've been keeping an eye on it. Are you trying to boot this with stock, or were you able to get a los-15 build done? I'll sync up and see if I can do anything to help. I'll have a little free time tomorrow.
[Moto E4 Guides, News, & Discussion] CodyF86:
https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=LA.UM.5.6.r1-05800-89xx.0

Which the stock moto e4 list in the build.prop as the tag.

Along with:

https://github.com/codyf86/android_device_motorola_perry

https://github.com/codyf86/android_kernel_motorola_msm8937

and:

https://github.com/codyf86/vendor-qcom-opensource-wlan-prima/tree/LA.UM.5.6.r1

pointing to kernel/motorola/msm8937/drivers/staging/prima in roomservice.

Our buddy the e4 uses pronto wifi also. :)
[Moto E4 Guides, News, & Discussion] SykkNyzz:
This is /oem/amazon. I tried removing this and the phone froze. If anyone is going to debloat.... This is my 2 cents
[Moto E4 Guides, News, & Discussion] SykkNyzz:
So: Boost, Sprint, Sprint Prepaid, and Virgin..... But virgin only does iPhones now.... Hmm...

(Retconning the virgin mistake I made: https://www4.virginmobileusa.com/#!/shop/phones/@Android/ )

---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------

[MENTION=5768732]amarc78[/MENTION] ?
[Moto E4 Guides, News, & Discussion] :
You have to delete the folder through TWRP or it will freeze the phone. Reboot to TWRP, click mount then click the oem box. Next go to the twrp file manager to delete the folder.
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Remember that issue I told you about with TWRP on my end.... Well I just wanted to let you know about it if you create a debloated flashable version.

---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------

Trust me about knowing that lol. I've been active with this rooting/debloat insanity since LG Ally was born

---------- Post added at 01:08 PM ---------- Previous post was at 01:04 PM ----------

Ally and Volt both have 740.... Wow. I was majorly active in the Volt Community and put in 6 working roms for them. I just don't understand the architecture of Nougat like I did KitKat.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Hows it coming along, I see you putting in hard work and I really appreciate it.
[Moto E4 Guides, News, & Discussion] cedarknoll:
anyone tried converting to verizon? any reason it wouldn't work?

edit: i assume you would have to get a sim unlock from ebay first
[Moto E4 Guides, News, & Discussion] :
Since Verizon doesn't allow bootloader unlocking, I would be really surprised if they'd let you activate another carriers device because once word gets out this is possible everyone who wants to unlock and root will stop buying Verizon devices and buy other carriers instead. They will lose money and it would just be stupid on their part.