yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] anthonykb:
--- Flash files that are contained in Surnia_Moto_E_2015_6.0_Stock_Partition_Updater.zip from 2nd post at linked thread by Buzbee2 >

https://xdaforums.com/moto-e-2015/cdma-development/stock-xt1521-gsm-xt1526-cdma-t3342789

--- Flash using following fastboot commands as follows with the images from the zip extracted to the C:\ drive ---

fastboot flash partition C:\gpt.bin

fastboot flash bootloader C:\bootloader.img

--- Then the radio firmware will operate fine on the Moto E 2015 Boost Mobile XT1526 phone after flashing the radio in TWRP---
[E 2015 Original Android Development] MotoJunkie01:
Interesting, so the Boost variant must first have the bootloader and partition index updated to stock6.0? Good find. Glad you got it working on your Boost Mobile variant. [MENTION=7428782]anthonykb[/MENTION], what I'll probably do, or you can do it either one, is go ahead and incorporate gpt.bin and bootloader.img from stock 6.0 into my updater-script for Boost users. For Virgin & Sprint users, I'll leave everything like it is.
[E 2015 Original Android Development] amarc78:
I was already updated to the 6.0 bootloader and even with a clean install it still didn't work for me. Won't read sim card at all.
[E 2015 Original Android Development] MotoJunkie01:
Hmmmm. Did you fastboot configure your carrier and fsg partitions?

fastboot oem config fsg-id boost

fastboot oem config carrier boost
[E 2015 Original Android Development] amarc78:
I'll try again, but yes.
[E 2015 Original Android Development] MotoJunkie01:
Try this, and I think we can get things working. Install a pure stock 5.1 firmware build. I'll get you an Aroma installer that will configure your configs for Boost Mobile. I want to try pure stock because we need to do a PRL & Data Profile update. Use any 5.1 build except s.12. And, of course, disregard flashing gpt.bin or bootloader.img from the firmware package of 5.1.Let me know if you install 5.1 stock. I'll get some of the files together we will need. Also, should you need any firmware builds for your xt1526 let me known. I have all firmware packages that were ever made for the device. I've got fastboot flashable packages and TWRP flashable zip versions.
[E 2015 Original Android Development] MotoJunkie01:
Here is the Aroma installer. Simply flash this using TWRP recovery. Select "Boost" when the installer prompts you to choose a carrier.

https://drive.google.com/file/d/0B1Sfod4HWfk2ZFQybXFiZHZDYkE/view?usp=drivesdk

You could try the Aroma installer now, before going through the 5.1 firmware package flashing. There's a pretty good chance that the Aroma installer alone will configure the baseband to work with Boost on your device.
[E 2015 Original Android Development] MotoJunkie01:
On the Boost Mobile xt1526 variant, here is what I just done and it worked perfect on mine. I "dirty flashed" the baseband installer, basically installing the radio firmware and leaving nv data intact, then rebooted system. On the stock dialer, I opened the SCRTN Menu (Network & Carrier Config Reset) by dialing ##72786# and choosing "YES" when prompted. Upon reboot, I again booted into TWRP and installed the MVNO_Slayer Aroma zip and selected "Boost" from the carrier menu. Then I rebooted system. RIL is fully functional, as is 4G/LTE data connectivity. Updating my partition index and bootloader to stock 6.0 was not necessary. (My bootloader.img and gpt.bin are the original stock 5.0.2 versions that shipped on the Moto E LTE xt1526 during initial release of the device).
[E 2015 Original Android Development] MotoJunkie01:
[MENTION=7428782]anthonykb[/MENTION], I'm going to compile a separate zip installer for the Boost variant. It can be done one of two ways, both of which we have confirmed to work: (1) I can either include stock 6.0 bootloader.img & gpt.bin in the zip/updater-script, or (2) I can reincorporate a format command for modemst1 & modemst2, and include the apns-config.xml/eri.xml for Boost from the mvno_slayer Aroma installer. What are your thoughts?
[E 2015 Original Android Development] tzheng0311:
Just wondering, are the IMG files essentially the same as fsg.mbn and NON-HLOS.bin? Regards
[E 2015 Original Android Development] MotoJunkie01:
img, mbn, bin, etc, are all image type formats which can be flashed from fastboot. For the purposes for which I am using them, yes they are exactly the same. To clarify, NON-HLOS.bin and modem.img are the same, and fsg.mbn is the same as fsg.img.
[E 2015 Original Android Development] MotoJunkie01:
[MENTION=7710906]tzheng0311[/MENTION] have you given this a try on your DDR devices yet? Works great on forced roaming on DDR, on stock ROMs anyway. I've not had a chance to test the data handover on custom ROM roaming yet.
[E 2015 Original Android Development] tzheng0311:
I'm going to try it later on today, thanks for the heads up. I'll let you know, I have like 3 on stock ROM and the rest on CM13

