IMEI Unknown, phone wont see any SIM card, phone is unlocked - Motorola One Questions & Answers

Hey everyone, I put a sim card in my Moto One (unlocked bootloader, carrier unlocked, not stock, rooted) and it wont detect the sim card. Is there any way to fix this? My phone wont even show an IMEI number.

Phelipe.mpbr said:
Hey everyone, I put a sim card in my Moto One (unlocked bootloader, carrier unlocked, not stock, rooted) and it wont detect the sim card. Is there any way to fix this? My phone wont even show an IMEI number.
Click to expand...
Click to collapse
Try flash from stock firmware
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my perry_f using XDA Labs

Related

[Q] Need help - No signal

I had a problem with a custom rom on my xt1023 so I restored it and installed the official 4.4.4 rom but since the installation, my phone doesn't detect any mobile signal even with my sim card installed in the phone. I tried to restore it and reinstall the rom multiple times but without any success. If someone could help me, it would be really appreciated!
Thanks
Did you try erasing modemst1 and modemst2 ? Try this:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
Now, try flashing the modem from your stock 4.4.4 ROM
fastboot flash modem NON-HLOS.bin
Reboot now.
shanmukhateja said:
Did you try erasing modemst1 and modemst2 ? Try this:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
Now, try flashing the modem from your stock 4.4.4 ROM
fastboot flash modem NON-HLOS.bin
Reboot now.
Click to expand...
Click to collapse
I just tried it but my phone still stays that I have no signal.
I don't know if it changes something but I'm from Canada and the only stock rom that I found is US.
Btw, thx for the help
noaaam said:
I just tried it but my phone still stays that I have no signal.
I don't know if it changes something but I'm from Canada and the only stock rom that I found is US.
Btw, thx for the help
Click to expand...
Click to collapse
Do you have the single sim variant>?
TheDj408 said:
Do you have the single sim variant>?
Click to expand...
Click to collapse
Yes, I only have one sim port
Sim Card
noaaam said:
Yes, I only have one sim port
Click to expand...
Click to collapse
Did you ever fix the problem? If so, how?

Stock rom for xt1526

Connected to freedompop with the sprint version, flashed cm13, runs fine, but the phone number is wrong and I cannot make any calls to it.
My thought is to update prl and profile, which i cannot do in cm13. So I thought if i go back to 5.1.1 that would do it.
I cannot seem to find a stock specifically for my phone. If I can use a diff model rom for it, fine, but no clue which one that is.
Help!
I realize this isn't the answer you are looking for, but AFAIK, FreedomPop phones only use data to make calls (via the messaging app). The number you are assigned in About Phone>Status is only used to get you on the network to receive data. I know you can pay for "Premium Voice" that is supposed to make calls over cellular (and not data) but from what I have read, this is for outgoing calls only. Also, while the phone number in About Phone might be used to make the premium voide call, FreedomPop will put in forwards so that it looks like the call is coming from your regular FreedomPop number. Calls can't be received to this About Phone number. Here is a forum posting that mentions it: https://forums.freedompop.com/discussion/13935/cant-receive-calls
TL;DR - As long as your data connection works, the phone number in Settings>About Phone>Status is meaningless.
PS - I could be completely wrong about this!!
monkey3ddd said:
Connected to freedompop with the sprint version, flashed cm13, runs fine, but the phone number is wrong and I cannot make any calls to it.
My thought is to update prl and profile, which i cannot do in cm13. So I thought if i go back to 5.1.1 that would do it.
I cannot seem to find a stock specifically for my phone. If I can use a diff model rom for it, fine, but no clue which one that is.
Help!
Click to expand...
Click to collapse
Idk what the latest version of the Moto E XT1526 (sprint) firmware is, but I flashed Build LP123.29-18.S.11 for Boost and it works fine on my Sprint XT1526 running on Ring Plus. I got it here:
http://firmware.center/firmware/Motorola/Moto E (2nd gen-2015)/Stock/XT1526/
XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.11_cid9_subsidy-DEFAULT_CFC.xml.zip
I flashed it manually by using these instructions:
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 oem config carrier spr
fastboot oem fb_mode_clear
That bootloader is version 80.0F. I do not know if that is the most recent bootloader version or not. If you have a later version of the bootloader - YOU SHOULD NOT FLASH A LOWER VERSION OF THE PARTITION TABLE (gpt.bin) OR THE BOOTLOADER (bootloader.img).
BEWARE - you should NOT try to downgrade the partition table or the bootloader. You should also never try to flash a partition table that is the incorrect version for the bootloader you are running!!! Doing so will either fail or result in a hard brick!!!!
Also, there is a file called MVNO Slayer that I installed to get free tethering on Ring+. Not sure if it would help your issue or not:
http://forum.xda-developers.com/mot...t/flashable-lte-fix-moto-e-6-x-boost-t3290719
I would try installing the MVNO Slayer first and see if that corrects your issue.
As was already mentioned, a device active on FreedomPop doesn't have an actual phone number. You need to either have the FreedomPop app installed, or use an alternative such as Hangouts Dialer. If you have root, you can extract the user name and password from the FreedomPop data (search for FreedomPop Google Voice integration for instructions) and enter them in the hidden SIP settings, which you can access using an app like Activity Launcher or AnyCut.. You would then be able to make and receive SIP calls using your FreedomPop number without having the FreedomPop app installed, but you wouldn't be able to send or receive SMS.
Thanks all, it was the freedompop app issue, never realized that, now I feel stupid.

