Currently have the 8.0 ROM on my XT1687 US variant and this ROM is absolutely amazing. I still have the choppy audio issue when trying to use VoLTE on Verizon though. Rather than bricking my phone trying to get it back to stock, does anyone have a TWRP flashable fix that updates the modem for this phone? According to this thread: https://forum.xda-developers.com/g5-plus/how-to/npn25-137-43-5-update-retus-verizon-t3657881 It shows as the problem being resolved, but no one ever created a TWRP flashable file for this, and I sure wish I knew how!
Related
Edit: Fixed using this - http://forum.xda-developers.com/showpost.php?p=53502055&postcount=16
Newer ROMs don't seem to have the correct settings for the Ting APN. Make sure the network type is strictly CDMA/LTE and in particular that the APN Type is set as both DEFAULT and as mms (default, mms).
Hey guys, hoping someone can help me out here.
I'm on the "Ting" cell network using an LS980. Resurrect Remix ROMs worked well for me up until the 5.3.8 update (5.3.7 was the last version that still gave me cell data). The new 5.3.9 also causes issues and the SIM card even completely locks itself at times as it attempts to contact the network.
I just installed the latest Blisspop nightly ROM and am having the same issue. I know that older LiquidSmooth ROMs were also working properly for me aafter I used one of them as a Plan-B from Resurrect.
If anyone has any ideas as to what the issue could be please let me know. I'm going to try tinkering with my radio files soon and see if I get anywhere.
Bumping. sorry but this is getting really frustrating. I tried flashing the ZVC and ZV8 modems and it didn't make a difference.
ZVC modem actually crashed my phone (running Blisspop 2.2 latest nightly, stock kernel, TWRP 2.7.x recovery) after attempting to flash the ZVC modem without clearing the cache/dalvik afterwards.
I've now restored my phone to factory, stock ZVE ROM and rooted using StumpRoot. I'll be putting on the TWRP recovery soon.
If anyone has any ideas as to why I'm having radio/modem/signal problems on any Resurrect ROM past 5.3.7 and with the new Blisspop please let me know. I really want to get back on a non-bloated, up to date ROM.
>tfw
Bumping again. My phone is actually having a few other odd issues now after having to go back to stock with the ZVE .tot and re-rooting/recovery...
I'm still mostly concerned with the data signal though. I'll sort the rest out myself.
PLS SUM1
Ayyyyy Lmao
I'm not so excited about posting a question as I see many have gone unanswered specifically in this variant's section, but here goes nothing.
I accidentally downloaded DU (Dirty Unicorns) for the T-Mobile variant by searching up DU for tje S4 on Google and sadly i forgot to specify "Sprint" or "L720". While there where no issues running the ROM, I decided I had to flash back to a Sprint based rom. Somewhere down the road I decided to flash back to stock (using the stock OD2 currently available) and now my device still shows up as an M919 with absolutely no data (seems to be roaming if I'm not mistaking).
I tried to reflash TWRP, flash Sprint based roms (AOSP will fix the issue temporarily, while TW roms such as Wicked X will experience the same issue), FULL wiping through TWRP, and then reflashing stock, but the issue persists. Does anybody happen to have a solution, suggestion, or idea? And a HUGE thanks in advanced.
I think you need to flash a full firmware with a pit file in Odin. Just visit sammobile, create an account and you're good to go. Lemme know if you have further questions
Try to flash OD2 .tar (get it from sammobile) with odin and then root ur phone again. That should fix the problem
Never heard of a pit file, always thought that it was limited to .tar and .bin, but I found my solution which I will post below.
PS How do I hit the thanks button on your comment since it has no "interface" to it?
I tried that and it didn't work. I already had OD2 as my default "flash if something goes wrong".
I'll post my solution in a new answer below.
Sorry for neglecting my own thread to the both of you who answered, I'm just not liking all of the new updates to the XDA website which will crash my browser or freeze all my tabs due to an overloaded amount of crap and ads running in the background of the site (sorry XDA, huge fan, but not as of lately). Apart from that, I also experience issues on the mobile version and right now I cannot find the button to thank the both of you.
ANYWAYS, back on topic, I was able to solve my issue by flashing an older 4.4.2 based stock (NAE) THEN flashing the OD2 right after that. Oddly enough, I was able to update to OH2 (stagefright patch) over the air. Doesn't the ability to update OTA die once you trip the KNOX Warranty bit???
And thank you both. If somebody explains how I can hit your thanks button now that XDA has updated yet again, I will thank you both properly
Hi All,
I've flashed @DrakenFX back-to-stock zip's for U variant on my Chinese one, both BootStack and StockSystem zips.
happy to confirm that everything works except the cellular network basically making this a tablet
Trying to go back to Chinese stock, the boot stack for that model has no mirrors on the download page (ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip)
would appreciate if anyone has the file and can re-upload it. Till then I'm stuck with absolutely no phone :crying:
Another option I'm willing to experiment with is to flash the modem so it will work nicely with the U-everything-else.
If anyone has reason to believe this will work and has the modem binary I'll go for it.
Having the U variant supported bands is a-OK by me.
I would've commented on the dev thread but as I'm a new user I'm still not allowed to
Here : ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip , just FYI next time you try to use a different variant Rom, you just need System.img & Boot.img (Stock System zip in this case using my files) , YOU DON'T need other variants Bootstack
TgSn said:
Hi All,
I've flashed @DrakenFX back-to-stock zip's for U variant on my Chinese one, both BootStack and StockSystem zips.
happy to confirm that everything works except the cellular network basically making this a tablet
Trying to go back to Chinese stock, the boot stack for that model has no mirrors on the download page (ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip)
would appreciate if anyone has the file and can re-upload it. Till then I'm stuck with absolutely no phone :crying:
Another option I'm willing to experiment with is to flash the modem so it will work nicely with the U-everything-else.
If anyone has reason to believe this will work and has the modem binary I'll go for it.
Having the U variant supported bands is a-OK by me.
I would've commented on the dev thread but as I'm a new user I'm still not allowed to
Click to expand...
Click to collapse
Hi! I have the exact same problem - no carrier signal after I flashed B29 US ROM on my chinese Axon 7 although the rest of the phone works fine - could you please please please tell me if you got it working and how??
Best Wishes
Hi there.. I read somewhere that it's possible to flash the global ROM on the US model and unlock the 866mbps WiFi speed (2x2 mimo).. Is this actually possible? If so, is it possible to flash just the radio on Lineage OS and get the same effect?
@TgSn
Did ur problem solved if not, then may b i could help you
Waiting for your reply
Can someone please explain to me the importance of updating firmware?
What exactly is firmware that only Motorola can touch?
Why can't this be included while installing a ROM?
Does Motorola somehow have the capability to touch a certain partition that we cannot?
If you flash official Motorola stock ROM, how does it differ from flashing custom ROM?They cannot do the same thing?
Lastly, if the Samsung galaxy S3 is already running 7.1, then why must we update "firmware"?
I know for a certainty Samsung stopped pushing updates long ago for the S3. Please help I'm very confused by this! I've never known to do this in all my years of flashing yet you all keep mentioning it here! Only thing I've known to flash outside of ROM was the radio/modem/baseband whatever you wanna call it. And that was a flashable zip.
How can old phones get new custom ROMs if there are no official releases for current "firmware"? Thanks all! Links and input appreciated!
Sent from my Moto G4 Plus using XDA-Developers Legacy app
Updating the firmware is necessary because the firmware brings a newer version of bootloader and for it to be compatible you need the latest version of bootloader (B1.03 right now)
Other phones need firmware or driver updates too. Sometimes they can be baked into the rom or an additional zip. It's up to the manufacturer how they deploy drivers.
Also the well known sim on/off switch is a driver inside the modem. And if the manufacturer don't release the source you cannot see the changes and need the stock rom/files to flash them prior the custom rom to get newer drivers.
https://forum.xda-developers.com/moto-g4-plus/help/want-to-understand-explain-n-firmware-t3517850 for some more information.
Hey guys , my wifi isn't working and i cant upgrade to nougat ,while upgrading the file starts to install and then the phone reboots into recovery and stops there plz help ! Is this because of root ? But i have removed my root and twrp recovery ...... and after that i tried ota nougat zip file but it didnt flash
Nik11_98 said:
Hey guys , my wifi isn't working and i cant upgrade to nougat ,while upgrading the file starts to install and then the phone reboots into recovery and stops there plz help ! Is this because of root ? But i have removed my root and twrp recovery ...... and after that i tried ota nougat zip file but it didnt flash
Click to expand...
Click to collapse
Don't discuss here, ask your question in the thread you're following the instructions to upgrade to nougat please. BTW Your given information is not specified enough to help you out.
Thanks everyone for your assistance! I appreciate the information.
Sent from my Moto G4 Plus using XDA-Developers Legacy app
I'm hoping someone will have had the same issue I'm facing and have a solution.
A few weeks ago, I decided to go back to stock Nougat from a custom ROM. Everything went smoothly, but I cannot access 4G anymore. 3G works perfectly fine.
Solutions I have tried:
Factory reset
Reset carrier settings (* # * #72786# * # *)
Update PRL
Update device config
Contacted Sprint Support and had them reprovision
Restored backup of previous ROM
Flashed custom ROM
Reflashed modem
Replaced SIM card
Does anyone have any other suggestions?
Model: XT1687
Carrier: Sprint
Bootloader Unlocked
Kernel: 3.18.31-Extended-Kernel
Build: Sandy-Stock-Debloat-V2
There are many threads on here about it, but this will get you started. Be sure and take a back-up of your EFS right now before trying the fixes. https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
[email protected] said:
There are many threads on here about it, but this will get you started. Be sure and take a back-up of your EFS right now before trying the fixes. https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
Click to expand...
Click to collapse
Thank you. I have looked at that thread many times but didn't try it because Sprint doesn't have VoLTE. My dumb self didn't even think that it might fix my normal LTE issue as well. Cheers
Welcome to the g5 plus, the most screwed up out of all Moto. Personally I feel 64bit was the start of all the issues, could be wrong, just my penny's worth. But then again, before that, we had not a single custom ROM with stable camera, we still don't. Maybe Moto borked this one.