Every now & then the wifi calling option disappears from my Settings, and I can't figure out what's causing it to go. I'm running a rooted version of the last stock VS3 T-Mobile rom, with Xposed. I noticed this morning that the icon had gone, so I checked the More Networks menu, and sure enough, it had gone again. I just reflashed GPK3, installed TWRP, SU & Xposed and Wifi calling is back, so there must be something else I'm doing that's disabling it, I just can't figure out what!
invisiblewave said:
Every now & then the wifi calling option disappears from my Settings, and I can't figure out what's causing it to go. I'm running a rooted version of the last stock VS3 T-Mobile rom, with Xposed. I noticed this morning that the icon had gone, so I checked the More Networks menu, and sure enough, it had gone again. I just reflashed GPK3, installed TWRP, SU & Xposed and Wifi calling is back, so there must be something else I'm doing that's disabling it, I just can't figure out what!
Click to expand...
Click to collapse
AFAIK, only Touchwiz stock Roms and kernels support WiFi calling on T-Mobile.
Is VS3 an international or custom Rom? If so, that is the problem.
Rob
VS3 is the stock ROM for the G900T3. VS1 is stock for the G900T. Anyway, after more experimentation, I think I've answered my own question, the problem appears to be Xposed. It's not as simple as Xposed just breaking Wifi calling because I've had them both running successfully on this phone and also on the G900T we also own. I'm still tinkering though. Until now I've been using an old Wanam-modified Xposed module for TW, I'm just about to install his latest version and see if that helps.
I've also refined my method for installing the security updates, in case anyone else is still struggling with them. They don't touch /data at all, so you can safely flash them without wiping and without having to do any restores (assuming you're running rooted stock, as I do). Here's what works, it's very safe but a belt-and-braces approach is best, so do a TWRP backup first:
Download the update from Sammobile or some other reputable source.
Boot into Download mode (Bootloader) (hardware combo is Vol-, Home & Power together, keep hold of them until rebooting starts).
Open Odin, uncheck Reboot, click on AP button and select the downloaded image, then click Start.
Once finished and you get the Pass notification, reboot phone manually back to Download mode (Vol-, Home, Power, keep hold of them until rebooting starts).
Close & open Odin, uncheck Reboot, click on AP button and select your TWRP tar file, then click Start.
Once finished and you get the Reset notification, reboot the phone manually to RECOVERY MODE (Vol+, Home, Power, keep hold of them until rebooting starts). Don't sweat it if you don't get the reboot right, it'll just boot to system and the recovery flash won't have taken, just boot back to Download mode, re-flash TWRP, and boot back to RECOVERY mode.
Phone should boot to TWRP, then just install the SuperSU zip, followed by Xposed (optional).
Reboot System, phone will reboot, rebuild the Art/Dalvik cache, and you'll be back as you were but on the new security-patched version.
Update: It looks as if the latest Wanam-modified version of Xposed solves the problem. I've installed it along with FireFDS which gives me pretty much all the customizations I want and after several reboots WiFi calling is still active. To fix, I followed the steps outlined above with a slight modification, I flashed the latest stock image, VS3GPK3, then rebooted to stock recovery which does its "installing system update" thing, checked WiFi calling was working on stock (it was), then rebooted back to Download mode, flashed TWRP, installed SU, rebooted to ensure WiFi calling still worked (it did), booted to recovery and installed the new Xposed module (87.1), rebooted, then installed FireFDS & rebooted again. I don't know for certain if doing the stock recovery update thing made any difference, my guess is it might have, and it doesn't hurt to do it.
Update 2: I noticed earlier that the WiFi calling also wasn't working on the G900T. The icon was there earlier, but not when I checked this evening. I took the opportunity to experiment with the boot to stock recovery theory, and that appears to be the key to getting WiFi calling to work with Xposed. I tried first the quick way, flashed VS1GPK3, booted back to Download and flashed TWRP, booted to TWRP & flashed both SU & Xposed. Booted to system and the WiFi Calling option was missing altogether. I started again, flashed VS1GPK3, booted to stock recovery, let the phone boot and WiFi Calling was back and working. I then booted back to Download, flashed TWRP, booted to TWRP, installed SU, rebooted the phone, WiFi calling still working, so I then flashed Xposed and rebooted, and bob's your uncle, it works!
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
After rooting, I installed safe trap on my razr 912 CDMA, (no bootstrap).
1. Went to safetrap 1.0 recovery, data wipe, safetrap ENABLED and tried installing GUMMY 1.0.0 and gapps.
Tried rebooting but, after pressing the 'search button' key to start the ROM boot, it doesnt show anything , complete blank screen. rebooted few times, factory reset ,etc, didnt help.
2. Went back and DISABLED safetrap, which restored my initial copy of the stock, rebooted and it worked fine, my intial Stock ROM was up and running.
3. I doubted that this was issue with safetrap and not gummy installation; so to check that, I went to safetrap recovery, ENABLED safetrap. DID NOT INSTALL anything else.
Simply rebooted the phone, hoping the stock ROM to boot up since I did not install anything this time.
Result was the same...nothing on the screen....blank screen.
4. I went back and DISABLED safetrap and all was fine. Now stuck with stock ROM cant install new ROMS.
(I have no intention of trying bootstrap, because i did that on earlier Razr while installing Gummy 1.0.0 and it bricked the phone)
Question: it seems enabling safetrap, i am not able to bootup , no matter what. Any solution to this?
I tried to install a new theme on jasmine rom. I rebooted and phone said updating app, and remained on update app for over 5 minutes.So I rebooted and the phone remained in the jasmine boot screen. I knew I had a problem so i rebooted into recovery, did a complete wipe and installed my backup and rebooted. The phone started to reboot (Lg splash screen) and then stopped. The screen went dark and my red and blue LED lights started blinking. I tried to get back into recovery manually. I was able to get to stock recovery, hit factory reset and instead of going to TWRP, it went back to the black screen and the blinking LED lights. Same results occurred when I hit safe boot.
I also tried to get in DL mode with the volume up button. Instead, the LG splashscreen came on for less than a second, the screen went black and the blinking lights came again. I tried ADB but it won't recognize my phone. Any suggestions, or is this a goner? Thanks for your help.
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
rp201 said:
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
Click to expand...
Click to collapse
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I did the exact same thing early today and stumbled on that same thread. So relieved
jlokos said:
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
Click to expand...
Click to collapse
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
ohlin5 said:
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
Click to expand...
Click to collapse
I have no clue what happened; Verizon sent me a new phone. I don't have a clue whether this was related to the theme, or not. It may have been an unrelated hardware issue.
So I followed these instructions to root my LG G3 https://www.reddit.com/r/LGG3/comments/3qcctd/how_do_i_root_a_vs985_running_511_35b/cwe6756. Everything worked fine at first,I downgraded and rooted kitkat,then installed TWRP. After flashing the ROM,nothing displayed on the phone. The phone is booting,I can feel vibrations and hear the volume up notifications,but I'm having trouble getting into recovery. I'm pretty sure this has something to do with the fact that I accidentally flashed the cache after flashing the 9.1 rom,and that I forgot to do a factory reset after the first one. What should I do now?
Can you put it in Download mode? Even if the screen doesn't display anything, you can tell that you successfully got it in Download mode by looking in Windows' Device Manager. You should already have installed the Verizon LG drivers, and preferably rebooted the PC, give the PC up to 10 minutes to load the drivers the first time you connect the phone in Download mode via a USB 2.0 port and with the original cable.
If you get it in Download mode, use LG Flash Tool 2014 to flash the 10B KDZ to make it easiest to root and put TWRP back on.
The problem definitely didn't have anything to do with not doing a factory reset. As long as you had wiped Cache, Dalvik/ART and Data.
By "flashing cache" if you mean wiping Cache, no, that shouldn't be the problem either.
JasmineROM 9.1 is just an update to 9.0; had you flashed 9.0 before 9.1? If not, then that's the problem.
What exactly do you mean about a problem getting into recovery? Do you mean you can't see that either or what?
I managed to get it fixed Since the phone was still working I was able to take screenshots of everything I was doing while hooked up to my computer until I could use Flashify to reboot into fastboot,then repeated the steps to downgrading using these instructions https://www.reddit.com/r/LGG3/comme...phone_stuck_in_factory_reset_status_2/cmlm3wo
It probably was getting into recovery and I just didn't notice since nothing was displaying,but its all working now,and I successfully flashed CM13 instead.
Hello guys,
I had a very strange problem with my Xperia Z3V. The phone was rooted and had philz touch installed. OS 5.1.1. The phone was charging and when I found it, it was rebooting itself continuously. So I went to philz touch recovery and tried to clear cache. Rebooted, and the phone passed Sony logo and started to boot the system, but after a while restarted itself. Then I went back to philz touch cleared cache and dalvik an retried. still the same. So I decided to format the system. still no success. But the problem I am facing now is that I am not able to enter recovery anymore. I can only enter system recovery which doesnt help at all. I tried to enter using safe mode but no luck reaching the philz touch recovery. Maybe philz touch has gone for good.
Any suggestion how to bring the phone to life once again?
Thank You all,
Same (sort of).
Two days ago one of mine stopped getting reception completely. After messing around with the SIM I decided something else is wrong.
It also won't cycle through reboot properly. Particularly, it won't shut down and gets very hot.
No new apps or messing with it. Just all of the sudden, on its own.
Now I can't get into Philz recovery to bring it back to a saved backup.
My other one is fine, and the two have identical apps, widgets and layouts.
If you had auto update Apps then you probably updated the su binary and/or the supersu that was included in the root kit published here. Don't update either. Something about the latest Supersu causes this. Just leave reflash the phone using Sony recovery app to stock. Then start all over. Phone will work fine. Don't update Supersu.