Question e-sim support on Edge+ (2023) from Boost Mobile

Search This thread

fatmanSings

Member
Jun 10, 2023
17
1
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1

Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
 
Last edited:

gibberishman

Member
Jun 9, 2023
28
7
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1

Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
 

fatmanSings

Member
Jun 10, 2023
17
1
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
 

gibberishman

Member
Jun 9, 2023
28
7
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
 

fatmanSings

Member
Jun 10, 2023
17
1
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
Thanks for your help!

The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
 

gibberishman

Member
Jun 9, 2023
28
7
Thanks for your help!

The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
 
Last edited:
  • Like
Reactions: fatmanSings

fatmanSings

Member
Jun 10, 2023
17
1
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?

I tried to change the oem config carrier to retus and that didn't work either
 
Last edited:

gibberishman

Member
Jun 9, 2023
28
7
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?

I tried to change the oem config carrier to retus and that didn't work either
You did "fastboot oem config carrier retus" ?
 

gibberishman

Member
Jun 9, 2023
28
7
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?

Do you think I can flash to the RETEU Edge 40 Pro firmware?
You may be able to root the device and change the value. Don't thing there's a file you can flash to override the carrier. I wouldn't recommend flashing the EU firmware. The hardware is slightly different, don't know if it would affect anything.
 

DeSlaye

Senior Member
May 17, 2016
72
16
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
 

fatmanSings

Member
Jun 10, 2023
17
1
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.

Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
 

Ascertion

Senior Member
Mar 29, 2012
3,498
1,507
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.

Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.

echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear

pause
fastboot reboot
exit

EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
 

fatmanSings

Member
Jun 10, 2023
17
1
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.

echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear

pause
fastboot reboot
exit

EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
 

Ascertion

Senior Member
Mar 29, 2012
3,498
1,507
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
No, when I go to the unlock site it just gives me a 404 error page after submitting my unlock token. I gave up and decided to just use the Boost firmware. The device is sim-unlocked and supports AT&T/T-Mobile.
 

fatmanSings

Member
Jun 10, 2023
17
1
No, when I go to the unlock site it just gives me a 404 error page after submitting my unlock token. I gave up and decided to just use the Boost firmware. The device is sim-unlocked and supports AT&T/T-Mobile.
Their tool is broken, try this method, it worked for me:

Post in thread '[Guide]Un/locking Motorola Bootloader' https://forum.xda-developers.com/t/guide-un-locking-motorola-bootloader.4079111/post-88653223

Make sure you're logged in before doing that, let me know if it works out.
 
  • Like
Reactions: DeSlaye

DeSlaye

Senior Member
May 17, 2016
72
16
  • Like
Reactions: norcalmike702

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I want to try this. Which RETUS firmware did you use? Is everything (including NFC + bank apps) working?
    RETUS and everything works flawlessly probably even better. Banking apps/NFC you need Universal SafetyNet Fix by displax, enable Zygisk in Magisk and then place Banking Apps or any app that complains about root onto the DenyList in Magisk. Then for Netflix/Hulu/Disney+ etc you need liboemcrypto disabler module and also put them on DenyList. But MagiskHideProps can enable eSim Menu on BOOST firmware as well. Then there is RETAIL firmware which has eSim Menu by default without any extra sorcery and is basically the same as RETUS and everything just works as well. All confirmed and tested by yours truly.
    1
    Screenshot_20230926-213642.png
  • 1
    Thanks for your help!

    The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
    The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
    1
    No, when I go to the unlock site it just gives me a 404 error page after submitting my unlock token. I gave up and decided to just use the Boost firmware. The device is sim-unlocked and supports AT&T/T-Mobile.
    Their tool is broken, try this method, it worked for me:

    Post in thread '[Guide]Un/locking Motorola Bootloader' https://forum.xda-developers.com/t/guide-un-locking-motorola-bootloader.4079111/post-88653223

    Make sure you're logged in before doing that, let me know if it works out.
    1
    Their tool is broken, try this method, it worked for me:

    Post in thread '[Guide]Un/locking Motorola Bootloader' https://forum.xda-developers.com/t/guide-un-locking-motorola-bootloader.4079111/post-88653223

    Make sure you're logged in before doing that, let me know if it works out.
    This is what I did too and how I unlocked my bootloader. Tempted to flash retail but I'm worried about breaking something,
    1
    I've tried to flash to both the RETAIL and RETEU software channels with my US edge+.

    It works and even activates eSIM for the boost variant, however PIN unlock will NOT work. It will take the PIN just fine and enroll fingerprints, but only fingerprint unlock works. After reboot PIN is required and the PIN will always be invalid even though I made sure to type it in correctly.

    I tried flashing both the radio + system or just system and the error shows up both ways.
    Flashing back to RTWO_G_T1TR33.43_48_21_subsidy_BOOST_DISH_regulatory_DEFAULT_cid50_CFC will restore all functionality (but take away eSIM).
    1
    Interesting thank you! Did you ever try to relock the bootloader after flashing RETAIL? I’ve been debating flashing retail as I really need eSIM support. How did you unlock the phone if PIN didn’t work?

    I don't want to risk relocking the bootloader as the OEM unlocking can be stuck for Moto phones and I'll end up having a brick on my hands.

    If PIN doesn't work I can't unlock the phone after a reboot. So it's useless for me.

    I think there's something up in the system image that breaks the PIN. I tried the following combos:
    * Full flash RETAIL/RETEU: PIN can be set, after going to Settings - Security PIN immediately shows incorrect, cannot enable developer options as PIN is always incorrect
    * Flash BOOST, then flash RETAIL boot.img/vbmeta.img/super.img: PIN can be set, Settings - Security PIN and developer options can correctly recognize the PIN, but once phone is locked PIN is always invalid

    In any case the phone is useless for me if I can't set a PIN. I have to factory reset from fastboot to get access to it again.