Related
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.
Q&A for [Radio][Modem][5.X.X] Updated Modem and radio files from oxygen os
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Radio][Modem][5.X.X] Updated Modem and radio files from oxygen os. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
its work on validus rom v8 , and i have more stable signal now , thanks
recover from oxygenOS fw.
Reply for script error while in twrp for flashing blisspop after using oxygen modem.
It was happened to me as well. What I did was;
Reflash cm12 firmware updater 21/03 followed by firmware updater 02/04. Then continue installing ROM, gapps, and etc. It worked for me at least.
Modem
I am currently running Blisspop...
Do I flash only the modem since I have the firmware provided by blisspop or I flash with the Oxygen firmware and modem?
Lost MMS
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
wttp said:
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
Click to expand...
Click to collapse
If you are precisely sure your APN is exactly as before, call your phone company and see if their 'reset' will help. Over these last several years and numerous ROM changes, it has solved my issues now about 3-4 times when nothing else was obvious, and it was always the MMS issue for me, as well. (Consumer Cellular)
JeffDC said:
If you are precisely sure your APN is exactly as before, call your phone company and see if their 'reset' will help. Over these last several years and numerous ROM changes, it has solved my issues now about 3-4 times when nothing else was obvious, and it was always the MMS issue for me, as well. (Consumer Cellular)
Click to expand...
Click to collapse
About 2 hours on the phone with Straight Talk, and no success. They sent several signals, but ... So tried reinstalling piece by piece and nothing helped. Won't be a show stopper for me as I don't send pictures much (everything else works great). Connection with the Full Oxygen Modem is the best I have ever had, and staying connected in spots I had no signal before.
Thanks for the help, but still a little miffed.
Answer to jasonx3 question
jasonx3 said:
I'm having this issue on CM 12s after flashing. i did a clean install from TWRP. i can't connect to LTE signal keep crashing. look at the signal icon you will see what i meant. will flashing this modem fix this?
Click to expand...
Click to collapse
This is an easy fix. Go to settings>mobile network> APN > select the correct carrier.
I had mine set automatically to T-Mobile and had to switch it to Metro PCS.
---------- Post added at 12:43 PM ---------- Previous post was at 12:37 PM ----------
wttp said:
Upgraded to Euphoria-OS-1.1-bacon-20150414 and newest modular mini-gapps 5.1 (20150410) , then flashed Full Oxygen 04-04-15 Bacon Modem flashable. Seem to have lost my ability to send and receive MMS. Everything else appears to be working. Reset APN and other settings to previous.
Any help would be appreciated as I am completely stumped. Thanks,
Click to expand...
Click to collapse
MMS app> settings> auto enable data and auto enable retrieve.
Should I flash only modem or whole firmware on cm-12-20150415-NIGHTLY? If I flash the firmware, will it be overwritten if I update cm12 rom? Sorry for my ignorance.
A great contribution
thanks
OxygenOS modem on encrypted CM12s
I sideloaded the OPO_OxygenOS_1_0-flashable-modem.zip file to encrypted CM12S with TWRP2.8.6. It didn't give me LTE at home where my wife's Moto E 2015 has it, but it did improve signal strength on LTE Discovery from -100 dBm to about -80 dBm but still EDGE. Will keep it until something better comes up.
Can someone please send a mirror of this modem and firmware? I am having bad luck downloading on main thread it always fails on Google drive and the mirror on main thread is wrong md5.
Thanks
Ty29 said:
Can someone please send a mirror of this modem and firmware? I am having bad luck downloading on main thread it always fails on Google drive and the mirror on main thread is wrong md5.
Thanks
Click to expand...
Click to collapse
Update ~ Never mind I figured out how to use Google drive.
Does it work with CyanogenOS and will it fix the signal dropping issue?
Can we backup current modem before flashing the new one ?
Hey can someone answer the question that has been asked a cpl times already if whether or not people on CM 12- or Blisspop like me- have to flash FULL or just MODEM. Sorry but i thought that's what this q&a was for
Revert back to original Modem
I had initially flashed the oxygen modem given in the first post. But later I figured out that the low reception was due to my location and not due to the cm modem.
Right now I want to revert back to my original modem settings and keep it open for future updates
what should be done here?
Do I need to erase and flash once again so that the future updates from OTA nightly will include any possible updates in modem too.
maxpayne1989 said:
I had initially flashed the oxygen modem given in the first post. But later I figured out that the low reception was due to my location and not due to the cm modem.
Right now I want to revert back to my original modem settings and keep it open for future updates
what should be done here?
Do I need to erase and flash once again so that the future updates from OTA nightly will include any possible updates in modem too.
Click to expand...
Click to collapse
CM has started to use the same modem as Oxygen OS (that you have) some weeks back. And anyways an update will overwrite your current, if it is newer.
Does the new Cm12 come with oxgenos radio & modem?
Does the new Cm12 come with oxgenos radio & modem? suppose if i have wifi or call quality issues in cm12 do i have to flash the modem or the whole firmware and is wiping necessary?
Not working on moto g xt1033
Hi,
i just flash this zip and after system reboot my phone is not turning on, so what is the issue here?
I've done everything correctly, followed every tutorial, and I'm still not having any luck. I started on stock rooted Lollipop, and all I was getting as installation aborted errors with using Lollipop Autorec. I've since flashed back to stock rooted Kitkat, which I've got the closest with. I've been trying to flash one of the newer nightly updates from Cyanogenmod (20150709 specifically). I've also tried using the first stable release, to no avail. I used one click root to root, which worked fine, and Autorec Kitkat installer for TWRP, which also installs fine, and I can get into recovery no problem. I wipe, I flash, and it boots up, but then it never loads. It ends up being stuck on a boot loop, and it's very frustrating because of how close I'm getting. A Cyanogenmod 11 snapshot flashed correctly, but I'd like to figure out the newer update problem. I'm on LG D800. I'm a complete noob at this stuff, and need a sensei to guide me, please. Thanks in advance.
(Update): I've just now tried installing the newest Resurrection Remix for LG G2, and that sticks me in a boot loop as well, so I have no idea what I have to do. Will update again in a moment because I'm going to try downloading stock Lollipop and the newest TWRP.
(Update 2): So, I've just done what I said I'd do earlier. I flashed the LP bootstack, then Resurrection Remix, then Gapps, and I'm getting a bootloop for that, as well, so I'm calling it a night, and going to bed. Someone please respond. I really need help.
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Yeah, I ended up trying that, and flashing Resurrection Remix, and I was still getting a boot loop on that, as well.
Really now said:
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Click to expand...
Click to collapse
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
(EDIT): Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Wezurii4694 said:
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
Click to expand...
Click to collapse
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Really now said:
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Click to expand...
Click to collapse
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Wezurii4694 said:
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Click to expand...
Click to collapse
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Really now said:
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Click to expand...
Click to collapse
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Wezurii4694 said:
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Click to expand...
Click to collapse
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Really now said:
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Click to expand...
Click to collapse
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Really now said:
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Click to expand...
Click to collapse
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Really now said:
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Click to expand...
Click to collapse
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Wezurii4694 said:
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Click to expand...
Click to collapse
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Really now said:
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Click to expand...
Click to collapse
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Wezurii4694 said:
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Click to expand...
Click to collapse
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Really now said:
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Click to expand...
Click to collapse
Oh, okay. Oh, when do I flash the kernal?
Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Really now said:
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Click to expand...
Click to collapse
I meant on Cloudy. I'm trying that out.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!
Hello, I've been using my moto g since it came out, a few months ago, when I was using CM 12, I've noticed that my 3g wouldn't toggle it, I mean, I wasn't able to turn it on, even with the "on" mark, the mobile data wasn't on, so I went back to 4.4, and as soon as I installed it, I've realised that the SMS would be the next problem. See, when I try to send a SMS, when choosing the contact would cause the APP to break, and even with 3rd party apps, the problem would remain, hope that somebody has the answers to those problems, sorry for my grammar, this freaking auto correct is driving me crazy.
This is pretty much guesswork as I'm not sure what model you have, the recovery you used, if you clean flashed everything etc' but.....I have a few ideas about what might have been(is) the problem(s).
I think your 3G issue was due to having a Kit Kat radio (modem) on a lolilliop ROM.... Did you flash the proper radio when you made the jump from 4.4 to LP?
As far as the MMS app breaking I'm assuming it force closes. My first question is did you clean flash the kit kat rom?
If so. And maybe even before clean flashing I would go to your app settings and clear data on your phone app, MMS, and also reset defaults to see if it provides a solution.
If not, most certainly a clean flash,wipe everything in recovery, except internal storage and reflash your rom and Gapps.
n0ts0smart said:
This is pretty much guesswork as I'm not sure what model you have, the recovery you used, if you clean flashed everything etc' but.....I have a few ideas about what might have been(is) the problem(s).
I think your 3G issue was due to having a Kit Kat radio (modem) on a lolilliop ROM.... Did you flash the proper radio when you made the jump from 4.4 to LP?
As far as the MMS app breaking I'm assuming it force closes. My first question is did you clean flash the kit kat rom?
If so. And maybe even before clean flashing I would go to your app settings and clear data on your phone app, MMS, and also reset defaults to see if it provides a solution.
If not, most certainly a clean flash,wipe everything in recovery, except internal storage and reflash your rom and Gapps.
Click to expand...
Click to collapse
I used TWRP, and followed the official tutorial from here, can't remember if I did flash the radio, how do I flash it? Where can I find a tutorial for it? Couldn't find on the web, guess I'm not searching the right terms...
And for the SMS, can't remember aswell if I did clean flash, how is it made? Sorry for asking such things, I made this about 10 months ago...
First I would upgrade your recovery if it is 10 months old. My recommendation would be 2.8.7.0 for stability purposes. DL from here.
http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
You can find the radio you need from here. It is a flashable zip which I'm assuming you already know how to flash if you already are rooted with custom recovery. Make sure you flash the correct radio for your device. Know your model number. http://forum.xda-developers.com/showthread.php?t=2649763
If you are going from Kit Kat to LP or above you will also need to update your bootloader. The link will go into detailed info why and how. http://forum.xda-developers.com/mot...-questions-t2996087/post59520890#post59520890
Keep in mind you should decide your desired final result before anything. CM13(MM), CM12.1(5.1) then get everything(files) you need depending upon what you are trying to do. A flashable ROM of your choice and the coinciding Gapps package are the only other things I can think of to get you up and running.