I received a used s3 which had stock 4.3 , modem/bootloader mjb, and knox. I rooted, removed knox and installed slim 4.4.4 rom, lean 4.4.4 kernel and latest philz. All running ok
including cell calls to/from, mms, apps and wifi data. Same modem/bootloader (MJB), IMEI available However cellular data will not connect and or transmit/receive using att, phone or lte APN.
Any help/thoughts appreciated?
Have you updated the bootloader and modem to kk?
audit13 said:
Have you updated the bootloader and modem to kk?
Click to expand...
Click to collapse
My research suggested that the modem mjb and bootloader mjb did not have to be updated if cell calls and sms were working. Also I have an older S3 with modem mjb and bootloader mg2 and the same rom and kernel
that was working fine.
??
Can you manually add the APN? Have you tried other KK custom ROMs?
audit13 said:
Can you manually add the APN? Have you tried other KK custom ROMs?
Click to expand...
Click to collapse
I just added an APN, tested and deleted it. I was holding off changing roms because it seems to me that this might be an ATT cell data network registration problem in which the choice of ROM is
irrelevant.
When you added the APN, were you able to connect to ATT?
audit13 said:
When you added the APN, were you able to connect to ATT?
Click to expand...
Click to collapse
Not for data, cell calls and sms work.
Are any APNs present in the phone? With every custom ROM I have installed on a phone (i747m, Atrix HD, Nexus 4, Galaxy Nexus, LG Optimus G), the APN was always automatically added.
audit13 said:
Are any APNs present in the phone? With every custom ROM I have installed on a phone (i747m, Atrix HD, Nexus 4, Galaxy Nexus, LG Optimus G), the APN was always automatically added.
Click to expand...
Click to collapse
Yes, there were att based apns labeled phone, att, lte, broadband, attactivate and two for smarttalk. I have tried the phone, lte and att apns and they all fail.
This is strange that it can't connect the ATT data network. Is ATT's data network functioning properly in your area? Are you able to try your sim in another phone?
audit13 said:
This is strange that it can't connect the ATT data network. Is ATT's data network functioning properly in your area? Are you able to try your sim in another phone?
Click to expand...
Click to collapse
I just tested the ATT data network with another sim and phone. AOK. Unable to easily test with the same sim due to a std/micro sim card mismatch. Will be able to
do that after 6p cdt today.
Weird, I would suggest creating a nandroid backup of your current ROM and try another ROM.
Do you have a link to the ROM you installed?
audit13 said:
Weird, I would suggest creating a nandroid backup of your current ROM and try another ROM.
Do you have a link to the ROM you installed?
Click to expand...
Click to collapse
Here is a link to the main d2lte download page. I downloaded the 7.0 version as my searches showed some instability in later releases .
http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
kwmike said:
Here is a link to the main d2lte download page. I downloaded the 7.0 version as my searches showed some instability in later releases .
http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
Click to expand...
Click to collapse
Will have to hold for now on another rom install due to external issues.
I don't see any assert lines in the ROM's updater-script file. I also noticed that it has been updated since Aug 5.
audit13 said:
I don't see any assert lines in the ROM's updater-script file. I also noticed that it has been updated since Aug 5.
Click to expand...
Click to collapse
Not knowledgeable enough to understand assert impact. Also held off on later version due to thread discussion about instability.
The only thing left to do seems to be trying another ROM. If that doesn't solve the issue, it may be a defective sim card or possible hardware issue.
audit13 said:
The only thing left to do seems to be trying another ROM. If that doesn't solve the issue, it may be a defective sim card or possible hardware issue.
Click to expand...
Click to collapse
Have to go on hold for a while now.
Thanks for the efforts
Any other thoughts/help appreciated!!
If you get it solved, let us know how you did it.
Sorry I couldn't solve the problem for you.
Cheers
Resolved. By removal of lean kernel and extensive correction of ATT registration data. Thanks for the help
Sent from my SGH-I777 using XDA Free mobile app
Related
My phone is unlocked and using a MetroPCS sim card, so I couldn't get the OTA update, even on Wifi. After following the instructions at [Download][Install] 4.3 OTA Update, I no longer have data connection on the phone unless I use wifi.
From what I've read, this usually happens because a modem wasn't flashed, but I assumed that the 4.3 update in that thread had a modem. Even so, I entered stock recovery and flashed the modem from the hidden part of Loserskater's post here. But I still have no data.
Does anyone have any ideas what went wrong or what I can do next? I don't mind rooting if that's what I have to do (I plan on it anyway, but didn't know if I should work on getting data first).
Thanks
mewikime said:
My phone is unlocked and using a MetroPCS sim card, so I couldn't get the OTA update, even on Wifi. After following the instructions at [Download][Install] 4.3 OTA Update, I no longer have data connection on the phone unless I use wifi.
From what I've read, this usually happens because a modem wasn't flashed, but I assumed that the 4.3 update in that thread had a modem. Even so, I entered stock recovery and flashed the modem from the hidden part of Loserskater's post here. But I still have no data.
Does anyone have any ideas what went wrong or what I can do next? I don't mind rooting if that's what I have to do (I plan on it anyway, but didn't know if I should work on getting data first).
Thanks
Click to expand...
Click to collapse
it could be that, you mixed a leaked modem with a different build thus messing with the final official build or update that ATT released last week
wipe everything if thats possible then download the 4.3 firmware from this link http://www.androidfilehost.com/?fid=23212708291680243 and since you are on stock just download it using odin (use this link if you have no idea of how to use odin) http://droidow.com/galaxy-s3-i747-update-with-ucuemj2-android-4-3-leaked/ but on the PDA part use the file you download from the link above (update43.zip) and that will fix your problems
this may or may not work, i have not tested as i have not updated to 4.3 am waiting for devs to update their roms to 4.3 and then i can go with 4.3/rooting
follow instructions carefully since 4.3 for the S3 is like a virus, this update just leads to HARD BRICKS but dont worry just do everything right and things will be fine
hope you have i747 = ATT not i747m = CANADIANS variants
winosxbuntu said:
it could be that, you mixed a leaked modem with a different build thus messing with the final official build or update that ATT released last week
wipe everything if thats possible then download the 4.3 firmware from this link http://www.androidfilehost.com/?fid=23212708291680243 and since you are on stock just download it using odin (use this link if you have no idea of how to use odin) http://droidow.com/galaxy-s3-i747-update-with-ucuemj2-android-4-3-leaked/ but on the PDA part use the file you download from the link above (update43.zip) and that will fix your problems
this may or may not work, i have not tested as i have not updated to 4.3 am waiting for devs to update their roms to 4.3 and then i can go with 4.3/rooting
follow instructions carefully since 4.3 for the S3 is like a virus, this update just leads to HARD BRICKS but dont worry just do everything right and things will be fine
hope you have i747 = ATT not i747m = CANADIANS variants
Click to expand...
Click to collapse
After hunting through all the settings options, I found that I had nothing in the Access Point Names menu under Mobile Networks. I think because I updated with a Metro-PCS sim card in the phone, rather than an ATT one, for whatever reason I didn't get any APN settings.
So after hunting down T-Mobile's and writing them in, I now have Data. Phew!
mewikime said:
After hunting through all the settings options, I found that I had nothing in the Access Point Names menu under Mobile Networks. I think because I updated with a Metro-PCS sim card in the phone, rather than an ATT one, for whatever reason I didn't get any APN settings.
So after hunting down T-Mobile's and writing them in, I now have Data. Phew!
Click to expand...
Click to collapse
nice to know you fixed it :laugh:
Hey guys. I just got a galaxy s3 from virgin mobile SPH-L710 last week and I managed to install cyanogenmod 11 m10 on it. But to go to cm11 m11 asI've recently learned needs the latest bootloader and baseband.
I know there's two threads in the development section on how to get the latest stock nd8 update.
One had a link to download and open in Odin however the link doesn't seem to be good anymore.
The second thread is for the Odin one click full restore but when I run it it fails on aboot.nbm. I've tried using different USB cables too but it doesn't seem to do any good. Any ideads on how else to upgrade?
I can assure you this is false. I have a Virgin Mobile SPH-L710 on baseband MK5 and I am running a nightly build that is newer than M11 and have no issues.
You should be fine with a dirty flash over M10. Just wipe the cache before flashing.
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Erunur said:
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Click to expand...
Click to collapse
My phone came with MK5 on it, when the phones were shipping with 4.3 installed.
To be honest with you, I would disregard the modem/baseband concerns altogether if I were you. These phones do come with KNOX on them and flashing bootloaders and modems is seriously a huge risk. Flashing a bootloader older than the one you are currently on will trip the killswitch and you will have an irreparable hard brick.
The only time I could possibly think considerations with the bootloader would need to be made is if you were looking to flash a rooted stock TouchWIZ ROM that needed newer bootloaders/modems. But, I really can't speak to that, as I am trying to avoid TouchWIZ and am only familiar with AOSP ROMs.
You may need to flash an APN fix in addition to the ROM and GAPPs. I also use @decimalman's custom kernel, the DKP kernel and have no issues. Basically, when I am clean flashing nightlies the order goes like this:
In PhilZ Recovery found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
ROM
GAPPs
Kernel
APN fix
Re-Root system for SuperSU
Reboot
I sent you the link for the APN fix, available in another active VM S3 forum, in your inbox. Download and flash the zip and that should fix any service-related issues you're having.
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Erunur said:
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Click to expand...
Click to collapse
And, you tried flashing all of those with the lateat version of PhilZ recovery?
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Erunur said:
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Click to expand...
Click to collapse
When you're on M11, have you checked in system root --> /etc folder to see if the apns-conf.xml is there? You might tru copying that over from the M10 build.
In the meantime, I'll look into the modem a bit more. The CM forum users all seemed to agree on that as a fix.
Hey all,
I recently picked up a TracFone BYOP Sim Card for my Galaxy S3. My phone is unlocked and the IMEI is clean, so in theory the Sim Card should work. Well, it didn't. At first I thought that the Sim Card itself was faulty. My phone was recognizing it, but I wasn't able to make phone calls or connect to data. After messing with the Sim Card a bit, I realised that the modem/bootloader on my phone was outdated. It was still on the NE4 version.
So, I updated the modem/bootloader to NJ2 (the latest version) and now my phone is reporting no Sim Card at all.. great. Since it was recognized before, I know that my Sim Card slot isn't acting up. I could possibly try using Odin to reset my phone, but there are not any files available for Android 4.4.2 to flash. Other than that, I can't downgrade the modem to my knowledge so it looks like I'm stuck with a broken version.
Help would be greatly appreciated.
~Mario119~
What rom do you have installed?
jason2678 said:
What rom do you have installed?
Click to expand...
Click to collapse
I have the latest build of Matrixzone's CM 13 installed. People report phone calls, texts, and 4G LTE are fully functional on the ROM, so I know that the ROM itself isn't the culprit.
Mario119 said:
I have the latest build of Matrixzone's CM 13 installed. People report phone calls, texts, and 4G LTE are fully functional on the ROM, so I know that the ROM itself isn't the culprit.
Click to expand...
Click to collapse
Gotcha. Sometimes stock roms have issues when they aren't on the firmware they're intended for, but cm is usually pretty universal.
Try a few airplane mode toggles. Sometimes that got the no sim thing to come around for me on the early cm13 builds.
If that doesn't work, consider flashing a cm 12.1 nightly and see if it has the same issue. I'm sure it's getting better, but when I last used it cm 13 want entirely stable yet.
jason2678 said:
Gotcha. Sometimes stock roms have issues when they aren't on the firmware they're intended for, but cm is usually pretty universal.
Try a few airplane mode toggles. Sometimes that got the no sim thing to come around for me on the early cm13 builds.
If that doesn't work, consider flashing a cm 12.1 nightly and see if it has the same issue. I'm sure it's getting better, but when I last used it cm 13 want entirely stable yet.
Click to expand...
Click to collapse
I just tried the Sim Card in another Galaxy S3 (a d2tmo) after reflashing it with a stock Odin image, and it worked. I've tried to flash the 4.3 Odin image on my d2att and it failed, along with the 4.2 Odin image. Does anyone know where I could perhaps find a stock 4.4.2 image?
AT&T never released a stock image past android 4.1.1, and you can't use that. That NJ2 bootloader cannot be downgraded, or you'll have a hard brick. That is why Odin is failing.
I'd still recommend giving enewman's NJ2 stock rom, or a lollipop aosp rom a try. I haven't had much access to this phone for about a month, but I had a lot of no sim troubles with CM 13 back then.
jason2678 said:
AT&T never released a stock image past android 4.1.1, and you can't use that. That NJ2 bootloader cannot be downgraded, or you'll have a hard brick. That is why Odin is failing.
I'd still recommend giving enewman's NJ2 stock rom, or a lollipop aosp rom a try. I haven't had much access to this phone for about a month, but I had a lot of no sim troubles with CM 13 back then.
Click to expand...
Click to collapse
The stock ROM won't work, it still isn't recognizing the Sim Card. It appears that the NJ2 Bootloader screwed with something internally. Since I can't downgrade, what are my options?
Mario119 said:
The stock ROM won't work, it still isn't recognizing the Sim Card. It appears that the NJ2 Bootloader screwed with something internally. Since I can't downgrade, what are my options?
Click to expand...
Click to collapse
Install the Samsung phone info app. Report what it says for bootloader and baseband. Let's make sure of exactly what is on this phone for firmware.
Alternately type this in a terminal or adb shell
Code:
getprop ro.bootloader
getprop gsm.version.baseband
jason2678 said:
Install the Samsung phone info app. Report what it says for bootloader and baseband. Let's make sure of exactly what is on this phone for firmware.
Alternately type this in a terminal or adb shell
Code:
getprop ro.bootloader
getprop gsm.version.baseband
Click to expand...
Click to collapse
Bootloader Version: I747UCUFNJ2
PDA Version: I747UCUFNJ2
CSC Version: I747ATTFNJ2
Baseband Version: I747UCUFNJ2
From the info I've seen, it appears everything matches up.
Does the phone display the correct imei from typing in *#06#? Could the imei be blacklisted?
audit13 said:
Does the phone display the correct imei from typing in *#06#? Could the imei be blacklisted?
Click to expand...
Click to collapse
The IMEI is the same as the IMEI printed in the rear of the device. According to Swappa and IMEIPro.info, the IMEI is not blacklisted anywhere.
I directly updated the Modem/Bootloader from NE4 > NJ1 > NJ2. I rebooted between every update, but I never checked to see if the Sim was recognized on NJ1.
Are you able to try the phone in its current state with another sim card?
audit13 said:
Are you able to try the phone in its current state with another sim card?
Click to expand...
Click to collapse
I tried a spare one that came with the activation kit, no luck. NJ2 definitely did something, unfortunately. Are you able to downgrade just the modem (not the bootloader) without a chance of bricking the phone?
I would not start mixing bootloader and modems as it could cause a brick.
At this point the phone does not work or recognize any sim cards? Was a working sim tested with the phone prior to making this thread?
audit13 said:
I would not start mixing bootloader and modems as it could cause a brick.
At this point the phone does not work or recognize any sim cards? Was a working sim tested with the phone prior to making this thread?
Click to expand...
Click to collapse
Technically, yes. I was on the NE4 modem and the phone recognized the Sim Card, but nothing was working with it. I thought the Sim was broken at that point, so I tried it in another Galaxy S3 and it worked perfectly. So I narrowed the problem down to my phone. I then proceeded to update the modem/bootloader to NJ2. After I updated and turned the phone on, it reported having 'No Sim Card'. I've tested it so far on 2 different ROMs, all of them say the same thing. Something with NJ1/NJ2 must of went wrong regarding the modem. The best part is, I can't Odin my phone back to stock because AT&T never bothered to release a 4.4.2 tar.gz file...
It's also possible that the sim reader is damaged.
audit13 said:
It's also possible that the sim reader is damaged.
Click to expand...
Click to collapse
I suppose it could be, but what about the fact that it recognized the Sim Card using the NE4 bootloader/modem? Perhaps it was working slightly (albeit broken), but changes in NJ2 rendered it completely broken? I just don't want to shell out the money if it isn't necessary, y'know. It'd be a shame if a replaced SIm Card Reader still didn't work, if it turned out to be something on the software-side.
Isn't the sim reader removable? They are cheap on eBay I think.
audit13 said:
Isn't the sim reader removable? They are cheap on eBay I think.
Click to expand...
Click to collapse
It turns out that they are only $6.50 for a brand new Sim Card Reader w/ 2-Day shipping. Might as well give it try, I can only improve from here.
Good luck. Keep us informed. Thanks.
Hi all and a great big up to the developers of XDA. Thank you very much for your time and helps you give, really thank you.
Tonight, I just ask you the problem I encounter with my phone. I have a Samsung Galaxy Note II but quite frankly I do not know if it's a GT-N7100 or SPH-L900.
When I go into Settings "About device"; here is the info I have:
1) Software Version: L900VPUCHO3; Hardware Version: L900.09; Android Version: 4.4.2; Model Number: SPH-L900; Baseband Version: L900VPUCHO3; Kernel Version: 3.0.31-3084104 dpi @ SWHD8903 # 1 Mon Aug 24 5:13:18 p.m. KST 2015; Build Number: KOT49H.L900VPUCHO3
If we stick to these information, the phone is really Galaxy Note II SPH-L900
However, when I use my IMEI number on the site imei.info this is what I like information:
2) Model: N7100 Galaxy Note II
Brand: SAMSUNG
IMEI: TAC: 990002 FCC: 11 SNR: 936743 CD: 9
http://www.imei.info/?imei=990002119367439
So please, tell you what's wrong with this phone and if possible how to go about solving the problem, thank you!
Boot the phone into download/Odin mode to find the model #.
audit13 said:
Boot the phone into download/Odin mode to find the model #.
Click to expand...
Click to collapse
When i boot my phone in download/odin mode, it show this Model: SPH-L900
But please i wanna know why my IMEI number tel that about my phone is GT-N7100
The imei # could have been re-programmed.
Are you getting the imei by dialling *#06#?
audit13 said:
The imei # could have been re-programmed.
Are you getting the imei by dialling *#06#?
Click to expand...
Click to collapse
Yes i got it by diialling *#06#.
But please, it's possible to flash GT-N7100 stock rom on SPH-L900 sprint?
I'm not familiar with the SPH-L900. If the bootlaoder is unlocked, you may be able to flash TWRP and a custom ROM based on a stock n7100 ROM.
If you want to use Odin, you won't be able to flash the n7100 ROM to the L900 because Odin will prevent flashing an n7100 ROM to a phone with an L900 bootloader.
Where did you get the phone?
audit13 said:
I'm not familiar with the SPH-L900. If the bootlaoder is unlocked, you may be able to flash TWRP and a custom ROM based on a stock n7100 ROM.
If you want to use Odin, you won't be able to flash the n7100 ROM to the L900 because Odin will prevent flashing an n7100 ROM to a phone with an L900 bootloader.
Where did you get the phone?
Click to expand...
Click to collapse
I purchased the phone with a friend who brought used usa.
However, how do you think it is possible to flash GT-N7100 sstock rom on SPH-L900?
Also before I forget, even with the official rom my phone I can not activate mobile data because it does not exist in phone so I have to connect on the wifi only.
You may not be able to connect to your cell company because the phone may not support the required frequencies.
Also, the phone is a CDMA phone: http://www.gsmarena.com/samsung_galaxy_note_ii_cdma-5152.php
I don't know of any way to flash a stock N7100 rom onto a L900.
audit13 said:
You may not be able to connect to your cell company because the phone may not support the required frequencies.
Also, the phone is a CDMA phone: http://www.gsmarena.com/samsung_galaxy_note_ii_cdma-5152.php
I don't know of any way to flash a stock N7100 rom onto a L900.
Click to expand...
Click to collapse
Then my phone is good for the trash ... :crying:
Did you compare your cell company's frequencies to the phone?
Did you try to manually add your company's APN settings to the phone for data? Can you make phone calls?
audit13 said:
Did you compare your cell company's frequencies to the phone?
Did you try to manually add your company's APN settings to the phone for data? Can you make phone calls?
Click to expand...
Click to collapse
Yes I can make calls even send messages. By cons, you can not manually add APN data from my operator as this part does not exist in the official rom my phone. My when I installed the custom rom Cyanogenmod 12.0 Nightly, I could put my APN data operator and Internet access via mobile data because this option exists in the CyanogenMod ROM.
Did you try to flash a stock L900 ROM to the phone, root, and add APN?
audit13 said:
Did you try to flash a stock L900 ROM to the phone, root, and add APN?
Click to expand...
Click to collapse
Yes and now that's what is the official rom SPH-L900 that is installed on my phone and I even rooter but still can not add the APN data from my operator as always nonexistent option in Roma .
In addition, there are only three languages (English, Chinese and Spanish) ...
Yes, the Sprint phones lave limited languages. Have you tried morelocale app to add languages?
The APN may be locked because the phone was made for use on Sprint.
What about flashing TWRP and a custom ROM: http://forum.xda-developers.com/note-2-sprint/development
audit13 said:
Yes, the Sprint phones lave limited languages. Have you tried morelocale app to add languages?
The APN may be locked because the phone was made for use on Sprint.
What about flashing TWRP and a custom ROM: http://forum.xda-developers.com/note-2-sprint/development
Click to expand...
Click to collapse
Apparently I bought a bad phone ...
With all these little worries, I admit I am bummed
Don't be bummed. The phone is a good phone and may be perfectly suitable after installing a custom ROM.
One CM, were you able to connect to the data network?
audit13 said:
Don't be bummed. The phone is a good phone and may be perfectly suitable after installing a custom ROM.
One CM, were you able to connect to the data network?
Click to expand...
Click to collapse
Yes, under CyanogenMod 12.0 (Android 5.0.2) I was able to connect with mobile data.
But with Cyanogenmod 12.1 (Android 5.1.) And received my calls emitted out unknown
Maybe try a ROM that is based on the stock Sprint ROM.
audit13 said:
Maybe try a ROM that is based on the stock Sprint ROM.
Click to expand...
Click to collapse
Ok but could you please help me find
If the current ROM is rooted, this might help, although it is a paid version: https://play.google.com/store/apps/details?id=ale.android.apnmanagerwithanimation&hl=en
There may be free apn managers available on the Play store.
This ROM may also work: Maybe this: http://forum.xda-developers.com/not...m-stock-oh3-rooted-deknoxed-deodexed-t3221123
I got the notification today.
guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
Same Here
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
have you saved the 66 mb zip ota update ? can you share it
If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.
sidgallup said:
If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.
Click to expand...
Click to collapse
YES
Welp... today i updated stock ROM to the latest version, after that i unlocked bootloader on Motos website, flashed TWRP, installed LineageOS and coudlnt get signal to connect to GSM, then flashed Resurrection Remix and same problem, everything works except calls, signal bars at at 0, no service.
This reminds me of some issues i had years ago and i needed to flash an older modem for calls to work.
Is anyone else having issues after updating to the latest stock ROM version?
EDIT: just confirmed theres something in the latest OTA that blocks GSM funcionality on custom ROMS, i did the exact same proccess with my brother's phone which is the same as mine, Boost E4, but this time without updating the stock ROM, just went directly to unlocking bootloader out of the box and this time is working perfectly.
I need some help now on how to go back to stock ROM and unlock mine.
It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?
nookin said:
It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?
Click to expand...
Click to collapse
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.
MotoJunkie01 said:
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.
Click to expand...
Click to collapse
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.
nookin said:
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.
Click to expand...
Click to collapse
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.
MotoJunkie01 said:
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.
Click to expand...
Click to collapse
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.
nookin said:
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.
Click to expand...
Click to collapse
Oh okay. That makes things clearer. With Boost Mobile being a Sprint owned subsidiary, and Tello being a Sprint affiliated MVNO, you are correct that with voice being functional, your data connection should likewise work. (Contrary to popular belief, Boost Mobile is not an MVNO and never has been.) I believe that, in your situation, the last OTA is likely not the problem, but rather with your ability -- or lack thereof -- to edit the APN settings. But, on a positive note, with root of the stock OS, using a root file editor can be used to manually modify your apns-config.xml file to add the 4G/LTE data and MMS parameters for Tello. I believe there are also root dependent apps which can edit APN settings.
Since your xt1766 is the Boost Mobile variant, your default APN & telephony parameters are configured specifically for Boost Mobile. I'm making an educated guess that using root permissions to add Tello data and MMS parameters should fix your issue.