Radio & Bootloader zip

As the title says.
Does anybody have any updated Radio / bootloader zips that I can flash via TWRP ?
I have an old Moto E Condor and I can't get the phone to recognize the Sim so was wondering if updating the radio / bootloader would help ?
I'm running out of ideas.
I have tried Android 6 & 7 tried different Sims.
I'm not sure how I would find out if it's a hardware issue rather than software ?
Any ideas ?
Thanks
Check this link for Radio file
https://forum.xda-developers.com/devdb/project/dl/?id=13877
I didn't got what bootloader you are talking about. But if you want latest twrp then check this link
https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Ankit_29 said:
Check this link for Radio file
https://forum.xda-developers.com/devdb/project/dl/?id=13877
I didn't got what bootloader you are talking about. But if you want latest twrp then check this link
https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Click to expand...
Click to collapse
Thanks mate.
I will give it a go
I had the same problem with my condor ,but flashing the "radio files" didn't help the case ,it always failed in my case ,so the best advice I can give you is to not flash isolated radio files ,but to backup your data and flash stock ROM for your device,trust me it'll save you a lot of headache
Akshay_92 said:
I had the same problem with my condor ,but flashing the "radio files" didn't help the case ,it always failed in my case ,so the best advice I can give you is to not flash isolated radio files ,but to backup your data and flash stock ROM for your device,trust me it'll save you a lot of headache
Click to expand...
Click to collapse
Thanks for that info.
You say that you had the same problem? Have you sorted it out now ?
When you flashed the stock ROM
Did you have to do this via fastboot ??
Thanks again
johnhux7 said:
Thanks for that info.
You say that you had the same problem? Have you sorted it out now ?
When you flashed the stock ROM
Did you have to do this via fastboot ??
Thanks again
Click to expand...
Click to collapse
Yes,my device is good as new,I'm writing this message from it so haha...you can find the appropriate stock ROM to flash here
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
If you don't know which ROM to download, got to your phones settings >about phone>build number
And download the specific ROM with that build number,now be absolutely sure to not flash a KitKat ROM on a device that was upgraded to lollipop earlier, its absolutely essential as it 100% will brick your device,
As for your question, yes you will need to be in fastboot to flash the ROM,and the program that you'll need to flash the ROM with is called mfastboot-v2 you can find it here
https://forum.xda-developers.com/general/rooting-roms/using-mfastboot-exe-to-unbrick-motorola-t3203518
Now after downloading both the ROM and mfastboot ,extract both of them into the same folder of your PC ,after doing that ,go into that folder and hold shift+right mouse key and select "open new command window here" from the dialogue box ,now assuming that you have downloaded the drivers for your phone , switch off your phone ,go into mfastboot mode by holding power key + volume down key for about 5-7seconds, now connect your phone to the PC with the help of USB cable and in the command window type "mfastboot devices" if everyw is done correctly it will show your device's name in an alphanumeric format under "list of devices" after that follow these commands in the ORDER! that they are written and you will be good to go :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE:- number of sparsechunk files may be different for your version (check the files extracted from the ROM inside the same folder to see the order of numbers) so if the numbers are like 0,1,2,3,4 flash them in that order ,I have named it 1,2,3 in the command above for illustrations, good luck if you will do this correctly, you'll be back to a facotory version of your phone,with the imei problem fixed , another thing though, you'll lose your custom recovery so after you flash this stock ROM ,you'll have to flash the custom recovery again,
Cheers!!
Akshay_92 said:
Yes,my device is good as new,I'm writing this message from it so haha...you can find the appropriate stock ROM to flash here
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
If you don't know which ROM to download, got to your phones settings >about phone>build number
And download the specific ROM with that build number,now be absolutely sure to not flash a KitKat ROM on a device that was upgraded to lollipop earlier, its absolutely essential as it 100% will brick your device,
As for your question, yes you will need to be in fastboot to flash the ROM,and the program that you'll need to flash the ROM with is called mfastboot-v2 you can find it here
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
Now after downloading both the ROM and mfastboot ,extract both of them into the same folder of your PC ,after doing that ,go into that folder and hold shift+right mouse key and select "open new command window here" from the dialogue box ,now assuming that you have downloaded the drivers for your phone , switch off your phone ,go into mfastboot mode by holding power key + volume down key for about 5-7seconds, now connect your phone to the PC with the help of USB cable and in the command window type "mfastboot devices" if everyw is done correctly it will show your device's name in an alphanumeric format under "list of devices" after that follow these commands in the ORDER! that they are written and you will be good to go :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE:- number of sparsechunk files may be different for your version (check the files extracted from the ROM inside the same folder to see the order of numbers) so if the numbers are like 0,1,2,3,4 flash them in that order ,I have named it 1,2,3 in the command above for illustrations, good luck if you will do this correctly, you'll be back to a facotory version of your phone,with the imei problem fixed , another thing though, you'll lose your custom recovery so after you flash this stock ROM ,you'll have to flash the custom recovery again,
Cheers!!
Click to expand...
Click to collapse
Thanks so much for taking the time to write this for me.
I'm new to using fastboot I got spoiled by using ODIN with Samsung whist I was learning.
Just one question.
Do you put in each of those commands and press enter after each one ?
johnhux7 said:
Thanks so much for taking the time to write this for me.
I'm new to using fastboot I got spoiled by using ODIN with Samsung whist I was learning.
Just one question.
Do you put in each of those commands and press enter after each one ?
Click to expand...
Click to collapse
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one
Sent from my Moto G (4) using Tapatalk
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
Akshay_92 said:
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one ...It's alright man,we all are new to some stuff at one point,do let me know if you come into a hiccup
Cheers!
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one
Click to expand...
Click to collapse
I though so.
Was just checking.
I'm going to have some fun doing this
Love learning some thing new
The Moto is my spare phone so I can practice on that before getting stuck into fastboot on my Honor 8
johnhux7 said:
I though so.
Was just checking.
I'm going to have some fun doing this
Love learning some thing new
The Moto is my spare phone so I can practice on that before getting stuck into fastboot on my Honor 8
Click to expand...
Click to collapse
[emoji1] yep absolutely,
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
[emoji1] yep absolutely,
Click to expand...
Click to collapse
Thank you so much for sharing your knowledge.
It's what I love about this XDA community
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
ramsut said:
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
Click to expand...
Click to collapse
Flash stock/custom ROM
ramsut said:
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
Click to expand...
Click to collapse
Hmm....Well this is certainly not professional and quite unfortunate,on the part of the service center employees,but since I assume that it's no longer under warranty and they won't take back the Devi because it's unlocked now and also because they won't take responsibility for it ,the best you can do is flash stock ROM,I have explained that earlier in this thread ...
Cheers!! And let me know how it went
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
Hmm....Well this is certainly not professional and quite unfortunate,on the part of the service center employees,but since I assume that it's no longer under warranty and they won't take back the Devi because it's unlocked now and also because they won't take responsibility for it ,the best you can do is flash stock ROM,I have explained that earlier in this thread ...
Cheers!! And let me know how it went
Click to expand...
Click to collapse
I got the SIM working.
Followed your instructions.
Got the phone back to stock
All good thanks for your help
John

