Related
hi, my xiaomi mi5 32gb/3gb ram had android 6(no ideea about version) and unlocked bootloader, bought from china with european version of the rom, gapps installed.
everything worked perfectly, no drops in signal, nothing to complain.
i updated to MIUI 8 Android 7 official and after that the signal dissapeared, the only moment i had signal was when i put a new simcard in the phone, and only for 2 minutes.
Then i flashed with XiaoMiFlash : gemini_global_images_V8.2.2.0.NAAMIEB_20170407.0000.00_7.0_global_95e92d22eb
-- the problem stays: no service/emergency calls only.
i have good 3G 3-4bars/4G sometimes, when it comes to signal in this location.
nothing helped.
flashing xiaomi-miui-hellas-7.0_gemini_V8_XTRV_7.4.20 with TWRP Recovery also didn't help my problem
Now i am with a phone with no signal, could you please give me some help to solve this?
i've seen a lot of people in this situation on forums, so a solution would be very good.
Perhaps the settings from the *#*#4636#*#* Hidden MENU, this way i would do it the way it is on a working phone.
Thanks, greetings. Dan
I tried to reload the stock rom on my phone, and lost my IMEI number. After loading Validus ROM on my phone, I was able to retrieve my IMEI number, but I cannot connect to 4G networks. I tried going into the bootloader and running the following commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
But I still cannot connect to 4G networks. Any suggestions?
UPDATE: I flash my phone with Validus 8.1 1.3 BETA, and then booted the phone. It was on 3G. I then rebooted into the bootloader, and ran the modem flashing commands that I did above. I then popped out the SIM card, and booted the phone.
I went into Settings > About Phone > Phone Status > SIM status, and watched the status as I put back in the SIM. I noticed the "Mobile Network Type" turned to LTE for a few seconds, and then went back to CDMA.
Does this give anyone any ideas? I thought this could have been a modem firmware issue, but as you can see above I've been flashing the modem firmware with the latest firmware from the Stock, so I'm not sure what this could mean.
UPDATE2: I noticed that when I am booted into Bootloader, my baseband version is M8953_27.36.07.41u SANDERS_NA_CUST. However, when I am booted into a custom ROM that has 3G working, the baseband is M8953_27.36.07.41e
Could this have anything to do with my issues? I have an XT1806 and tried to flash the stock ROM SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I had a similar issue with my moto X pure Edition. Everytime I would flash stock rom, I would lose Wifi. I my fix for that issue was to flash stock rom, let it boot up to the welcome screen, turn off the phone like completely off, boot to bootloader and use the commands in this order:
Erase modem1
Erase modem2
Flash Moden NON...
Flash fsg
Use the commands u have up there on first post, but use the order I posted.
Try that and see if that works.
cerobles1 said:
Use the commands u have up there on first post, but use the order I posted.
Try that and see if that works.
Click to expand...
Click to collapse
This did not work for me, sadly. I think I need the backup of someones EFS partition. Does anyone have one for me?
Please let me know.
I flashed stock ROM SANDERS_NPSS26.116-61-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml, and am now having similar issues. Netowork data shows 'H' instead of 4G LTE. Changing the APN and changing stuff under *#*#4635#*#* does nothing either. I have an XT1806 and my baseband in both fastboot and the settings is M8953_27.36.07.41e. Please help!
kevinm2738 said:
I went into Settings > About Phone > Phone Status > SIM status, and watched the status as I put back in the SIM. I noticed the "Mobile Network Type" turned to LTE for a few seconds, and then went back to CDMA.
Click to expand...
Click to collapse
^Me too.
I have never had this phone working faster than 3G. Which has been a major bummer. I pre-ordered the sanders XT1806 64gb p5 and received it in October 2017. The day it arrived, I booted it without any SIM and saw the stock ROM had around 50 preloaded apps, so I blasted it away and installed Lineage 15. I didn't think to put the SIM in and test connection speeds on the stock ROM. I just went straight to using Lineage 15.
Because of camera issues I switched to Validus Nougat, and shortly after the official Oreo update was released and the camera blobs for it became available, I upgraded to Validus Oreo and ran several versions of that up to the final one. I tried switching providers from Straight Talk (Verizon flavor) to Verizon Prepaid Wireless because I was paranoid that I had a bad SIM or that they were purposely capping me. It made no difference. I just loaded Lineage Pie on it and am once again connected at 3G mobile data speeds.
Just like Kevin observed, it looks like it tries to negotiate for LTE but fails and drops back to CDMA.
My baseband in both bootloader and settings shows as M8953_27.36.07.40R
Any ideas?? I've been using this phone for almost a year and a half now and haven't enjoyed high speed data yet. Would love a fix...
kevinm2738 said:
Could this have anything to do with my issues? I have an XT1806 and tried to flash the stock ROM SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
You flashed the wrong firmware.
Try https://drive.google.com/open?id=161Z95p4Ss16xgzvAix5O2kxCktY-LwCM which is XT1806 firmware. Then reflash.
You might also want to flash the RETUS nougat firmware and then update to Oreo. I have that too.
@lufusol, I didn't see any mention of Kevin's carrier in his post. For your case I did some checking here and there.
Motorola's carrier compatibility chart only shows partial support for Straight Talk. Verizon proper has full support. Not sure about the prepaid service.
The site below also shows only partial but does include a bunch of APNs to use/try.
https://apn.gishan.net/en/apn/straight-talk/motorola-moto-g5s-plus
FrequencyCheck shows supported bands along with an animated percentage graph (100% for supported bands). But, if I'm reading things correctly GSM & CDMA is only up to 3G or 3.5G(4G).
https://www.frequencycheck.com/carr...te-na-64gb-xt1806/straight-talk-united-states
If I were to go by the above then technically there isn't a problem with the phone but I don't know. Only others with the XT1806 on that carrier can confirm the limitations.
Moto G5S Plus XT1806, balanceOS 2.0, MultiROM, XDA Legacy
@lufusol, ugh, neither of my XDA apps would allow me to add a pic to my previous message or a new one. Resort to using the web.
The bands supported by the XT1806 (from GSMArena) should be compared to the bands used by Straight Talk. Maybe to see if you're not getting what you should or getting all that you can.
Update: I reflashed stock nougat 7.1.1, rerooted, fixed permissions on /persist, that got 4G/LTE working again. Then I reflashed PE 9 and 4G/LTE remained working. Haven't tried another custom Oreo or Pie ROM since the fix, but PE Pie isn't exactly running flawlessly (it's like the fp reader doesn't exist, and Bluetooth audio keeps "buffering") so I plan to try lineage pie and maybe even go back to Validus Oreo final and see if I can retain LTE functionality while fixing those issues (sure would be nice to see Validus Pie, but doesn't look to be in the works, even GZOSP Pie seems to have been abandoned)
Anyway, fixing persist permissions while on the stock ROM was the solution for me
@lufusol, GZOSP Pie build was released a couple of days ago so not abandoned I guess. ?
ZTE Axon 7 A2017U, Project New World, Multiboot, XDA Legacy
marcdw said:
@lufusol, GZOSP Pie build was released a couple of days ago so not abandoned I guess. ?
Click to expand...
Click to collapse
This is now off topic but I'll respond why I said what I did:
The official GZR all-in-one ROMs thread here at XDA has a link (to AFH) containing 4 GZOSP Pie builds for Sanders, released from mid September through early October 2018. No updates since, and no Validus (Pie) builds in sight.
You're right, of course, they just need to update their thread and afh uploads. I went to their official Google+ page and found this:
Syed Sajid
Ground Zero Roms
Jan 22, 2019
New Validus Pie Beta v3.0 Official build for Sanders(Moto G5S Plus).
- Android-9.0.0_r30
- Jan Patch
- Latest Validus Sources
- Updated Blobs to pie
- update media codecs and profiles from deen PPK29.68-16-8
- uprev to [email protected] hal.
- gps: Increase batch size to max
- update camera blobs from stock OPSS28.65-36-6
- update sensors blobs from LA.UM.7.6.r1-03700-89xx.0
- update GPS blobs from LA.UM.7.6.r1-03700-89xx.0
- update AptX blobs from LA.UM.7.6.r1-02500-89xx.0
NOTE: its beta build
Link: https://sourceforge.net/projects/sa....Beta.3.0-OFFICIAL-20190122-0743.zip/download
Party on! I love me some Validus. Will try it ASAP. Lol
Ah yes. With each ROM announcement post there are different download locations I noticed. The ever-important OP hasn't been maintained. [emoji53]
I upgraded to OOS 10 Stable, and immediately started having issues where I would not receive the contents of MMS, but I would receive notifications of them saying "message expired or not available".
Most of the advice I got was to downgrade back to the latest OOS 9, but I didn't want to most likely lose most of my data.
Here's what I would recommend trying:
Option A: Resetting Your APN settings
Open the Settings app
Tap on "WiFi and internet"
Tap on "Sim & network"
Choose the SIM you are having issues with (can be both, in which case do the following steps for each SIM)
Select "Access Point Names"
Tap the 3-dot menu icon at the top-right, then tap "Reset to default".
Reboot your device.
Option B: Flash older Modem images
Go to this XDA thread for stock ROM images.
Download the file named "9.0.17-OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905-FASTBOOT.zip"
While the file is downloading, make sure you have USB debugging enabled and and can flash partitions in fastboot. This should require an unlocked bootloader to do so (TAKE A BACKUP BEFORE UNLOCKING THE BOOTLOADER).
Once the file is done downloading, locate the file on your computer, and unzip it.
Inside you'll find another zip file called "images.zip". Unzip this into its own subdirectory.
Go inside that new subdirectory and you'll see a bunch of img files. The one we need to look at is the modem.img file.
Open a command prompt / terminal on your PC in that subdirectory.
Type the following commands into the terminal:
Check if your device shows up in ADB:
Code:
adb devices
Reboot to fastboot:
Code:
adb reboot-bootloader
Check if your device shows up in fastboot:
Code:
fastboot devices
If it appears in fastboot, flash both the modem A and B partitions with the old modem image like so:
Code:
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot reboot
If you're still getting issues, try resettign the APN as described in Option A above.
This worked for me on OOS 10 Stable on Verizon with one SIM card in my OnePlus 6T.
Were you running into this issue?
https://forums.oneplus.com/threads/...fter-android-10-update.1134562/#post-21036876
I have MMS working currently with Pulse and the stock OnePlus Messages app, but had to finally abandon Google's Messages which I really prefer over everything.
I had reset APN, tried setting manually, and had no luck, but now I'm curious to try an older modem!
Edit: No luck here Flashed both modems, reset APN, but still get expired messages in Google Messages.
mrpeters said:
Were you running into this issue?
https://forums.oneplus.com/threads/...fter-android-10-update.1134562/#post-21036876
I have MMS working currently with Pulse and the stock OnePlus Messages app, but had to finally abandon Google's Messages which I really prefer over everything.
I had reset APN, tried setting manually, and had no luck, but now I'm curious to try an older modem!
Edit: No luck here Flashed both modems, reset APN, but still get expired messages in Google Messages.
Click to expand...
Click to collapse
My issue was similar, but I could not get any MMS whatsoever on any messaging app, even the OnePlus and Verizon ones.
What was the last version of OOS you were running that had working MMS? Some people reported that even 9.0.17 wasn't working for them, and their alternative was to revert to 9.0.13
EddieK23 said:
My issue was similar, but I could not get any MMS whatsoever on any messaging app, even the OnePlus and Verizon ones.
What was the last version of OOS you were running that had working MMS? Some people reported that even 9.0.17 wasn't working for them, and their alternative was to revert to 9.0.13
Click to expand...
Click to collapse
I can't say with certainty that I was on 9.0.17 and not 9.0.13 but I'm pretty sure I had taken the latest OTA a little while before installing the Android 10 OTA.
Having this same issue here, MMS works OK with OnePlus's app, but not Google Messages. Just got the latest 10.0.1 udpate, and the problem persists.
The last working modem file for me was on 9.0.13, I can still send MMS on other versions but I need to disable wifi first for some reason.
You guys struggle way to much for a service that I consider obsolete... MMS is a service back from the medieval smartphones era (if I can call those smartphones) when wap was the way to receive multimedia messages. There are so many alternatives now, that makes the struggle now pointless...
demeez said:
The last working modem file for me was on 9.0.13, I can still send MMS on other versions but I need to disable wifi first for some reason.
Click to expand...
Click to collapse
9.0.13 modem with OOS 10.0 Stable or 10.0.1 Stable?
chasemyass said:
You guys struggle way to much for a service that I consider obsolete... MMS is a service back from the medieval smartphones era (if I can call those smartphones) when wap was the way to receive multimedia messages. There are so many alternatives now, that makes the struggle now pointless...
Click to expand...
Click to collapse
If only I can prevent any and all of my friends, family, and co-workers from ever sending me MMS, then I'd never have to worry about it!
But honestly though, I agree MMS is pretty pointless and just uses up my data for no real reason.
Then again, it means I don't have to have certain people connect with me on social network messaging apps to send me MMS.
demeez said:
The last working modem file for me was on 9.0.13, I can still send MMS on other versions but I need to disable wifi first for some reason.
Click to expand...
Click to collapse
mrpeters said:
9.0.13 modem with OOS 10.0 Stable or 10.0.1 Stable?
Click to expand...
Click to collapse
9.0.13 modem works on 10.0 Stable for me, haven't updated to 10.1 Stable yet.
Who's your carriers? I have TMobile, completely removed the stock messaging app and use Google's exclusively. No problems at all here, international 6t with latest 10.1. If Verizon, I read somewhere on these boards about a couple files someone copied over and fixed their issue. I can't say for certain it was MMS or SMS, I'll see if I can track the post down.
---------- Post added at 10:12 PM ---------- Previous post was at 09:45 PM ----------
A little searching, couldn't find what I was looking for but I read in one of the posts about 2 files being copied over...I wish I'd had paid better attention, didn't apply to me so just kinda breezed over it.
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Bandalo76 said:
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Click to expand...
Click to collapse
Have you updated to a newer version of OxygenOS since having Verizon replace the SIM? I have been to Verizon twice now, and both times they have replaced the SIM. It works great, until OxygenOS updates, and then it breaks again. This has been super frustrating, especially because I don't get a notification that the MMS failed to download. I'll go days and then talk to someone in person and they'll ask why I haven't been replying to group chats; then I'll come to find out that I haven't been getting any group messages, nor have I gotten a message saying they failed to download.
For anyone that hasn't seen this, and to help link the two different threads, here's something from the Google Messages community site: support.google.com/messages/thread/18774467
I have sent messages in to both Google and OnePlus, so if I (by some miracle) get a workable resolution, I'll share it here and on the Google community thread.
mason-johnson said:
Have you updated to a newer version of OxygenOS since having Verizon replace the SIM? I have been to Verizon twice now, and both times they have replaced the SIM. It works great, until OxygenOS updates, and then it breaks again. This has been super frustrating, especially because I don't get a notification that the MMS failed to download. I'll go days and then talk to someone in person and they'll ask why I haven't been replying to group chats; then I'll come to find out that I haven't been getting any group messages, nor have I gotten a message saying they failed to download.
For anyone that hasn't seen this, and to help link the two different threads, here's something from the Google Messages community site: support.google.com/messages/thread/18774467
I have sent messages in to both Google and OnePlus, so if I (by some miracle) get a workable resolution, I'll share it here and on the Google community thread.
Click to expand...
Click to collapse
There's another thread that's talking about this issue: https://forum.xda-developers.com/on...dating-to-android-t3999711/page2#post81270021
I posted a reply over there with a possible fix from OnePlus about clearing the system cache. It worked for me, but for how long is anyone's guess.
Came just to chime in and say I'm glad I'm not alone in this struggle... Such a shame to not be able to use Android Messages. Has anyone come up with a permanent fix yet? Does it work fine if you are on a none OOS ROM?
I followed Option A, rebooted to recovery, using TWRP cleared Dalvik/ART cache. Booted up and IT WORKS OMG IT WORKS!!!! Now I can stop using the Default messenger and Signal which splits my conversations and now only use Signal. I was seriously considering downgrading to 9 before coming across this post. Thank you OP.
Also anyone trying to test, I use the following site its sends an MMS to your phone.
https://www.twilio.com/mms
I'm so sick and tired of all this bull**** of A10, both GPS and MMS not working and nobody can tell why, and how fix this.
Hello, I had tried posting this where I assume it belongs but I can't seem to post anywhere but here. Anyways, today me and a friend rooted his ROG Phone 2 via rooted ROM we had found here. Everything had gone to plan, unlocked the boot loader with Asus's tool, fastboot the custom ROM, ran Magisk and let it update, confirmed root with it and a cheapo Play Store root checker, all was good.
First issue, WiFi didn't work, but no big deal, unlimited data. Then he discovered that sound didn't work, so I immediately looked it up, didn't find a post specific to his phone but someone mentioned the mic not working in the one I read, gut feeling I told him to check the mic, loe and behold, not working.
He doesn't want to have to reset to factory ROM and lose the root. Ant idea what's wrong? I could find the post we followed if requested before I find and post it anyways.
As mentioned it's the new Asus ROG Phone 2
Model
ZS660KL
The 512GB/12GB RAM
As far as I'm reading is there shouldn't be any exact issues and is no particular reason. We read later on in the comments, someone had the WiFi issue but the OP assured his didn't have the issue.
WiFi isn't a major need, again, data. But the sound and mic is a huge issue as it's his daily. I'm familiar with rooting and custom ROMs, mainly Samsung's. I'm quite confused, I've never had a major issue with a ROM that doesn't have a simple work around.
What firmware version is he on? He has to make sure that the magisk-patched boot image matches the firmware he has installed or he will have issues like the ones you describe with WiFi, sound, and possibly abnormally long boot times.
This is a boot image issue
Had the same issue when rooted.. i flashed the ww rom again to unroot my device now everything works. Hopefully someone can give a solution
He's working on patching a fresh ROM from Asus, that's the only idea he can make right now.
I've seen a bunch of people asking about getting the One Plus 7 Pro working on Visible Wireless network and thought I would share what has worked for me in case anyone is still looking for a solution.
Some specifics first, I have a OP 7 Pro, GM1917, that's the global version I think? YMMV
Currently running Derpfest 12, mainly because I like how android 12 looks and feels. Still looking for something better since devs haven't released an update since may.
What I have noticed is that OOS version 10.0.2 works with Visible Wireless out of the box, while later versions do not. Seems somewhere after that version that OOS updates broke Visible support.
I first noticed this because I bought the phone off swappa, wanting to upgrade from the crappy Visible Midnight I got to see if I get good service in my area. After installing a custom rom and then using MSM to reflash latest stock when something broke, Visible wasn't working. Which didn't make sense. It had worked before. right? So my thinking was that the original owner had owned the phone long enough to OTA from 10 to 11. Sure enough, downgrading to 10 and then using OTA to upgrade fixed the issue.
Tools and Guides:
EDL Recovery mode driver + Guide on how to enable unsigned drivers.
Warning! Leaving Unsigned Drivers enabled will make you system vulnerable to bad actors, virus/trojan masquerading as driver, etc. Disable Unsigned drivers after use!
How to Unbrick Your OnePlus 7 Pro Device from Dead State
In this tutorial, we have listed detailed instructions to unbrick youer OnePlus 7 Pro and bring it back from a dead state, using the MSM Download Tool.
www.droidwin.com
OOS Stock 10.0.2 Unbrick Tool MSM thingy
Index of /list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/Q
OOS Stock OTA update to later version of 11
OnePlus7ProOxygen_21.P.43_OTA_0430_all_2204061153_a32bd850d41a490c.zip | by tattoorepairman for OnePlus 7 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
So here's my process.
Enable unsigned drivers support for your PC, download and install qualcomm EDL driver.
Backup phone, of course.
Put phone in EDL mode. Run MSM tool with guacamole_21_O.22_191107_repack
OTA update from local file, OnePlus7ProOxygen_21.P.43_OTA_0430_all_2204061153_a32bd850d41a490c.zip (Might work with latest OTA zip, havent tried.)
That will give you OOS 11, almost latest (I think there's like one more update to stable from there, but I'm lazy) with working Visible support.
Alternatively, if you want to make sure that you get legit OOS and not have to rely on zips from the internet, just let OTA update you to latest like normal, or use Oxygen Updater app.
From there, do whatever. Install TWRP, ROM, Magisk, etc.
Keep the files around somewhere so that if something goes wrong, you have everything prepared to fix it on hand.
Enjoy
I've managed to get visible sim working on all A12 roms using a few methods. Downloading an app that adds APN settings if the rom doesn't let you. Then typing in all the apn settings from this reddit post:
https://www.reddit.com/r/Visible/comments/ehdeik
For dun apn type, I used DUN all capitalized and it seems to work fine.
Then this is the key step: swapping the sim card between the two sim slots and restarting the phone repeatedly until it properly recognizes the sim card. If that doesn't work then inserting a different random sim, in my case I inserted my old tmobile sim, then taking it out and putting back the visible sim and switching sim slots if needed.
I'm using a GM1915, tmobile version that's been permenantly unlocked thanks to an xda member called mobbdeep.
right, I'd seen that, but i only have an old tacfone sim that's no longer active. does the sim have to be active for it to work? also, doesn't that need to be done every time you reboot the phone? that seems kind of annoying lol. especially since I reboot my phone sometimes like 2-3 times a day when it refuses to lock onto band 66.
b-thorn said:
right, I'd seen that, but i only have an old tacfone sim that's no longer active. does the sim have to be active for it to work? also, doesn't that need to be done every time you reboot the phone? that seems kind of annoying lol. especially since I reboot my phone sometimes like 2-3 times a day when it refuses to lock onto band 66.
Click to expand...
Click to collapse
Any old sim should work, my tmobile sim isn't active but forces my phone to change bands. It's also just a one time thing.