Related
Hello all,
I tried searching the forum and google for this problem but haven't come across anything.
I really hope someone can help me out or I'm gonna have to buy a new phone.
I need to access the PhoneUtil menu by punching in *#7284# so I can continue with this procedure to enable AWS. But the menu is not coming up. I even restored the phone to factory settings but still no menu. USB debugging is enabled.
I followed this procedure when I first got the phone a few months ago and it worked. Now all of a sudden my phone only starts to detect Bell/Rogers network and not Mobilicity. So I'm guessing if I went through this process again it will work...but I can't get phoneUtil to pop up this time.
Any ideas?
Splifff said:
Hello all,
I tried searching the forum and google for this problem but haven't come across anything.
I really hope someone can help me out or I'm gonna have to buy a new phone.
I need to access the PhoneUtil menu by punching in *#7284# so I can continue with this procedure to enable AWS. But the menu is not coming up. I even restored the phone to factory settings but still no menu. USB debugging is enabled.
I followed this procedure when I first got the phone a few months ago and it worked. Now all of a sudden my phone only starts to detect Bell/Rogers network and not Mobilicity. So I'm guessing if I went through this process again it will work...but I can't get phoneUtil to pop up this time.
Any ideas?
Click to expand...
Click to collapse
Do you have an AT&T S4? And, if so, did you take the MF3 firmware update? Because if you do, and you did, you shouldn't have. The only thing you can do with a phone on MF3 is Root. No service menu, no Kies, No ODIN, and no going back.
If this is the case, there is a lot of information about it all throughout the General and Q&A sub forums and this information has been there for a while.
If it isn't the case, maybe you can give a little more information and someone can help you. Good luck.
Splifff said:
Hello all,
I tried searching the forum and google for this problem but haven't come across anything.
I really hope someone can help me out or I'm gonna have to buy a new phone.
I need to access the PhoneUtil menu by punching in *#7284# so I can continue with this procedure to enable AWS. But the menu is not coming up. I even restored the phone to factory settings but still no menu. USB debugging is enabled.
I followed this procedure when I first got the phone a few months ago and it worked. Now all of a sudden my phone only starts to detect Bell/Rogers network and not Mobilicity. So I'm guessing if I went through this process again it will work...but I can't get phoneUtil to pop up this time.
Any ideas?
Click to expand...
Click to collapse
did you install the phone util apk?
Yes I downloaded and installed phoneutil.apk from multiple sources many times, but the menu never shows. It's a Bell S4 not AT&T. Could I have installed the MF3 update even though its a Bell phone?
Not sure how to root but I can search. Will rooting it solve the problem?
If you need any other information let me know.
Splifff said:
Yes I downloaded and installed phoneutil.apk from multiple sources many times, but the menu never shows. It's a Bell S4 not AT&T. Could I have installed the MF3 update even though its a Bell phone?
Not sure how to root but I can search. Will rooting it solve the problem?
If you need any other information let me know.
Click to expand...
Click to collapse
I had the same problem too I think it is becoz of the OTA update..which disables that USSD code...did u find any solution how to solve the issue? I really do not want to root the phone..thank u.
Hello everyone. I'm having a problem with my network after going into the test menu (*#*#4636#*#*):crying:. I'm hoping someone can help me out.
My Phone:
I have a stock Nexus 6p not rooted.
The Problem Cause:
After going into the test menu (*#*#4636#*#*). I pressed the menu button (...) and pressed the "Set GSM/UMTS Band" button. My three options were "USA Band", "Band 6" and "Band 7", decided to select "USA Band".
The Problem effect:
Since I did that, I can't make or receive phone calls. My phone won't ring (though it "rings" for the person trying to call me and they get to my voicemail). If I try to call someone else, it hangs perpetually at "dialing".
Soulution I have try:
1-Setting the bands and switch between USA,6,7 but nothing changed.
2-Doing soft/hard factory reset but also nothing changed.
Any ideas how to fix this problem?!
S_2z said:
Hello everyone. I'm having a problem with my network after going into the test menu (*#*#4636#*#*):crying:. I'm hoping someone can help me out.
My Phone:
I have a stock Nexus 6p not rooted.
The Problem Cause:
After going into the test menu (*#*#4636#*#*). I pressed the menu button (...) and pressed the "Set GSM/UMTS Band" button. My three options were "USA Band", "Band 6" and "Band 7", decided to select "USA Band".
The Problem effect:
Since I did that, I can't make or receive phone calls. My phone won't ring (though it "rings" for the person trying to call me and they get to my voicemail). If I try to call someone else, it hangs perpetually at "dialing".
Soulution I have try:
1-Setting the bands and switch between USA,6,7 but nothing changed.
2-Doing soft/hard factory reset but also nothing changed.
Any ideas how to fix this problem?!
Click to expand...
Click to collapse
Factory image.
https://developers.google.com/android/nexus/images?hl=en#angler
Same problem
I'm having the exact same problem. I couldn't make or receive calls out of the box. When I fiddled with the test menu, I was able to at least get it to where I could place calls but I still cannot receive them. I'm not sure what I did at this point. Verizon support and Huawei support have been useless. I tried to factory reset and that did not help.
RageSalamando said:
I'm having the exact same problem. I couldn't make or receive calls out of the box. When I fiddled with the test menu, I was able to at least get it to where I could place calls but I still cannot receive them. I'm not sure what I did at this point. Verizon support and Huawei support have been useless. I tried to factory reset and that did not help.
Click to expand...
Click to collapse
Flash the whole image as the colleague up there said...radio flash should fix it
S_2z said:
Hello everyone. I'm having a problem with my network after going into the test menu (*#*#4636#*#*):crying:. I'm hoping someone can help me out.
My Phone:
I have a stock Nexus 6p not rooted.
The Problem Cause:
After going into the test menu (*#*#4636#*#*). I pressed the menu button (...) and pressed the "Set GSM/UMTS Band" button. My three options were "USA Band", "Band 6" and "Band 7", decided to select "USA Band".
The Problem effect:
Since I did that, I can't make or receive phone calls. My phone won't ring (though it "rings" for the person trying to call me and they get to my voicemail). If I try to call someone else, it hangs perpetually at "dialing".
Soulution I have try:
1-Setting the bands and switch between USA,6,7 but nothing changed.
2-Doing soft/hard factory reset but also nothing changed.
Any ideas how to fix this problem?!
Click to expand...
Click to collapse
What carrier are you with? I did the same thing but I managed to get my phone working again.
why did you mess with these settings if you don't know EXACTLY what you're doing? very big mistake. there some settings you should never fiddle with unless you're dead certain
best best now, imo, if the factory image doesnt fix it... unlock your bootloader and install a ROM that has an expanded set of radio bands... I know some ROMs have it, but not sure which ones.
Yes use Chroma it has more bands to choose from. I think someone needs to create a sticky not to mess with those settings.
I only messed with the settings because I was already not able to make or receive phone calls. Messing with the settings allowed me to at least call out now.
RageSalamando said:
I only messed with the settings because I was already not able to make or receive phone calls. Messing with the settings allowed me to at least call out now.
Click to expand...
Click to collapse
Flash the factory image. That way you know for sure you are as stock as could be. Then if the problem persists exchange the device because its faulty. You shouldn't have to mess with any settings to make calls. Other than maybe a borked APN setting.
RageSalamando said:
I only messed with the settings because I was already not able to make or receive phone calls. Messing with the settings allowed me to at least call out now.
Click to expand...
Click to collapse
What carrier are you on. I have delt with this issue with another member on here. We resolved it.
Verizon
scoobysnack said:
What carrier are you on. I have delt with this issue with another member on here. We resolved it.
Click to expand...
Click to collapse
I'm on Verizon.
Set GSM/UMTS Band Problem Resolved
scoobysnack said:
Yes use Chroma it has more bands to choose from. I think someone needs to create a sticky not to mess with those settings.
Click to expand...
Click to collapse
:good::good::good::good:
Yep! Flashing the Chroma ROM did it! It's all back to normal now. Thank you scoobysnack soooooooooo much for your help!
what I did are;
1. Hard reset
2. Unlock bootloader
3. Install TWRP
4. Root
5. Install custom firmwares
6. Revert back to stock firmware
7. Install different 'radio' images
8. Install different stock firmwares
Unfortunately, none gave me a positive outcome.
Last Hope Was:
I flashed Chroma, a lightweight AOSP ROM focused on battery, performance and stability.
http://forum.xda-developers.com/nex...-chroma-11-08-2015-lockscreen-navbar-t3244444...
The following link is for Chroma download and installation instruction:
http://nexus6proot.com/nexus-6p-custom-roms/chroma-rom-for-nexus-6p-android-6-0-1/2/
This custom ROM for Huawei Nexus 6P was first recommended by a scoobysnack. It works with a proper selection of bands according to your country.
On the dialer, use this codes *#*#4636#*#*
Selection for different bands would then available.
S_2z said:
:good::good::good::good:
Yep! Flashing the Chroma ROM did it! It's all back to normal now. Thank you scoobysnack soooooooooo much for your help!
what I did are;
1. Hard reset
2. Unlock bootloader
3. Install TWRP
4. Root
5. Install custom firmwares
6. Revert back to stock firmware
7. Install different 'radio' images
8. Install different stock firmwares
Unfortunately, none gave me a positive outcome.
Last Hope Was:
I flashed Chroma, a lightweight AOSP ROM focused on battery, performance and stability.
http://forum.xda-developers.com/nex...-chroma-11-08-2015-lockscreen-navbar-t3244444...
The following link is for Chroma download and installation instruction:
http://nexus6proot.com/nexus-6p-custom-roms/chroma-rom-for-nexus-6p-android-6-0-1/2/
This custom ROM for Huawei Nexus 6P was first recommended by a scoobysnack. It works with a proper selection of bands according to your country.
On the dialer, use this codes *#*#4636#*#*
Selection for different bands would then available.
Click to expand...
Click to collapse
I'm glad you figured it out. However, If you tried the factory image and it didn't work, that's a problem! You should have had cellular service right out of the box and definitely after you flashed the factory image. Unless you did not actually try the factory image itself. Can you clarify. Because if that's the case you have a defective unit and it will be an issue when you need to actually restore your device some day. Also don't want people to get the idea that a factory image is not a fix for this.
XxMORPHEOUSxX said:
I'm glad you figured it out. However, If you tried the factory image and it didn't work, that's a problem! You should have had cellular service right out of the box and definitely after you flashed the factory image. Unless you did not actually try the factory image itself. Can you clarify. Because if that's the case you have a defective unit and it will be an issue when you need to actually restore your device some day. Also don't want people to get the idea that a factory image is not a fix for this.
Click to expand...
Click to collapse
Flashing the factory image does not work. I messed with my phone for 4 hours trying to get of to work again. I was originally on chroma when I screwed my bands up. That's how I knew about the other bands. I believe it only fixes international phones . I'm in the US on VZW and flashed factory image and had to select band 6. So depending on where you are depends on what method you have to use to correct the problem. And yes a sticky and FAQ should be made as a lot of people seen to have this problem.
scoobysnack said:
Flashing the factory image does not work. I messed with my phone for 4 hours trying to get of to work again. I was originally on chroma when I screwed my bands up. That's how I knew about the other bands. I believe it only fixes international phones . I'm in the US on VZW and flashed factory image and had to select band 6. So depending on where you are depends on what method you have to use to correct the problem. And yes a sticky and FAQ should be made as a lot of people seen to have this problem.
Click to expand...
Click to collapse
The images work on either variant. It confuses me why a factory image would not fix it but I'm sure there is a reason. Its new to me though. What's weird is I am on Verizon in the US as well. Works right out of the box for me and any issues that I have come across have been fixed by a factory image. I wonder if people having problems on Verizon are having issues due to network and sim card provisioning issues and by switching bands you are fixing it but you are not on the normal bands maybe. I know some people on Verizon had to call and tell them to activate LTE on their line even though they were supposed to be getting it. And that fixed the no service.
Nexus 6p - Set GSM/UMTS Band Problem
XxMORPHEOUSxX said:
The images work on either variant. It confuses me why a factory image would not fix it but I'm sure there is a reason. Its new to me though. What's weird is I am on Verizon in the US as well. Works right out of the box for me and any issues that I have come across have been fixed by a factory image. I wonder if people having problems on Verizon are having issues due to network and sim card provisioning issues and by switching bands you are fixing it but you are not on the normal bands maybe. I know some people on Verizon had to call and tell them to activate LTE on their line even though they were supposed to be getting it. And that fixed the no service.
Click to expand...
Click to collapse
I guess the reason why a factory image did not fix the problem is because my phone version is US not International. And I am now not from US, originally from Middle East. So there is no compatibility between US and the international bands. The only choices I had from the Bands are USA Band, 6 and 7. I am guessing that the International version has more options and compatible with variant bands.
guys. try to install chroma rom , it has several different bands. just to get it working . then return back to stock if you want i had the same issue and i had data working and sms without calls until a guy helped me ( im very grateful for him ). i hope it works. please let me know
@scoobysnack .. man, I came to help but you were faster haha
I used Chroma ROM it gives you proper selection of bands according to your country.
Similar problem
I have the same issue and my carrier is Airtel - from India. Will Chroma work with this?
RageSalamando said:
I'm on Verizon.
Click to expand...
Click to collapse
Hi
Last june I finally got my new Redmi 2 Pro (HM2014819, ergo the Brazilian version) and as soon as it arrived, I decided to reflash it into the latest available Nexus Experience custom ROM. Before that, though, I managed to check that my phone did had access even to LTE networks.
Turns out the GPS got weird because I supposedly didn't attempt to fix it before in the original ROM. I tried the the modemst1/2 format trick and it also didn't work. So I flashed MIUI7 over it again in an attempt to get a fix in the original ROM.
When I got back to MIUI, all celular/signal data was gone, along with my IMEI number (probably from the modemst partition wipe). I had to struggle a lot and I finally was able to recover it using this tutorial. However, as I just noticed recently playing Pokemon Go, 4G networks never came back even though I'm up and running on both H and H+ networks.
Using QPST and QXDM, I delve further into the QCN file and I could notice that the LTE values were actually set for Redmi2 PRIME version, which are Asia-related basebands 3 and 40 (meaning the actual LTE value in binary had 1's in the 3th and 40th bytes). However, the Redmi2 PRO version supports South America-related LTE bands 2, 4 and 7, as GSMArena points out.
Using this information and following this guide, I also tried to change/write over new Decimal values that would match my required LTE bands, but to no avail. When manually selecting networks, only 3G networks show up, even though I'm sure I could see and even pick 4G networks manually when I first booted up my (at that time, unmodified) new Redmi2.
What did just happen? What CAN I do?! How can I recover the intended, factory original version of the brazilian Redmi 2 networks?! Is there something to do with modemst2 erasure, or IMEI loss, or even NON-HLOS.bin file? Aren't they all overwritten when you reflash MIUI through MiFlash anyway?
Please, PLEASE, help me! I'm already on the brink of purchasing another cellphone (and it won't be another Xiaomi, that's for sure) if I can't get this to work. I did purchase this sorely because of the 4G connection and now I lost it entirely. Come on! :crying:
damn.... i've done this mess of erasing modemst's too and got the same problem. VERY LUCKY of me, i had a twrp backup that i did some days before doing this. hope you find some solution to this and dont give up on xiaomi just for a mess that you did xD
igorinolw said:
damn.... i've done this mess of erasing modemst's too and got the same problem. VERY LUCKY of me, i had a twrp backup that i did some days before doing this. hope you find some solution to this and dont give up on xiaomi just for a mess that you did xD
Click to expand...
Click to collapse
Igor, do you think you could at least share your modemst partition and/or your QCN file? I could use this to find the differences between my modem configurations and set it exactly as the brazilian's factory default modem.
If you're worried about IMEI scamming, then a simple printscreen from certain screens on QPST/QXDM will suffice, since I can tell what's wrong from them. If you're willing to help me (and have a rooted device), please, do tell and I can walk you through how to get them. Thanks!
http://en.miui.com/thread-218200-1-1.html
Follow this tutorial.
My signal came back but I'm having frequent signal loss. The only solution is to turn on/off airplaine mode.
I've to send it to tecnical assistant but I don't want to stay without the phone.
Acttually I'm not sure if the 4g works, because my city only supports 3G. When the data connection is on I don't loss the signal.
LuizHPiccinini said:
Follow this tutorial.
Click to expand...
Click to collapse
That's the exact tutorial I've followed to recover my IMEI. And I even mentioned that in the OP, bud. My problem happened after that. Please read more carefully.
Sorry, I just saw the second link.
Drezus said:
Igor, do you think you could at least share your modemst partition and/or your QCN file? I could use this to find the differences between my modem configurations and set it exactly as the brazilian's factory default modem.
If you're worried about IMEI scamming, then a simple printscreen from certain screens on QPST/QXDM will suffice, since I can tell what's wrong from them. If you're willing to help me (and have a rooted device), please, do tell and I can walk you through how to get them. Thanks!
Click to expand...
Click to collapse
as soon i get to my pc with the programs, ill try to help you if nobody comes first :highfive:
igorinolw said:
as soon i get to my pc with the programs, ill try to help you if nobody comes first :highfive:
Click to expand...
Click to collapse
Thanks a lot!
Oh gosh guys, I hope you can help me too! I've got the exact same problem with my HM2014819!
Did you manage to fix that?
Hi the exact same thing happened to me, I had no mobile internet at all and I fixed that qcn stuff but all I could find was asian versions, I get no 4G network and I have no other brazilian file to compare. If you managed to fix that, please please share, thanks a lot.
Hello, first of all I want to let you know that I am not an expert but have so far been able to convert my Axon A2017 to the US A2017U version.
Big thanks [email protected] for supplying the necessary files.
I have:
-unlocked the bootloader
-rooted the phone
-flashed successfully B20
However, When I upgraded to B29, I lost TWRP and the cell radio of the phone is non-responsive. It won't even turn on. Bootloader is sill unlocked. I made phone calls on my T-mobile network when it was the origional A2017 B8 version. So I believe the bandwidths are compatible.
I have already done the following troubleshooting: (note: WIFI currently works just fine)
-My network is with T-Mobile, and I have been using a different axon A2017U for over a year with no problems.
-When I type *#*#4636#*#* and got to phone Info says, GSM Service: Radio Off, and the Turn on Radio button does nothing.
- I have tried working with every setting in this menu with no luck.
-When I insert my SIM card that is working on my current axon 7 into the converted A2017U, it is able to pick up T-Mobile network u.s. LTE, (fast.tmobile.com) and T-Mobile US (tmus). However, there are no bars because the radio is not turned on.
-When I try to search for new networks an error message saying, "network search cannot proceed when the data service is enabled disabled it?" So I disable it and nothing happens except for an error message saying "error while searching for Networks".
-In network mode I have switched to every option available, LTE/wcdma/GSM, wcdma/GSM, and GSM only with no result.
I am currently running Android version 6.0.1 on build B-29. Any help to get the radio up and running to receive phone calls would be greatly appreciated. Everything else is working except for the phone radio to send and receive phone calls.
Thanks for any Help.
Do you still have your IMEI or did the partition get corrupted?
ultramag69 said:
Do you still have your IMEI or did the partition get corrupted?
Click to expand...
Click to collapse
I check the number with several online checks, as well as T-Mobile, and they are unable to bring up any information about the number. I imagine it got blocked or corrupted during the upgrades.
What do I do to unblock it or make it functional again?
Go to settings>About>Status and check your IMEI number. If it's blank its noyt gonna work on any network...
You might be able to restore it if you have a backup of it - no-one will give you their backup as you then have their phone - or as a last resort, you might need to restore to the stock Chinese Rom again and see if that fixes it...
Good luck, I'm off to bed after a long backshift...
ultramag69 said:
Go to settings>About>Status and check your IMEI number. If it's blank its noyt gonna work on any network...
You might be able to restore it if you have a backup of it - no-one will give you their backup as you then have their phone - or as a last resort, you might need to restore to the stock Chinese Rom again and see if that fixes it...
Good luck, I'm off to bed after a long backshift...
Click to expand...
Click to collapse
Thankfully the numbers are there on both IMEI slot 1 and IMEI Slot 2. Thanks for your help. I hope to hear from you after a good night of rest.
Flash the correct modem/bootstack for your device.
Shipcaptian said:
Thankfully the numbers are there on both IMEI slot 1 and IMEI Slot 2. Thanks for your help. I hope to hear from you after a good night of rest.
Click to expand...
Click to collapse
Just go to the LineageOS thread and download the A2017 modem file, then just flash it
Choose an username... said:
Just go to the LineageOS thread and download the A2017 modem file, then just flash it
Click to expand...
Click to collapse
Sounds Good
Will I need TWRP to flash it or can is just use the Reg. recovery system?
Shipcaptian said:
Sounds Good
Will I need TWRP to flash it or can is just use the Reg. recovery system?
Click to expand...
Click to collapse
You need TWRP. Just install it with axon7tool via edl if you don't have fastboot, or try axon7toolkit
Choose an username... said:
You need TWRP. Just install it with axon7tool via edl if you don't have fastboot, or try axon7toolkit
Click to expand...
Click to collapse
Here's the latest update:
I loaded TWRP onto the phone and installed the file A2017U_N_Modem.zip. (Several Times)
nothing has changed. The radio is still turned off and no signal is being picked up from my carrier T-Mobile.
While loading it says: Loading A2017U_N_Modem for nougat system. I am not running nougat and I cannot find any other modem to download. Will that make a difference?
Any other suggestions are welcome?
Shipcaptian said:
Here's the latest update:
I loaded TWRP onto the phone and installed the file A2017U_N_Modem.zip. (Several Times)
nothing has changed. The radio is still turned off and no signal is being picked up from my carrier T-Mobile.
While loading it says: Loading A2017U_N_Modem for nougat system. I am not running nougat and I cannot find any other modem to download. Will that make a difference?
Any other suggestions are welcome?
Click to expand...
Click to collapse
You need to flash the A2017 modem, not the A2017U one
Here: https://www.androidfilehost.com/?fid=457095661767137840
bkores said:
You need to flash the A2017 modem, not the A2017U one
Here: https://www.androidfilehost.com/?fid=457095661767137840
Click to expand...
Click to collapse
Okay it works! I've got signal but when I try to make a phone call and my other phone picks up I can't hear or say anything. Any idea what's happening? I have tried refreshing the signal with no luck.
Hey man, I'm having the same problem with my Axon 7, brand new A2017U. Turned it on for the first time and I haven't had an ounce of radio on. Same things you've tried I've tried and it refuses to work. Mine is not rooted and I don't want to. I've tried downgrading my update and to no avail. Factory reset etc. I've contacted ZTE and they said they have forwarded my details and my phone details, storage size, color etc. To the necessary representatives. I think I'm gonna be sent a replacement, but just wanted to let you know your not alone.
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Knuxyl said:
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Click to expand...
Click to collapse
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Yeah I already tried that but it jept giving me an error saying unknown command [ ]] or somrthing along those lines. i looked through the script and didnt see any typis. i think your NON-HLOS.img is different format than the NON-HLOS.bin files found in the stock firmwares, plus it's much larger. Anyways, tried a fastboot flash the modem with it and that didnt work either.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
madbat99 said:
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
Click to expand...
Click to collapse
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Also as an update, the 56 version didn't fix it either
Knuxyl said:
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Click to expand...
Click to collapse
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
madbat99 said:
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
Click to expand...
Click to collapse
You are 100% on point. Sprint (and its subsidiaries) had Motorola Mobility to include code in an OTA update which would disable functionality of any network other than the original UICC (SIM). In other words, when you got a new Sprint compatible xt1766 (Sprint, Boost or Virgin Mobile), opened the box and booted the device with the preinstalled SIM in it, the xt1766 became forever locked to that network -- the OTA update carved that in stone. The update made it impossible to downgrade the baseband radio, killed all GSM functionality, and broke the radio on custom ROMs (the latter being unintended most likely). The only people I have heard of getting around this are the ones that didn't take the -8 OTA update. Like you were saying, I'd like to know what Jason M. done in his custom ROM to fix radio function, whereas at least the radio would work with the original SIM on a custom ROM. He said something about "adding missing symlinks" to the build.
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
chmod 0700 /persist/rfs/msm/mpss/datablock/id_00
Click to expand...
Click to collapse
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
lugnut2099 said:
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
Click to expand...
Click to collapse
Seriously, you unbricked my kids phone!
Requested permission to access your file twice
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
ELEKTRIKMESSIAH said:
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
Click to expand...
Click to collapse
You see that member's account disabled? So.... You're talking to no one
Reading is fundamental