Lost SIM Card Detection and Signal after reboot

Hello everyone, after unlock procedure and install global stable 9.5.3.0, i lost sim card detection and no signal.
I have a routine to make sim card detectable and signal on. (I have a rooted rom, and unlocked my phone)
First step :
Connect phone with USB
On pc with adb cmd :
adb shell
su
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
Reboot the phone
At this point i lost IMEI (IMEI 0) but my SIM card is detected.
Second step :
put phone on fastboot mod
On pc fastboot cmd :
fastboot flash modem NON-HLOS.bin
Start phone
Third step :
On pc adb cmd :
adb shell
su
setprop sys.usb.config diag,adb
With QPST on PC, i restore a qcn file found here androidfilebox.com/app/redmi-5-plus-modem-firmware , MEG7 modem version.
Reboot the phone.
Here, SIM card detected and Signal ON, so all is OK.
BUT Fourth step :
When i reboot the phone , i get back to no sim card detected, and i have to repeat the process. :s
So my question is how could i keep my settings and get full use of my phone even if i reboot...
Sorry for my english, i'm trying my best here
i have the same issue on my Zuk Z2, but i haven't make it;
if you could read chinese, maybe this wil be helpful for you.
club.lenovo.com.cn/thread-4224052-1-1.html
Still need help
Aaaaaand still need help
Dini62 said:
Hello everyone, after unlock procedure and install global stable 9.5.3.0, i lost sim card detection and no signal.
I have a routine to make sim card detectable and signal on. (I have a rooted rom, and unlocked my phone)
First step :
Connect phone with USB
On pc with adb cmd :
adb shell
su
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
Reboot the phone
At this point i lost IMEI (IMEI 0) but my SIM card is detected.
Second step :
put phone on fastboot mod
On pc fastboot cmd :
fastboot flash modem NON-HLOS.bin
Start phone
Third step :
On pc adb cmd :
adb shell
su
setprop sys.usb.config diag,adb
With QPST on PC, i restore a qcn file found here androidfilebox.com/app/redmi-5-plus-modem-firmware , MEG7 modem version.
Reboot the phone.
Here, SIM card detected and Signal ON, so all is OK.
BUT Fourth step :
When i reboot the phone , i get back to no sim card detected, and i have to repeat the process. :s
So my question is how could i keep my settings and get full use of my phone even if i reboot...
Sorry for my english, i'm trying my best here
Click to expand...
Click to collapse
Read you message.
In reality I never went through something like this on my note 3. My best guess the qcn file you used is not compatible and efs may be corrupted too.
Many users were facing issues like this so I made a thread to help them. Some users reported a permanent fix while some were never able to get it to work.
Possible fix:
Find a backup of modemst1 modemst2 and fsg from another user if he/she may be willing to share.
Flash the files using fastboot command.
Fastboot flash modemst1 modemst1 and so on.
And then change IMEI and Mac address manually.
Worst case scenario:
You may need a motherboard replacement if nothing works.
But I think it is possible that your efs partition as a whole is corrupted.
adb shell
su
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
These command erase the modemst1 and modemst2 and fsg partition that makes up the efs. What you need is these three partitions from someone else device that are not corrupt and flash them on your device.
For anymore help contact me on:
Telegram - Archit9169
WhatsApp - 9169834624
Thanks to answer, i'm gonna try to get those partitions, it could be hard
I'm facing very similar issue after an ota update. However, I get the sim detected on a simple reboot for a few minutes. Please update if the solution worked.
Hello. I'm facing similiar issue on MEG7 vince. I can't restart my phone because every time loses the baseband and sim detection. My rutine to get back is:
1.- Flash via trwp a shared good one similar EFS partition backup. With this step I recover the baseband and the sim detection BUT the status of SIMs are "radio off" don't have signal and can't do calls. (the IMEI remains despite the lost baseband)
2.- Flash via QPST a xqcn backup ( I founded 2 files on google). Reboot the phone. Sometimes the signal and baseband come back without problem BUT sometimes I back to the beggining, without baseband and sim detection. It's really annoying.
Now I have obtained a modemst1 modemst2 and fsg images of a identic model. My question: how to flash it? with twrp? fastboot? adb?
Thanks for the suggestions.
I'm facing the same thing but only on 2nd sim slot. The 1st slot work flawlessy. Switching sim card doesn't matter.
It recognizes the operator and imei but signal is gone!!! I've tryed everything, flashing miui 9.6.4, 8.8.2, via fastboot and test point!! Relocking bootloader... flashed 00000080_0.xqcn as well.
nothing has worked.
I haven't tryed your solution, can you share all files needed? Thanks.
Anyone can help me?
I don't think it's hardware issue, because Sim's operator is recognized... But signal strength always show -1dbm 99 asu, whatever I do in network type (global,LTE etc..) and only on 2nd slot.
cristhian7cz said:
Now I have obtained a modemst1 modemst2 and fsg images of a identic model. My question: how to flash it? with twrp? fastboot? adb?
Click to expand...
Click to collapse
Hello cristhian7cz , i still have this issue.
With your files, u could try Archit9169 solution :
"
Possible fix:
Find a backup of modemst1 modemst2 and fsg from another user if he/she may be willing to share.
Flash the files using fastboot command.
Fastboot flash modemst1 modemst1 and so on.
And then change IMEI and Mac address manually.
"
If you have issues, or don't know what to do, may u send me modemst1, modemst2 and fsg files you get ?
tried Archit9169 solution but still no luck
Ohh I'm not alone at least. Had this problem with my 1st simcard slot and so far I didnt find any solutions worked. Re-locking, upgrade and even downgrade, but nope
I hope someone enlighten us
[https://forum.xda-developers.com/re...xtracttarfork-process-error255-t3656328/page2
QUOTE=Rayquaza;77634878]Ohh I'm not alone at least. Had this problem with my 1st simcard slot and so far I didnt find any solutions worked. Re-locking, upgrade and even downgrade, but nope
I hope someone enlighten us[/QUOTE]
Bro is modem issue,i solve it with flashing NON-HLOS.bin extract from rom i am using when thing goes wrong,u can try with twrp but i use fastboot
Sent from my Redmi 5 Plus using XDA Labs
XavierBrian said:
[https://forum.xda-developers.com/re...xtracttarfork-process-error255-t3656328/page2
QUOTE=Rayquaza;77634878]Ohh I'm not alone at least. Had this problem with my 1st simcard slot and so far I didnt find any solutions worked. Re-locking, upgrade and even downgrade, but nope
I hope someone enlighten us
Bro is modem issue,i solve it with flashing NON-HLOS.bin extract from rom i am using when thing goes wrong,u can try with twrp but i use fastboot
Sent from my Redmi 5 Plus using XDA Labs
Click to expand...
Click to collapse
I'm running AOKP 8.1, do I need to flash that file from extracted rom I'm running at?
Rayquaza said:
I'm running AOKP 8.1, do I need to flash that file from extracted rom I'm running at?
Click to expand...
Click to collapse
Yeah u should! extract the rom look for that hlos thang
Sent from my Redmi 5 Plus using XDA Labs
i'm still trying to fix my phone.
if someone has a backup from modemst1 modemst2 and fsg, i'm searching for them
derekk75j said:
I'm facing the same thing but only on 2nd sim slot. The 1st slot work flawlessy. Switching sim card doesn't matter.
It recognizes the operator and imei but signal is gone!!! I've tryed everything, flashing miui 9.6.4, 8.8.2, via fastboot and test point!! Relocking bootloader... flashed 00000080_0.xqcn as well.
nothing has worked.
I haven't tryed your solution, can you share all files needed? Thanks.
Click to expand...
Click to collapse
Have you found a solution of your 2nd sim slot problem? I have the same problem
No, haven't tried yet. I would like follow this guide
https://youtu.be/PvvcQZfeqNI, but using a modem backup meg7 version (xqcn). But i have to repair my PC first. What did you try so far?
proyectos3d said:
Have you found a solution of your 2nd sim slot problem? I have the same problem
Click to expand...
Click to collapse
I can't believe!! I was on arrow os pie: i flashed miui am founded here
and then magisk 17.3 and voilà: my 2nd slot sim has back again, and works flawlessly!!

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

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?
fatmanSings said:
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?
Click to expand...
Click to collapse
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.
gibberishman said:
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.
Click to expand...
Click to collapse
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
fatmanSings said:
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
Click to expand...
Click to collapse
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.
gibberishman said:
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.
Click to expand...
Click to collapse
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?
fatmanSings said:
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?
Click to expand...
Click to collapse
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.
gibberishman said:
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.
Click to expand...
Click to collapse
How long does it usually take for the firmware files to get dumped? A month or so?
fatmanSings said:
How long does it usually take for the firmware files to get dumped? A month or so?
Click to expand...
Click to collapse
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.
gibberishman said:
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.
Click to expand...
Click to collapse
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
fatmanSings said:
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
Click to expand...
Click to collapse
You did "fastboot oem config carrier retus" ?
gibberishman said:
You did "fastboot oem config carrier retus" ?
Click to expand...
Click to collapse
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?
fatmanSings said:
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?
Click to expand...
Click to collapse
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.
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
DeSlaye said:
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
Click to expand...
Click to collapse
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.
fatmanSings said:
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.
Click to expand...
Click to collapse
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.
Ascertion said:
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.
Click to expand...
Click to collapse
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
fatmanSings said:
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
Click to expand...
Click to collapse
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.

Categories

Resources