Edit: Woop, turns out i'm on S.12 and this baseband really doesn't like it lol, gonna update first
[E 2015 Original Android Development] amarc78:
Did you get this to work running stock or a custom rom? I tried again running HalogenOS and still didn't work. I'll restore stock and try it, then if it works I'll try flashing some custom rom. When I can have my phone down for a bit.
[E 2015 Original Android Development] MotoJunkie01:
Yes. I installed it on my Boost xt1526 variant using the instructions a couple posts back. I'm updating the Boost variant's installer to be exclusive to Boost only, and Sprint/Virgin will have its own installer. Oh, to fully answer you, I've confirmed that it works on the Boost variant on Stock & CM,/LOS ROMs.

I am nearly 100% certain you need a PRL & Data Profile update. For those you'll need to first install stock, then we update your configs, then you can flash pretty well any ROM you wish.
[E 2015 Original Android Development] :
I give up. I did everything exactly the way you said and different ways, but no matter what I do I can't get it working on a custom rom. I tried Viper, Halogen anf AICP. I got it working on stock, then when I entered the dialer code and did that step I ended up with no signal on stock and had to start over again. I reinstalled stock and your modem updater and regained a signal. I then clean flashed a custom rom and still had no signal. Maybe it's because of the 6.0 bootloader I'm running on.
[E 2015 Original Android Development] MotoJunkie01:
On the Stock 6.0 bootloader.img and gpt.bin prerequisite, this is what first initiated my baseband to work. The gpt.bin actually alters the partition sizing on /fsg, fsc, ssd, /modemst1 & /modemst2. My installer flashes two key radio partitions: /modem, of course, and /fsg . Before you took the 6.0 partition update, your device's fsg partition was actually too small for the fsg.img in my installer. The 6.0 stock bootloader.img updates and alters the /tz partition, /aboot (application bootloader), /rpm partition (primary bootloader), and the extremely dangerous & sensitive sbl1 partition (secondary bootloader). Believe it or not, none of these bootlloader partitions affect cellular connectivity in any way. So the 6.0 bootloader can safely be ruled out as your issue.
[E 2015 Original Android Development] MotoJunkie01:
[MENTION=5768732]amarc78[/MENTION] I know you done this previously, but please try this in fastboot as an added step:

fastboot oem fb_mode_set

faatboot erase carrier

fastboot erase modemst1

fastboot erase modemst2

fastboot oem config fsg-id boost

fastboot oem fb_mode_clear

Reboot system and go directly to Settings Mobile Networks Access Point Names

Let me know when you get that far please
[E 2015 Original Android Development] :
Can't do it right now. I'm not by my pc and can't have my phone down right now.
[E 2015 Original Android Development] MotoJunkie01:
OK. When you get a little time & feel like working on it, I'm pretty sure we can get it straight.
[E 2015 Original Android Development] tzheng0311:
Sorry for the delay Moto, I still haven't been able to flash it onto any of my vanilla 5.0 builds. Flashing the baseband causes the phone to lose its modem. Does it require the 6.1 bootloader?

Thanks
[E 2015 Original Android Development] MotoJunkie01:
Some members have reported that on Boost Mobile, flashing the stock 6.0 bootloader & gpt.bin (partition index) is first required. On Virgin Mobile & Sprint, the Baseband should work on any stock or custom ROM that is 5.0.2 - 7.1.2_r33. Please report back and let me know.
[E 2015 Original Android Development] FanboyStudios:
Doesn't seem to work for me... Maybe its my kernel causing it?
[E 2015 Original Android Development] MotoJunkie01:
Yes that's possible also. Keep in mind that testing on this baseband has been done mostly under a stock scenario. However, many custom ROM users which tested also reported no problems. What kernel are you using?
[E 2015 Original Android Development] FanboyStudios:
FireKernel... Latest version that still has the overclock.
[E 2015 Original Android Development] tzheng0311:
Okay, i'll keep trying, I can't seem to get it to work on my VM 5.0.2 builds
[E 2015 Original Android Development] FanboyStudios:
Confirmed not working... I've been through some remote areas where VM didn't have coverage but Verizon did. No roaming.

