Hey guys,
I have a dual sim Indian version Moto G (xt1033) with stock kitkat rom. I am facing a very peculiar problem. When I try to restore a CWM back-up with xposed installed my phone does not have any signal (cellular and wi-fi don't work). When I go into settings, the cellular and wi-fi settings are greyed out.
I also tried to disable xposed before taking a backup once but as soon as I booted, the phone's system UI kept crashing and I could not perform even a single action. I had no option but to restore my firmware and build it back up.
Now, I want to install xposed again but am afraid that I would not be able to take any more backups if I install xposed. Please guide me if there is any solution to this problem.
Just flash the latest radio and your good
CCody said:
Just flash the latest radio and your good
Click to expand...
Click to collapse
Thanks!
Related
Hello,
my stamina mode (4.3 Stock ROM, see signature) doesn't work properly anymore. Usually, network connections were disabled shortly after locking screen and by unlocking screen, network connections were established again (connection symbol needed 1-2 seconds to appear).
Now my connections do not get disabled anymore. I receive Whatsapp messages even after an hour of not using my device e.g. and the connection symbol is already there like the device was never disconnected.
I do not have any exceptions in my stamina settings. I had Whatsapp in there for testing purposes, but removed it. I've got the feeling that this problem exists since I've once tested the Whatsapp exception...
The first and easiest way is a factory reset of your phone before doing anything else.
Have you ever made a factory reset after switching from android 4.1.2 to 4.3?
I came from CM to 4.3; first the leak versionn, then .199 and finally .210 - each with full wipe. That should not be the problem; stamina mode worked properly on every stock 4.3. It is broken for only one or two weeks now.
Of course i could do a factory reset or a CWM backup from a clean 4.3 installation, but I hoped to solve it another way, e.g. reinstalling a certain APK or editing sth. in the system
dyfk3l said:
I came from CM to 4.3; first the leak versionn, then .199 and finally .210 - each with full wipe. That should not be the problem; stamina mode worked properly on every stock 4.3. It is broken for only one or two weeks now.
Of course i could do a factory reset or a CWM backup from a clean 4.3 installation, but I hoped to solve it another way, e.g. reinstalling a certain APK or editing sth. in the system
Click to expand...
Click to collapse
You can flash .210 again via recovery WITHOUT any wipe.
The zip file will format and install a clean system (with all original apk, framework and so on)
istux said:
You can flash .210 again via recovery WITHOUT any wipe.
The zip file will format and install a clean system (with all original apk, framework and so on)
Click to expand...
Click to collapse
I prefer original FTF files when using stock ROMs, so that I can customize it according to my taste.
To topic:
I've restored a CWM-backup of the fresh installed stock ROM, but same problem... strange. We'll, the best way should be reinstalling the whole ROM *grrrrrr*
Thanks anyway!
dyfk3l said:
I prefer original FTF files when using stock ROMs, so that I can customize it according to my taste.
To topic:
I've restored a CWM-backup of the fresh installed stock ROM, but same problem... strange. We'll, the best way should be reinstalling the whole ROM *grrrrrr*
Thanks anyway!
Click to expand...
Click to collapse
Good choice.
By the way also with Flashtool you can flash only the system this way: uncheck all inside wipe box and check all inside exclude box, but system that has to be unchecked.
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
nonameguy321 said:
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
Click to expand...
Click to collapse
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
385
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
nonameguy321 said:
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
Click to expand...
Click to collapse
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
majmoz said:
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
Click to expand...
Click to collapse
Maybe I should have left out the part of the front facing camera not working.. or created that as a separate topic.
The one that I'm really having issue with is the Insertcoin Konfig settings not actually applying themselves.. tweaks on other ROMs worked without a problem..
i Am using motorola droid turbo android 6.0 reserrection remix rom.
Is there any way i can do wifi calling using custom rom?
bilalrajput said:
i Am using motorola droid turbo android 6.0 reserrection remix rom.
Is there any way i can do wifi calling using custom rom?
Click to expand...
Click to collapse
https://youtu.be/nF_lJTGKFP0
TheSt33v said:
https://youtu.be/nF_lJTGKFP0
Click to expand...
Click to collapse
I'm limited to 8 thanks per day. I'll come back later.
TheSt33v said:
https://youtu.be/nF_lJTGKFP0
Click to expand...
Click to collapse
The only thing that would have been better is this one...
https://www.youtube.com/watch?v=xoMgnJDXd3k
rnwalker7 said:
The only thing that would have been better is this one...
https://www.youtube.com/watch?v=xoMgnJDXd3k
Click to expand...
Click to collapse
I'm making it a personal goal to respond to as many questions with youtube videos as possible.
I use Google Hangouts and their add-on app for WiFi calls. Have to have Google voice number to do this.
Sent from my MetroPCS Turbo
Ok a simple question
I am on stock official 6.0.1
I can't find wifi calling option :/
Where to find it and how to make a wifi call?
Sparksys said:
Ok a simple question
I am on stock official 6.0.1
I can't find wifi calling option :/
Where to find it and how to make a wifi call?
Click to expand...
Click to collapse
Advanced calling menu
It's not there..no advanced calling menu anywhere
I'm on computer freeks mm.1.0.4 stock based ROM
It's under advanced calling as mentioned.
Not for me :/
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Hyperbomb64 said:
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Click to expand...
Click to collapse
I see the same behavior. I'm also unlocked, rooted with twrp. No exposed though.
Sent from my XT1254 using Tapatalk
Hyperbomb64 said:
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Click to expand...
Click to collapse
Have you tried turning Wi-Fi back on after Airplane mode turns it off?
Airplane mode turns OFF Wi-Fi.
https://www.howtogeek.com/194421/what-does-airplane-mode-do-and-is-it-really-necessary/
Enabling airplane mode always disables Wi-Fi. However, on most devices, you can enable Wi-Fi after enabling airplane mode. Cellular signals will still be blocked, but Wi-Fi will be working so you can connect to that in-flight Wi-Fi network. Some devices also allow you to enable Bluetooth when airplane mode is enabled.
Click to expand...
Click to collapse
Yeah tried that.
Would there be any way to turn off the radio other than using airplane mode? Also does this feature actually work using verizon wifi calling built into marshmallow?
Sent from my XT1254 using Tapatalk
So it seems that flashing SuperSU causes wifi calling to stop working. I flashed stock recovery and firmware, downloaded the new OTA, flashed TWRP and wifi calling continued to work. As soon as I flashed SuperSU it stopped. Anyone stock and rooted that has wifi calling working?
Hyperbomb64 said:
So it seems that flashing SuperSU causes wifi calling to stop working. I flashed stock recovery and firmware, downloaded the new OTA, flashed TWRP and wifi calling continued to work. As soon as I flashed SuperSU it stopped. Anyone stock and rooted that has wifi calling working?
Click to expand...
Click to collapse
What version of SuperSu did you use? And if it was the older beta 2.62, did you then update it to the latest version afterwards?
First way I tried was the bets 2.62 to see if it would work. When it didn't I restored my nandroid backup and then flashed beta 2.62 then 2.79 per TheSt33v's guide (select the beta zip then select add more zips and select the latest).
Hyperbomb64 said:
First way I tried was the bets 2.62 to see if it would work. When it didn't I restored my nandroid backup and then flashed beta 2.62 then 2.79 per @TheSt33v's guide (select the beta zip then select add more zips and select the latest).
Click to expand...
Click to collapse
Not to contradict him... but when you flash the beta SuperSu to do intitial root for this finicky version of Motorola Marshmallow firmware, you should then reboot to your desktop make sure it works -- that you actually have root -- then reboot back into recovery and flash the newer SuperSu.
In my opinion, that's the best way. Yes, there are many times I consecutively flash zipped files in TWRP, but flashing two vastly different versions of SuperSu is not one of them.
Hyperbomb64 said:
First way I tried was the bets 2.62 to see if it would work. When it didn't
Click to expand...
Click to collapse
Are you saying flashing that beta SuperSu WILL didn't root your phone or didn't allow Wi-Fi calling to work? That version of SuperSu WILL root your phone -- but you will just need to update to newest version afterward.
I've attached that beta SuperSu to this post.
ChazzMatt said:
Not to contradict him... but when you flash the beta SuperSu to do intitial root for this finicky version of Motorola Marshmallow firmware, you should then reboot to your desktop make sure it works -- that you actually have root -- then reboot back into recovery and flash the newer SuperSu.
In my opinion, that's the best way. Yes, there are many times I consecutively flash zipped files in TWRP, but flashing two vastly different versions of SuperSu is not one of them.
Are you saying flashing that beta SuperSu WILL didn't root your phone or didn't allow Wi-Fi calling to work? That version of SuperSu WILL root your phone -- but you will just need to update to newest version afterward.
I've attached that beta SuperSu to this post.
Click to expand...
Click to collapse
I have done both ways meaning flashed beta version of SuperSU, booted, confirmed that I have root, then update. Also I have flashed both and can confirm that I still have root.
So I'll run through it again and check, but I should be able to flash stock firmware, check if wifi calling is working, flash Beta SuperSU, confirm that phone is rooted, update to latest SuperSU, then check if wifi calling is working. Would those steps be correct?
Sent from my XT1254 using Tapatalk
I have a WW firmware installed on my phone and rooted with magisk 20.0. Whenever i try to update my phone to the latest firmware it installs without any issues but the wifi stops working. When i click to connect to wifi it turns on, scans for 2 seconds and the nturns off automatically. Can someone help me with this
Spawn_Ishan said:
I have a WW firmware installed on my phone and rooted with magisk 20.0. Whenever i try to update my phone to the latest firmware it installs without any issues but the wifi stops working. When i click to connect to wifi it turns on, scans for 2 seconds and the nturns off automatically. Can someone help me with this
Click to expand...
Click to collapse
Hmm, sorry dude, much as I'd love to help I'm not sure why this happens to a few people. You say you are rooted, you could always install swift backup from the playstore, backup your apps, data, WiFi passwords etc DON'T FORGET TO COPY THE BACKUP FOLDER TO YOUR PC, and your pics /downloads, then follow this guide to flash latest raw and see if that fixes your problems...
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
Then reinstall swift backup followed by your apps and data... That'll get your phone running on the latest 1910.35 raw rom. Hope it helps...
Hi!
I previously had rooted my S7 Edge with Super SU v2.79 years ago but now I want to switch to Magisk because I need to hide root from certain apps. Magisk fails to install saying:
! Boot image patched by unsupported programs
! Please restore to stock boot image.
Click to expand...
Click to collapse
From here I read I can try unSU. But in my case it did not work. How exactly can I fix this now? As I understand I need to reflash some stock images? But what exactly is the minimum requirement? Just boot.img? Or system? Also if I don't want to loose my apps, data, config, can I flash them without loosing them? Or if not is it possible to hide root while still using SuperSU since I really don't want to lose my data/apps/config.
You get the info to restore the stock boot image, which is just the kernel image. As you are rooted right now, use a backup tool like Swift Backup (full version is paid) or Neo backup (FOSS) to backup all app data and apps and personal data in case something goes wrong. Backup that stuff to your PC of course, saving all data that was created by the backup app and your other stuff. Then flash stock kernel, test if all is good and stick to Magisk stable plus needed modules.
Next time please provide all system data like used (custom?) ROM and Android version. If you use a custom ROM you need to revert to the unrooted custom ROM kernel of course.
Thank you for your response!
I am not rooted currently as I uninstalled Super SU but I think I can install it back if needed. Will flashing stock kernel always cause app data to be lost? Or is there chance that it does not get touched? As for ROM I use stock android 7 rom. I am not sure where and if can I still find it.
I don't really trust backup because because previous attempts have ended up with boot loops and broken apps. If there is chance that that app data stays intact without backup then I might try it but if the process factory resets everything and then relies on restoring backup as one part of the process then for now I would try to come up with some other solution.
Also will it cause all the stock bloatware to come back or is the kernel separate from apps?
sysctl said:
Thank you for your response!
I am not rooted currently as I uninstalled Super SU but I think I can install it back if needed. Will flashing stock kernel always cause app data to be lost? Or is there chance that it does not get touched? As for ROM I use stock android 7 rom. I am not sure where and if can I still find it.
I don't really trust backup because because previous attempts have ended up with boot loops and broken apps. If there is chance that that app data stays intact without backup then I might try it but if the process factory resets everything and then relies on restoring backup as one part of the process then for now I would try to come up with some other solution.
Also will it cause all the stock bloatware to come back or is the kernel separate from apps?
Click to expand...
Click to collapse
to back up use smart switch in pc, to install magisk is recommended to flash stock firmware first and instal magisk to avoid issues like bootloops