Related
Little background:
I was running Alliance and it was great, decided to be stupid and really wanted MIUI.
So...I stupidly thought I could make MIUI work (I know, I know, I'm retarded). Installed MIUI and of course soft brick, no biggie.
Then Odin'd back to stock (downgraded to NCE). Everything was fine.
Rooted w/ TowelRoot. Installed Busybox and Flashfire and then installed Twi5ted Lollipop.
APN settings wouldn't stick so I thought it might be something wrong with the ROM so then I installed TMS5 (wiped, etc) and everything worked.
Decided I wanted to back to Alliance and wiped, Flashfired Alliance and APN settings won't stick again.
Keeps saying SIM card not inserted, then it will grab a bar or two, then nothing. Try to change APN settings, they won't save, try to reset APN settings back to default, rebooted, etc etc etc.
TLDR:
1. Alliance
2. MIUI (softbrick)
3. Stock NCE via Odin
4. Root, flashfire, busybox etc
5. Twi5ted (APN no worky)
6. TMS5 (APN worky)
7. Alliance (APN no worky)
Thanks for any help!
lollipop-related
Bump.
So, I've read a ton of threads in the past week related to this issue. I have a gs2 on at&t and a gs3 on sprint, and I recently decided to jump away from good old kitkat for lollipop, so naturally I tried cm12 first. Great, both galaxy's love it. But I've tried everything under the sun to get APN's to stick. Ive only found one thing that worked, and its really only a temporary solution, because if you reboot, they ALWAYS get deleted and permissions to write get screwy again.
So, on both phones, I had to wipe everything and flash cm11. Then I dirty flashed cm12, which I didn't even think would work, but for some odd reason it did, and while still in the recovery console (before first boot!) I flashed one of those APN patch scripts to flash the APN's instead of trying to copy the XML later (it always gets deleted on next boot) nor use the actually APN utility in lollipop... And as long as you DONT connect to WiFi on initial setup when you boot, youll notice the flashed APN's show up in the list. DONT EDIT THEM... lol
They won't connect for a couple minutes usually, but after a couple minutes both phones connected... Idk if this will work on your gs5, but it worked for my 2 and my 3 which are both on different providers.
OK, I know that was long-winded and not that useful, but I tried literally everything to address this problem, with no luck. Apparently its super common across a ton of devices that upgrade to lollipop, whether a stock or custom ROM.
I tried setting permissions manually to EVERY ditectory or file that stores anything from the modem. In the data directory, in efs, in system... On every XML and db file. Nothing seems to allow them to be written correctly through the system. And everywhere I found anything on the Google dev forums, Google denied the possibility that its actually a system level problem, and their fault.
Good luck, and please let me know if you find any actual way to solve the APN issue, not like my tricky little workaround that SUCKS if your phone ever dies. lol
I know, I know, there are a ton of posts by people asking how to return to stock. My situation is quite peculiar though.
I was part of the Motorola Feedback Network and I got to test 5.1 Lollipop on my XT1053 along with maybe 100 other people a few months. I was quite fortunate, but I felt like messing around and I flashed CM12.1. Now that 5.1 is available for everyone, I want to go back since CM has a cell radio battery drain bug that isn't present in stock.
So here's the problem:
I am unable to return to 4.4.4 to receive the OTA. Because I was already on Motorola's 5.1, my bootloader, motoboot and other important files were all upgraded to 5.1 and I can't downgrade. I tried flashing them using fastboot but no dice. Thankfully, I had a back up of CM12 or else my phone would be bricked.
I tried downloading a flashable OTA but it won't install because it's expecting me to come from 4.4.4, not 5.1.
I think what I would need is a generic 5.1 zip for the XT1053 in order to return to stock, but what do you think?
Like I said, I have the CM12 back that restored just fine so my phone is functional so I'm in no hurry. Thanks for any help!
To those of whom have downgraded back to a rooted 4.4.4 IMG from a rooted 5.1 IMG
I started out on a 4.4.4 img from ComputerFreak and then I did all the steps in his readme to upgrade to the pre-rooted 5.1 IMG. Everything went smoothly and everything worked correctly. The reason I want to go back to KK is that the XPosed Mods I use most do not work on 5.1 just yet. So I decided to revert back to KK until those mods become available on LP.
I flashed back to stock KK. That was also successful. The only mishap that comes up when on stock KK is the "Uninstall Motorola Sensor Serivces firmware". I researched this and everyone said they did not know what it was and/or to just reboot the phone and it does not come up again. I did not choose to uninstall it or take any action besides rebooting the phone and it usually "goes away".
THE REAL ISSUE:
Whenever I flash any rooted KK IMG to the phone via mofo the wifi does not turn on, no matter which rooted KK IMG I flash to the Turbo. I go to turn on the WiFi and the little switch image simply goes back to off as soon as i release my finger.
The WiFi works on stock KK and any pre-rooted LP IMG. I have done multiple data and cache wipes. I did it every time after flashing a new IMG.
ComputerFreak and I have been trying to figure this out and no solution. He said he's had the issue before but doesn't remember how to solve it and that others have had it too.
Thanks in advance for any help!! :good::good:
zacw4328 said:
To those of whom have downgraded back to a rooted 4.4.4 IMG from a rooted 5.1 IMG
I started out on a 4.4.4 img from ComputerFreak and then I did all the steps in his readme to upgrade to the pre-rooted 5.1 IMG. Everything went smoothly and everything worked correctly. The reason I want to go back to KK is that the XPosed Mods I use most do not work on 5.1 just yet. So I decided to revert back to KK until those mods become available on LP.
I flashed back to stock KK. That was also successful. The only mishap that comes up when on stock KK is the "Uninstall Motorola Sensor Serivces firmware". I researched this and everyone said they did not know what it was and/or to just reboot the phone and it does not come up again. I did not choose to uninstall it or take any action besides rebooting the phone and it usually "goes away".
THE REAL ISSUE:
Whenever I flash any rooted KK IMG to the phone via mofo the wifi does not turn on, no matter which rooted KK IMG I flash to the Turbo. I go to turn on the WiFi and the little switch image simply goes back to off as soon as i release my finger.
The WiFi works on stock KK and any pre-rooted LP IMG. I have done multiple data and cache wipes. I did it every time after flashing a new IMG.
ComputerFreak and I have been trying to figure this out and no solution. He said he's had the issue before but doesn't remember how to solve it and that others have had it too.
Thanks in advance for any help!! :good::good:
Click to expand...
Click to collapse
Did you reflash the 4.4.4 modems and radios, or did you just flash the 4.4.4 system image? I'm assuming that when you upgraded to 5.1, you flashed the 5.1 radios and modems.
TheSt33v said:
Did you reflash the 4.4.4 modems and radios, or did you just flash the 4.4.4 system image? I'm assuming that when you upgraded to 5.1, you flashed the 5.1 radios and modems.
Click to expand...
Click to collapse
Yeah, I flashed the 4.4.4 modems and radios. Which I'm assuming that's why it works on a stock 4.4.4 IMG. But idk why when the phone has rot access it won't work.
zacw4328 said:
Yeah, I flashed the 4.4.4 modems and radios. Which I'm assuming that's why it works on a stock 4.4.4 IMG. But idk why when the phone has rot access it won't work.
Click to expand...
Click to collapse
I'd be willing to bet that it has to do with the sensor firmware message that you got before. That message is no joke. Something involving the sensor firmware or whatever that is destroyed my last Turbo, which was luckily still somehow under warranty after everything I did to it. If I were you, I'd try flashing back to stock 4.4.4 and if you see that message, pick uninstall this time.
TheSt33v said:
I'd be willing to bet that it has to do with the sensor firmware message that you got before. That message is no joke. Something involving the sensor firmware or whatever that is destroyed my last Turbo, which was luckily still somehow under warranty after everything I did to it. If I were you, I'd try flashing back to stock 4.4.4 and if you see that message, pick uninstall this time.
Click to expand...
Click to collapse
I get it when I am on stock 4.4.4. Do you know what it does though? I need my phone.. Everything is working on stock 4.4.4 and a 5.1 IMG. Just not rooted 4.4.4.
zacw4328 said:
I get it when I am on stock 4.4.4. Do you know what it does though? I need my phone.. Everything is working on stock 4.4.4 and a 5.1 IMG. Just not rooted 4.4.4.
Click to expand...
Click to collapse
I believe it's the firmware for the various sensors on the phone (IR, gyroscope, etc.). When mine got corrupted, it affected all kinds of things on the phone. It took literally 20 minutes to boot and android OS would force close, among other things. Flashing back to stock (all images) did not solve the problem, which seems to imply that the firmware is stored on a partition that isn't flashed even during a full restore. The only thing that solved the problem was allowing the firmware to uninstall. However, when I went back to 5.1, they got corrupted again, this time beyond repair.
It doesn't sound like yours are corrupted since your problems are limited to Wi-Fi, and aren't catastrophic like mine were. You probably just have the 5.1 version still installed, which doesn't play well with the 4.4.4 images for some reason. Why the problem only appears when you have root, I have no idea. Are you using a rooted image that sets SELinux to permissive? If not, that might have something to do with it.
TheSt33v said:
I believe it's the firmware for the various sensors on the phone (IR, gyroscope, etc.). When mine got corrupted, it affected all kinds of things on the phone. It took literally 20 minutes to boot and android OS would force close, among other things. Flashing back to stock (all images) did not solve the problem, which seems to imply that the firmware is stored on a partition that isn't flashed even during a full restore. The only thing that solved the problem was allowing the firmware to uninstall. However, when I went back to 5.1, they got corrupted again, this time beyond repair.
It doesn't sound like yours are corrupted since your problems are limited to Wi-Fi, and aren't catastrophic like mine were. You probably just have the 5.1 version still installed, which doesn't play well with the 4.4.4 images for some reason. Why the problem only appears when you have root, I have no idea. Are you using a rooted image that sets SELinux to permissive? If not, that might have something to do with it.
Click to expand...
Click to collapse
If it is the literal sensors for things like IR and gyro, that would make sense as my IR sensors are not on right now on stock, non-rooted KK IMG. But I am afraid that if I do the uninstall, the phone will not be usable.
I'm not sure if the IMG sets SELinux to permissive or not. @computerfreek274 any input on that?
zacw4328 said:
If it is the literal sensors for things like IR and gyro, that would make sense as my IR sensors are not on right now on stock, non-rooted KK IMG. But I am afraid that if I do the uninstall, the phone will not be usable.
I'm not sure if the IMG sets SELinux to permissive or not. @computerfreek274 any input on that?
Click to expand...
Click to collapse
If it's CF's image, it does. I would do that uninstall if I were you. It will replace it with the factory default firmware. Up to you. If you decide to do it, flash a stock, unrooted image first, and clear cache. Maybe even factory reset if it's not too much of a pain.
TheSt33v said:
If it's CF's image, it does. I would do that uninstall if I were you. It will replace it with the factory default firmware. Up to you. If you decide to do it, flash a stock, unrooted image first, and clear cache. Maybe even factory reset if it's not too much of a pain.
Click to expand...
Click to collapse
I'm already back on a factory KK IMG and did aa few factory resets and cleared cahce multiple times. So just go ahead and do the uninstall then?
zacw4328 said:
I'm already back on a factory KK IMG and did aa few factory resets and cleared cahce multiple times. So just go ahead and do the uninstall then?
Click to expand...
Click to collapse
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
TheSt33v said:
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
Click to expand...
Click to collapse
Alright. I might try it out tomorrow.
Look, man. I have fxzd from LP images (cf, thest33v) over and over again. eveey single time, I did the uninstall. seems the only way you will have an issue is if you do not uninstall (revert) that piece of software. you can mod the xml file in the FXZ by removing the line "erase user data" and all will be golden. personally, I tend to back up my internal and just wipe anyway, though. run the stock fxz, do that option, and you will be good. Good luck man.
kitcostantino said:
Look, man. I have fxzd from LP images (cf, thest33v) over and over again. eveey single time, I did the uninstall. seems the only way you will have an issue is if you do not uninstall (revert) that piece of software. you can mod the xml file in the FXZ by removing the line "erase user data" and all will be golden. personally, I tend to back up my internal and just wipe anyway, though. run the stock fxz, do that option, and you will be good. Good luck man.
Click to expand...
Click to collapse
TheSt33v said:
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
Click to expand...
Click to collapse
I just did the uninstall. It tried to download the 5.1 OTA(I keep force stopping MotoOTA) so I force stopped that again. After a second my phone rebooted. My IR sensors now work on stock 4.4.4. I haven't flashed a rooted 4.4.4 IMG yet to see if the WiFi will then work. I will do that sometime soon. This no root is killing me haha. Luckily I at least have a modded Pandora APK for no ads and unltd skips.
[EDIT]:
Well I still cannot use WiFi when flashing a rooted KK IMG to my phone.
zacw4328 said:
I just did the uninstall. It tried to download the 5.1 OTA(I keep force stopping MotoOTA) so I force stopped that again. After a second my phone rebooted. My IR sensors now work on stock 4.4.4. I haven't flashed a rooted 4.4.4 IMG yet to see if the WiFi will then work. I will do that sometime soon. This no root is killing me haha. Luckily I at least have a modded Pandora APK for no ads and unltd skips.
[EDIT]:
Well I still cannot use WiFi when flashing a rooted KK IMG to my phone.
Click to expand...
Click to collapse
That's bizarre. Have you been using the same rooted image every time? There might be something that's just corrupt in that image.
TheSt33v said:
That's bizarre. Have you been using the same rooted image every time? There might be something that's just corrupt in that image.
Click to expand...
Click to collapse
I've tried two different ones. They worked fine before I went to the rooted 5.1 img.
Edit: I solved it by going back to Stock rom, Android 2.2.1 Froyo. It didn't happen anymore, so it must be some software related issue which remained on the phone even after fully wipe including the OS. Now I will just need to root the phone again and flash custom roms on it.
Hi there,
When I bought my Samsung Galaxy S back then it came with Android 2.2 Froyo (or it was Eclair, don't remember), which I updated to 2.3 Gingerbread. Since then I flashed newer Android roms found on this forum. I never had any problems. So I had ICS (various versions), JB (various versions) and KitKat (I think I was on 4.4.0 and later on 4.4.4)
So up to Android KitKat 4.4.0 I used it on daily basis but after I got a new phone I didn't use it much anymore (I would only turn it on to make sure the battery won't die). But recently I turned it on, I can do things on the phone but when I leave the phone on standby it would eventually reboot on its own.
I tried installing an older version of KitKat. I picked one from an older date, which happened to be 4.4.2. The same issue happens there too. I just installed Android 6.0.1. made by Full Advance. and the issue happens there too.
My phone has an SD card inserted but no SimCard, anything else you need to know just ask.
I would like to keep Android 6.0.1 from Full Advance. It seems a fast and stable rom. It feels faster than the KitKat 4.4.4 I had.
I would be glad if the issue on the self reboot would be solved. I want to use this phone as a MP3 player. I really like AudioFX.
Any help appreciated, thanks!
Hello all!
I've been looking around the forum for answers to my questions, but I'm still pretty unsure, and I'm worried about messing up my phone, so if someone could hold my hand a little bit, I would appreciate it so much!
When the marshmallow update came out, I unlocked my bootloader with Sunshine and installed TWRP and rooted. I'm currently on stock 6.0.1 and September 1, 2016 security patch.
Issue #1: Ever since I unlocked/rooted/updated to marshmallow I've had problems with some of my apps deciding they can't connect to the internet, even though WiFi and 4G are clearly connected. Like I'll be able to browse the internet on Chrome just fine, but the Amazon app won't connect.
From what I've read, it seems like a problem a lot of people have had after upgrading to marshmallow, but I'm still worried it's because I'm unlocked or rooted or have Xposed installed or something.
Restarting the phone seems to be the only thing that really makes the apps work again (temporarily). I read somewhere about clearing the cache from recovery and that seemed to have fixed the problem for a couple of months, but lately I've been having the problem again, and clearing the cache isn't helping beyond having to restart my phone to do it.
Issue #2: I've been scared to take the OTA security updates.. I've generally gathered that they won't relock my bootloader, but I'm unclear on if it's ok to take the updates OTA or if I have to download and install them through TWRP.
Also, do I even need those updates? Call me stupid, but I'm not that worried about security (the only thing I own is a massive amount of student debt, go ahead and take it =P). I'm really just hoping the updates fix the internet thing.. is that a possibility?
So overall I guess I'm asking, will taking the updates OTA wreck my stuff, and is there a chance updating will fix my internet connectivity problem?
Or will using a different ROM possibly fix my internet problem? If so, which ROM would you recommend? I used to have a Razr M with the latest (at the time) CM ROM, but I couldn't use Bluetooth and WiFi at the same time, so it kind of left a bad taste in my mouth about custom ROMs...
Any answers or advice would be greatly appreciated!! Thank you!!
If you have TWRP installed, NEVER take an OTA. You will bootloop or brick your phone. Instead just install the TWRP flashable version from this forum.
This is what you would flash, via TWRP if you want the latest firmware while keeping custom TWRP recovery.
[ROM] MCG24.251-5-5 100% Stock
https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
Perhaps re-flashing your modem might help? It's also at that thread. TWRP flashable version.
By popular demand, here are just the modems: https://www.androidfilehost.com/?fid=745425885120733904
Click to expand...
Click to collapse
Ok, thank you ChazzMatt!
birdgofly said:
Ok, thank you ChazzMatt!
Click to expand...
Click to collapse
As for custom ROMs, for you who is not that experienced I would suggest this one:
Computerfreek274_1.0.8 Update Marshmallow 6.0.1 Global,De-bloated,Root,Volte, 5/29/17
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's actually a tweaked, debloated version of Verizon stock Marshmallow firmware. Everything will still work, including Verizon VoLTE (on Verizon, of course, not other networks). Has slight volume boost, battery optimization, etc.
And of course, lots of experienced users are also running that ROM. I do not mean to criticize it in any way, but you just mentioned that you ran some ROM where some stuff didn't work. This is a ROM built on stock, not CM/LOS based. Nothing much has been changed, just bloatware removed and some tweaks.
No worries, that ROM sounds perfect!
Thank you very much for all of your help!!
birdgofly said:
Hello all!
I've been looking around the forum for answers to my questions, but I'm still pretty unsure, and I'm worried about messing up my phone, so if someone could hold my hand a little bit, I would appreciate it so much!
When the marshmallow update came out, I unlocked my bootloader with Sunshine and installed TWRP and rooted. I'm currently on stock 6.0.1 and September 1, 2016 security patch.
Issue #1: Ever since I unlocked/rooted/updated to marshmallow I've had problems with some of my apps deciding they can't connect to the internet, even though WiFi and 4G are clearly connected. Like I'll be able to browse the internet on Chrome just fine, but the Amazon app won't connect.
From what I've read, it seems like a problem a lot of people have had after upgrading to marshmallow, but I'm still worried it's because I'm unlocked or rooted or have Xposed installed or something.
Restarting the phone seems to be the only thing that really makes the apps work again (temporarily). I read somewhere about clearing the cache from recovery and that seemed to have fixed the problem for a couple of months, but lately I've been having the problem again, and clearing the cache isn't helping beyond having to restart my phone to do it.
Issue #2: I've been scared to take the OTA security updates.. I've generally gathered that they won't relock my bootloader, but I'm unclear on if it's ok to take the updates OTA or if I have to download and install them through TWRP.
Also, do I even need those updates? Call me stupid, but I'm not that worried about security (the only thing I own is a massive amount of student debt, go ahead and take it =P). I'm really just hoping the updates fix the internet thing.. is that a possibility?
So overall I guess I'm asking, will taking the updates OTA wreck my stuff, and is there a chance updating will fix my internet connectivity problem?
Or will using a different ROM possibly fix my internet problem? If so, which ROM would you recommend? I used to have a Razr M with the latest (at the time) CM ROM, but I couldn't use Bluetooth and WiFi at the same time, so it kind of left a bad taste in my mouth about custom ROMs...
Any answers or advice would be greatly appreciated!! Thank you!!
Click to expand...
Click to collapse
There's a complete TWRP flashable update to the latest '5-5' firmware. Saves you the time of putting stock recovery back on and taking it OTA. The TWRP flash won't install the stock recovery, TWRP will stay. There's also a zip to clear/reset the radio/modem. You may not need that due to updating the rom.
Sent from my XT1254 using Tapatalk
So just an update for anyone who might come across this thread later.. I ended up flashing the ComputerFreek ROM suggested by ChazzMatt (didn't clean install, just wiped cache). It worked great, and so far I haven't had any more problems with apps not being able to connect!
Thank you to ChazzMatt, ComputerFreek, Einsteindks, and the wonderful XDA community for all your help