CyanogenMod 13 with FireKernel
[E 2015 Original Android Development] FanboyStudios:
Pic
[E 2015 Original Android Development] anthonykb:
If you want to revert to native stock Boost Moto E 2015 firmware partitions download zip here:

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

Unzip the compressed firmware package files to a folder and open command prompt changing

directory to the same folder with unzipped files so you can run commands to flash firmware:

cd C:\MOTOE

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot erase cache

fastboot erase userdata

fastboot erase customize

fastboot erase carrier

fastboot oem config carrier boost

fastboot oem config fsg-id boost

fastboot oem fb_mode_clear

Boot the phone into the android os and provision/activate your service to the modem

either the usual way or by using SCRTN dialing ##72786# in the dialer. Accept the

prompt then reboot the phone and let it do it's thing until you return to the homescreen.

If switching back to the Moto E 2015 from another phone, tap activate button after booting the phone

to open EPST where you will follow a prompt confirming you are switching devices by tapping yes.

Enter your Boost account information to restore service provisioning to this device.
[E 2015 Original Android Development] :
I activated my Moto E 4 so I won't be trying this mod anymore. R.I.P Surnia.
[E 2015 Original Android Development] FanboyStudios:
Aww :(
[E 2015 Original Android Development] MotoJunkie01:
Yeah I know what you mean. I'm mainly on my Moto G3 Osprey these days. Same hardware, SoC and baseband as the Moto E2 Surnia, but bigger display and overall better performance.
[E 2015 Original Android Development] MotoJunkie01:
[MENTION=6673664]FanboyStudios[/MENTION], if you want optimal roaming support, trust me, go full stock. You can root, customize, deodex, OMS theming, etc. I prefer custom ROMs too, but I like my domestic roaming more.
[E 2015 Original Android Development] RedStripeE90:
I have the Boost XT1526. Will this unlock the SIM card slot so you can use it with T-Mobile or AT&T?
[E 2015 Original Android Development] FanboyStudios:
Have a link to Virgin Mobile Stock ROM?
[E 2015 Original Android Development] MotoJunkie01:
Lp

I have all stock firmware packages for the xt1526 in my archives on Google Drive storage. There were officially 7 firmware builds for the Moto E LTE Virgin Mobile.

1. Android 5.0.2 (LXI22.50-14.6)

2. Android 5.0.2 (LXI22.50-14.8)

3. Android 5.1 (LPI23.29-18-S.1)

4. Android 5.1 (LPI23.29-18-S.2)

5. Android 5.1 (LPI23.29-18-S.8)

6. Android 5.1 (LPI23.29-18-S.11)

7. Android 5.1 (LPI23.29-18-S.12)

[MENTION=7313305]Buzbee2[/MENTION] actually compiled Stock 5.1.1 and Stock 6.0 ROMs for the xt1526, by porting them from Surnia variants released outside of the United States. My experiences with both his 5.1.1 & 6.0 have been remarkable. By the way, those ROMs come with a flashable Aroma installer to configure voice and data services for Virgin Mobile DDR. Oh, a piece of info you may find interesting also: the Virgin Mobile, Boost Mobile & Sprint variants of the xt1526 all shipped with the exact same firmware builds/ROMs.

Abtway, let me know which stock build you device on. Depending on your choice, I have updater zips for your bootloader & partition index.

Here is a link to [MENTION=7313305]Buzbee2[/MENTION]'s Stock 5.1.1 & 6.0 builds for the xt1526. https://xdaforums.com/moto-e-2015/cdma-development/stock-xt1521-gsm-xt1526-cdma-t3342789/page19

If you want an OEM Stock 5.0.2 or 5.1 build, I can send you a link.
[E 2015 Original Android Development] FanboyStudios:
Do the Lollipop builds have the famous memory leak?
[E 2015 Original Android Development] MotoJunkie01:
The 5.0.2 builds both have the memory leak. The bug was patched with the initial release of Stock 5.1.

The 5.0.2 and 5.1 builds are available in either fastboot flashable factory firmware packages or in TWRP flashable ROM zip installers.

Also, the builds are all available in pure unmodified stock, or in debloated, deodexed, pre-rooted builds.

This site includes some of the xt1526 factory firmware packages. https://firmware.center/firmware/Motorola/Moto E (2nd gen-2015)/Stock/XT1526/
[E 2015 Original Android Development] Alex230799x:
Before flashing the updater, I could install Lineage OS 14.1 or any custom rom, after flashing, and in no custom rom it gives me signal or use the dialer, how can I solve this? I have my backup of the rom Stock 6.0 but I want to use a custom rom with normality.
[E 2015 Original Android Development] WarpedJoker:
Hey, for some reason I am unable to get LTE service on anything other than the original stock version. Before I flashed this modem I was able to use custom ROMs and data worked, but I only got 3g or 1x signal. After flashing this modem if I'm on my original Nandroid backup (5.0 something I believe) I get LTE signal and all is well. But if I'm on a custom ROM it says insert sim. I finally got buzbee2's stock 6.0 ROM working, but again ... I'm stuck with just 3g or 1x...

Before I flashed 6.0 stock I went to my nandroid backup and did a prl and data profile update so I know that's not it.

I don't know what else to do...

Also, signal fades and goes out frequently. I can leave my phone on the table untouched and watch the signal go from very low to very high then back down and then off for a second. Then after a few minutes, it will stay strong for an hour or so, then it goes crazy again. I use google voice for texting and if i am trying to have a conversation while it's acting up like that I will send a message then have to go back up to see if any new texts were sent before mine went through because even though its delayed they show in the correct order. very frustrating.

(PS this did it while on a custom rom before flashing this modem update as well. It was the reason I updated modem in the first place.)
[E 2015 Original Android Development] MotoJunkie01:
Make your your partitions are updated to the most current version. (Actually update to [MENTION=7313305]Buzbee2[/MENTION]'s 6.0 partitions with his partition updater) Then after flashing the custom ROM of your choice, boot into fastboot mode, connect to your PC, open a command window and execute these commands:

fastboot erase modemst1

fastboot erase mofemst2

fastboot erase carrier

Upon reboot, edit your APN configs that support your carrier's LTE & MMS params.

By the way, who is your carrier?
[E 2015 Original Android Development] WarpedJoker:
I'm on Freedompop

And what do you mean by edit my apn configs? is that the *#4636#* menu?

I have not found any other APN settings. Only menu i found thats close to what others have said about apn on google was settings - more - cellular networks ... but only options i have there are: data roaming slider, Preferred network type (LTE, 3G, 1x, Global) LTE is selected, System Select (Home Only or Automatic), and CDMA subscription ( RUIM/SIM and NV)

---------- Post added at 01:31 AM ---------- Previous post was at 12:52 AM ----------

Ok, Nevermind. I ran the fastboot commands and now LTE is on. But I have another question... The speed of the network is the same as it was before. I'm downloading another speed tester to make sure but I got .5 Mbps download and 1.1 Mbps up. Prior to running these commands, I got 1.17 Mbps down and 1.0 up.

-update-

Signal strength in Phone info Menu is -108 dBm 32 asu (don't know what that means... lol but the bar looks almost full)

Speedcheck pro DOWN : .065 Mbps UP 1.25 Mbps

Speedtest by Ookla DOWN 1.05 Mbps UP 1.09 Mbps

Are these LTE speeds? I honestly never checked before the problems started, but I do know while my status bar said 3g I got speeds very near these, sometimes higher.

Thank you for your help moto
[E 2015 Original Android Development] hydroman202:
I have a sprint xt1526, but im currently using another phone for better coverage. My question is, does this ported modem provide decent coverage for around rolla mo 65401? If it does i may just switch back to it.
[E 2015 Original Android Development] :
Buy me a plane ticket and I'll let you know when I get back in NY, LOL. I think your best bet for finding that out would be to either install it and see how it goes, or look at a coverage map for your carrier.
[E 2015 Original Android Development] WarpedJoker:
Hey [MENTION=7383447]MotoJunkie01[/MENTION] If I want to go back to before I flashed this baseband updater, what is the best way to do that? I have tried to live with stock 6.0 from buzbee2 but apps are not installing on my sd card like they were in slim7 ... it seems like 6.0 is internal first and maybe, just maybe a few files from each app gets put on sd card (Even though I have it formatted as internal).

When I flash a custom rom it says no sim detected. I have tried your MVNO slayer, i have tried all the fastboot comands to config carrier and everything... but nothing is working. So my hope is I can revert back to before this baseband and see if it lets me flash custom roms again.

Im on freedompop service device is xt1526 Type M1092 (it originally said boost when i first received it from freedompop)

I have updated bootloader 6.0 partitions from buzbee2

and your baseband 6.0.1

I have not flashed anything else except custom roms. kernel should be stock I guess.

Any help would be great
[E 2015 Original Android Development] hydroman202:
How was this modem ported? Just curious. Maybe someone could post a tutorial or something.
[E 2015 Original Android Development] hydroman202:
Hello, i was wondering, how did you port the modem from that device to the xt1526? The reason i ask is because i was curious if was possible to port the modem from the att variant of this model, (i think there is one, i could be wrong), to the sprint xt1526 and in that manner i would not be losing signal when traveling as much. (I am not sure if this is even possible, but i figured it would not hurt to ask). Anyways, i appreciate your time. Thanks!
[E 2015 Original Android Development] MotoJunkie01:
The xt1548 (Moto G3) and xt1526 (Moto E2) are both equipped with the msm8916 baseband radio. As to your question of porting the AT&T baseband to the xt1526, it would not be feasible or in any way productive. The Sprint/Virgin/Boost variant of the xt1526 cannot be used on domestic GSM networks due to carrier implemented network restrictions. So flashing a GSM configured radio to this device would likely result in a complete loss of signal.
[E 2015 Original Android Development] WarpedJoker:
How can I flash just the modem or baseband from stock android that was originally on my device? (I want to undo flashing this baseband basically)

can I just flash the modem and fsg files from a stock firmware with fastboot/adb since you said that is all that was included in this updater?
[E 2015 Original Android Development] MotoJunkie01:
Yes. Extract NON-HLOS.bin and fsg.mbn from desired firmware package. Place these files in your PC's fastboot/adb directory, connect device to your PC with micro USB cable, open a command window in your fastboot directory and:

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot oem fb_mode_clear

Reboot your system. Done.
[E 2015 Original Android Development] MotoJunkie01:
This will effectively overwrite this modem and replace it with the desired modem version.
[E 2015 Original Android Development] WarpedJoker:
Thanks!
[E 2015 Original Android Development] MotoJunkie01:
No problem. I'm in the process now of creating TWRP flashable basebands of all versions from Android 5.0.2 and up.
[E 2015 Original Android Development] WarpedJoker:
Well crap, now I'm back to my no LTE problem. I'm on slimrom, and I didn't notice the problem because when on wifi it doesn't show mobile connection... I have tried fastboot erase like you said in a previous post but it still only 3g, 1x or off. And it goes frequently between the three.

Any other suggestions?

ps service in my area is fine. I hardly ever saw 3g before I switched to a custom ROM. And I can't go back to stock. I like slim7 way too much. :(
[E 2015 Original Android Development] MotoJunkie01:
Very possibly this could be a result of your telephony settings (Preferred Network, APN, etc). Please give me a little more information and we should be able to get your 4G/LTE back to normal. Please provide your:

(1) Carrier (Virgin, Boost, Sprint, etc.);

(2) Type of plan (prepaid or contract);

(3) Go to your dialer, dial *#*#4636#*#*, and ensure your Preferred Network is LTE/CDMA autoPRL;

(4) Go to Settings, find Mobile Networks, Access Point Names, and provide me with your APN configuration (screenshots will suffice);

Thanks.
[E 2015 Original Android Development] WarpedJoker:
I'm sorry it took so long to get back, We're short staffed at work so I've been working crazy hours.

1) Carrier is FreedomPop Sprint MVNO (Purchased from FreedomPop)

2) I don't know how to classify the type of plan, its free =)

3) LTE/CDMA autoPRL was in fact selected.

4) Ok, ScreenShots

Also prior to switching to slim7 while still on stock I went ahead and did a PRL update because I read that you could not do that on custom ROMs and I wanted to make sure I covered all my bases.

Whats weird is I thought the APN was my problem because FreedomPop was not selected... however, when I select that option it acts like its going to switch but then changes back to default. So I changed the settings of the default to match FreedomPops settings and it went to the CDMA option. Which was still on 3g or 1x or off completely.

Anyways I appreciate your help tremendously. I would be lost without most of your posts lol
[E 2015 Original Android Development] MotoJunkie01:
Try this: revert back to a stock build, like you done when updating your PRL/Data Profiles. Use stock dialer and dial ##72786# and then select "YES" once you are prompted in the SCRTN menu. Your device will reboot and go through an activation sequence, as though the device were brand new. Once the stock ROM reboots, your 4G/LTE should return like normal.

Now you are free to flash your custom ROM of choice. I meant to ask also, when you fastboot flashed your NON-HLOS.bin and fsg.mbn, from what version firmware did you extract those files?
[E 2015 Original Android Development] WarpedJoker:
It was from Android 5.1 from firmware.center - XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.12_cid9_subsidy-DEFAULT_CFC.xml