Related
FYI I installed the newest busybox and it broke wifi as well as cell reception. Won't recognize the sim. I found this post below as well... going to have to odin when I get home. i have the i957
- - - - -
just for the docs:If you installed Busybox on a rooted OneX with stock ROM, and removed some symlinks in /system/bin, make shure to keep /system/bin/insmod and /system/bin/chmod untouched or link it with /system/xbin/busybox (or wherever you installed busybox to).*If you don't, you phone will not prompt for the SIM PIN and will not show any network operator or signal.If the phone starts, the file /system/bin/poweron_modem_fls.sh gets executed. This file will call a binary named IMCdownload which has /system/bin/insmod hardcoded. If this insmod is nonexistent the IMCdownload will fail and /dev/ttyACM0 (the GSM modem terminal) does't get created.Next, gsm0710mux is called. This tool talks to /dev/ttyACM0. It tries to run /system/bin/chmod (even hardcoded). If this fails, the phone will not prompt for the SIM PIN even.It took me two days and a nearly bricked OneX to figure this out.Maybe its helpful so someone
Sent from my SAMSUNG-SGH-I727 using xda premium
Mine is broken also.
Hey guys, This isn't a problem with Busybox, It was a bug in my application.
The bug was present in version 8.0 I pathced the bug as fast as possible in 8.1 but a lot of people still got it because of caching issues.
What happened was that it symlinked all applets to busybox which means it overwrote some system applets that on some devices shouldnt be overwritten. I didn't catch this bug because my device was not affected by this.
To resolve this issue, simply reflash your current rom. You do not have to wipe any data.
When you reboot this should resolve the problem.
Again I want to apologize for this problem and annoyance.
Best Regards,
Stephen - Stericson
Thanks for the response!
Sent from my SAMSUNG-SGH-I727 using xda premium
Your welcome, did you get it fixed?
I really hate that this happened so I am trying my best to help everyone get back up and running. Hopefully too many people won't hate me after this goof.
Stericson said:
Your welcome, did you get it fixed?
I really hate that this happened so I am trying my best to help everyone get back up and running. Hopefully too many people won't hate me after this goof.
Click to expand...
Click to collapse
Yea works just fine, just odin flashed a new rom. I've been in much worse situations, just hope the people who don't know as much are ok.
Sent from my SAMSUNG-SGH-I727 using xda premium
A lot of them have been emailing me and so far I have had success getting them all back on track.
and I've made found two threads on XDA about it and have posted there, so I'm trying to make sure all is right in the world
Stericson said:
A lot of them have been emailing me and so far I have had success getting them all back on track.
and I've made found two threads on XDA about it and have posted there, so I'm trying to make sure all is right in the world
Click to expand...
Click to collapse
It's great you are doing that as a dev.
Sent from my SAMSUNG-SGH-I957 using xda premium
I'm using the stock rom of Galaxy Tab 7.7, the latest version of Busybox break wifi, and I can't access Google Play, Gmail, I can't install or uninstall from within busybox, and the terminal emulator won't work neither. So i can't install new version, can't access to command line, can't get rid of the installed version.
The rom refreshing is troublesome, since I'm using the stock rom and stock recovery. Is there any simple fix for this situation???
scubajeff said:
I'm using the stock rom of Galaxy Tab 7.7, the latest version of Busybox break wifi, and I can't access Google Play, Gmail, I can't install or uninstall from within busybox, and the terminal emulator won't work neither. So i can't install new version, can't access to command line, can't get rid of the installed version.
The rom refreshing is troublesome, since I'm using the stock rom and stock recovery. Is there any simple fix for this situation???
Click to expand...
Click to collapse
I suppose you could find someone to adb pull the missing files and then push them manually?
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
I suppose you could find someone to adb pull the missing files and then push them manually?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Galaxy Tab 7.7 is not a popular device. Besides, I really don't know which file busybox touched.
Reflashing took ten minutes and all my apps are fine. Didn't have to do a seperate root like last time so that was nice. Aslo the bloatware was removed.
Odin for I957 only:
http://forum.xda-developers.com/showthread.php?t=1658243
WiFi But No Mobile Network
I installed Busybox 1.20.1 and my WiFi still works fine but I have no mobile 3g network. I can call and text message fine also. Google Play and any other application requiring internet access only work while WiFi is enabled. Busybox 1.20.0 worked fine. I have a Casio Commando with a stock rom. I have tried uninstalling busybox but it fails every time, telling me the system will bootloop. I have tried unrooting with no luck also. What are my options to fix this?
What version of my app did you use to install Busybox? 8.0? Curiously if you were hit by the 8.0 bug you lost both.
The easiest way is just to reflash a stock rom. You should not have to wipe or lose any data.
Version 8.3
I've also read that the Casio Commando cannot be reflashed.
Did you change any of the smart install settings? If not, I'm a little unsure if the cause was Busybox.
The previous bug was caused by overwriting system applets that shouldnt be overwritten, that was fixed as of 8.1. so the only way it could overwrite something it shouldnt would be if you adjusted the pre-adjusted settings in smart install.
Have you tried a reboot to see if the issue persists after that? Or maybe a reinstall of Busybox? Maybe you got an incomplete install somehow?
Yeah, I tried all of that. I didn't change any settings either. It won't even let me use smart install anyway. I just used the regular install option. I waited for smart install to finish loading then installed 1.20.1 over 1.20.0 and then I had no mobile network. The 3g icon and bars show up and they're white but they're supposed to turn green. Mobile network settings look good too.
Maybe it's an issue with 1.20.1, Can you try rolling back to 1.20.0?
Yeah, I already installed 1.19.4, 1.19.3, and 1.20.0 after I installed 1.20.1. Right now it says BusyBox v1.19.3 is installed to /system/bin/
Can you run the command:
ls -l /system/bin
and show us the output?
Hello there everyone, total noob here.
I have tried to "root" my S3 LTE using this method: http://forum.xda-developers.com/gal...-cf-root-cwm-recovery-ported-supersu-t1914394 (or more likely this: http://forum.xda-developers.com/showpost.php?p=45291825&postcount=306 ). Everything went great, Odin has shown a pass and it was successful while installing CWM, then I installed Supersu through CWM (only thing I did differently was putting a supersu zip file on internal storage) and that was a success too. I did everything like it said, even without plugging out my phone. After rebooting everything went down...
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Now, I dont have root AND internet access.
Other info that might me useful:
Android 4.3
Null IMEI: no
Baseband: i9305XXUEMK1
I have performed factory reset, still no use.
Any help regarding repairing wifi, getting root access or bringing back state before "rooting" would be appreciated.
Regards,
Maziu92.
Maziu92 said:
Hello there everyone, total noob here.
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
Click to expand...
Click to collapse
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Maziu92 said:
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Click to expand...
Click to collapse
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
tharinduwijewardane said:
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Click to expand...
Click to collapse
Oh, I did it, that's why it said the binary was missing. But I did it other way around:
1. I have flashed CWM like it said in second link provided in first post
2. Installed SuperSU 2.02 from zip file on internal card though CWM instead of file provided in thread (I could have installed remove-boot-recovery too, but I didnt notice that I needed that. Anyway, I did that later)
3. Rebooted and tried to turn on - supersu was still blocked by knox :/ BUT!
4. I have installed manually supersu.apk, then opened it via installator (important! Dont tap 'done' but 'run'!) and next I didnt get the "missing binary" popup but if I want to disable KNOX. Well, yeah, I do, so I tapped OK and it looped and looped... http://www.reddit.com/r/galaxys5/comments/2a92qq/supersu_stuck_disabling_knox/cisq087 found this soulution and it worked (reboot phone and start supersu again). Sorry about my short memory, but I think I needed to install supersu.apk manually again and tap disable once more time, but disabling KNOX took a few seconds.
5. And then I went to the settings in Supersu and tapped option 'install supersu into /system', rebooted and it worked fine!
5.a To make sure it really works I downloaded (via 3g ) Root checker and it said it is rooted.
So now I have root, yaay, but still no Wifi access :/
tharinduwijewardane said:
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
Click to expand...
Click to collapse
I have been using odin 3.07.
Really, It is the only way to get back wifi? Are there any other options apart this?
Nooby questions:
-will it work with my phone? It says that its "MODEM: I9305XXUFNI3" and mine is XXUEMK1.
-in the meantime I have read about efs files/folder, what are they for and should I somehow backup them?
-while flashing 4.4.4 it is possible that my IMEI will go null?
-will it be possible to go back to 4.3?
I dont want to brick it or anything, thats why I am asking.
And of course, thanks for your help, Tharinduwijewardane ^^
Edit:
Actually, I have managed to repair my WIFI connection without flashing new rom etc.... So what was wrong, you will ask? Me.
I have downloaded adblock (before factory reset) and it asked to connect via proxy, so I did. And then I have disabled it because it was blocking SuperSU along with KNOX. And my phone tried to connect with internet via proxy, but it couldnt, because of this configuration.
Found this by complete coincidence (my GF told me to check if I get connection though Chrome and it said that it cant connect because of proxy settings). It is strange that this configuration was still there, even after factory reset.
Oh well, case solved, thanks again for helping and even everyone else for checking this out^^
glad to hear u got it fixed.
:good: :good:
So I did a factory reset and flashed the rooted H811 system image exactly as per instructions from the other thread and everything has been working flawlessly, except my HotSpot. When I try to turn on the Mobile Hotspot, I get a pop-up saying "Unfortunately, WiFi has stopped" and the ON/OFF toggle for the HotSpot stays off. Then, when I try to turn it on again, this time I get a toast notification saying "Activity is not exist this device." So it looks like it's looking for an application that's missing?
EDIT: SOLVED! Do not freeze the Upsell (com.lge.upsell) application, as that's what HotSpot uses to verify your tethering status with T-Mobile, as well as display the first time use tutorial.
It has nothing to do with recovery. It was my own mistake.
No issues for me so far with hotspot. I even have all the apps you listed frozen in TB.
Mine works fine also. Not sure what the problem could be.
now that we are rooted i am using wifi tether router by fabio and it works great. also bypasses tmobiles limit which i believe is 2 gbs or so of tethering. costs 2 bucks but imo its totally worth it
I just tried it on my G4 and didn't have any issues. I'm also on tmobile and rooted.
Sent from my LG-H811 using XDA Free mobile app
Okay, thanks for confirming, guys.
EDIT: I figured it out. Do not freeze the Upsell (com.lge.upsell) application, as that's what HotSpot uses to verify your tethering status with T-Mobile, as well as display the first time use tutorial. It has nothing to do with recovery. It was my own mistake.
siraltus said:
Okay, thanks for confirming, guys.
I figured out what was wrong. I tried flashing TWRP 2.8.7.0 using Flashify (as per instructions in the post!) and I think it flashed the recovery to the wrong partition, wiping its contents. I guess it was a hidden system partition that contained something that HotSpot needed.
I KDZ'd back to stock without wiping user data, then flashed the rooted image, and HotSpot works!
So... DO NOT USE FLASHIFY FOR NOW!
Click to expand...
Click to collapse
I used flasify for twrp and my hotspot still works.
Sent from my LG-H811 using Tapatalk
KJW979 said:
I used flasify for twrp and my hotspot still works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I figured it out. Do not freeze the Upsell (com.lge.upsell) application, as that's what HotSpot uses to verify your tethering status with T-Mobile, as well as display the first time use tutorial. It has nothing to do with recovery. Thank you everyone for confirming it was not the recovery. It was my own mistake.
KJW979 said:
I used flasify for twrp and my hotspot still works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Same here with no issues.
I can't seem to find the com.lge.upsell application, I'm getting this error after typing:
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
I just want my unlimited tethering back ;__;
Flashed 10n update on my rooted H811, no problems with hotspot. If the other thread you're referencing is from here (http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858), it has been updated with a hotspot fix on a separate file.
restoring com.lge.upsell, fixed it for me as well. Thanks,
I have the same problem! After rooting (with 20p debloated unlocked roam), the hotspot is not working with the message "Activity is not exist this device." (verbatim!). The interesting part is that when I installed FoxFi, it worked! Of course it stopped after 15 minutes as it was a freeware. When FoxFi was running, I could see that native Hotspot app showed my mac as a tethered device and everything seemed very natural (besides the blue FoxFi logo on top). On uninstalling FoxFi, native HotSpot app started giving the same error message. I could not find Upsell (com.lge.upsell) app or apk on my phone. Please advise - I would like to continue using the native HotSpot app with my T-Mobile connection. Many thanks!
---------- Post added at 06:16 PM ---------- Previous post was at 06:01 PM ----------
metropical said:
restoring com.lge.upsell, fixed it for me as well. Thanks,
Click to expand...
Click to collapse
Can you share this APK please?
UPDATE: Went to recovery mode using flashify, downloaded zips using Android File Transfer from my mac, Flashed Stock 20p, followed by Extreme 20p (both flashed at the same time) and voila! Tether is back to work and I am giving this update through my phone's tether connection
The speeds are not so great, but I am tempted to blame it on T-Mobile and not on ROM:
The whole research and finding the zip files for 20p took the majority of time. Otherwise, the download itself should take <20 minutes, transferring files <5 min, flashing another 10 minutes and restart of the phone another 5 minutes or so (it is a dirty flash - it only bothered to update some 5 apps!)
I think it is corrupted ROM (I positively remember there was a glitch for whatever reason and i lost all my data - probably the glitch deleted relevant tether files as well). But now it is much easier!!!
Links to the ZIP files that I used:
http://forum.xda-developers.com/tmo...om-lg-g4-h811-20p-stock-rooted-radio-t3477821
http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
Many thanks y'all!!!
glad you found your way to it.
this was the issue I had. http://forum.xda-developers.com/showpost.php?p=62060665&postcount=8.
I had uninstalled com.lge.upsell as part of my own try to de-bloat and that was a step too far.
The 1st link you point to is the rom I used and the radio fix and hotpot/tether fix as well.
There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***
First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.
I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!
Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.
biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.
is Snapchat also broken
Sent from my HTC One using Tapatalk
SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:
Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards
CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.
CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.
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