after a lot of trial and error trying to determine why WiFi calling kept giving me the "Error: REG99 Unable to Connect" message, I was able to narrow it down to busybox pro found here. after I install this app WiFi calling breaks and I'm left with that REG99 message. if I remove busybox and reboot, WiFi calling is working properly again. I've scoured the Internet and there have been a few references to this, but no real solution other than to remove busybox. I'm posting here hoping someone may have a solution!
dimm0k said:
after a lot of trial and error trying to determine why WiFi calling kept giving me the "Error: REG99 Unable to Connect" message, I was able to narrow it down to busybox pro found here. after I install this app WiFi calling breaks and I'm left with that REG99 message. if I remove busybox and reboot, WiFi calling is working properly again. I've scoured the Internet and there have been a few references to this, but no real solution other than to remove busybox. I'm posting here hoping someone may have a solution!
Click to expand...
Click to collapse
Did you use the smart install option?
Swizzle82 said:
Did you use the smart install option?
Click to expand...
Click to collapse
yes! and it ended up choosing /su/bin... should I do something different?
dimm0k said:
yes! and it ended up choosing /su/bin... should I do something different?
Click to expand...
Click to collapse
I don't know if it was related to busybox, but I had been getting the same error until I reflashed a new system and factory reset. The first tine I had trouble getting the same busybox to load. After the second try it loaded in seconds and used smart install. Uninstall the busybox files through the app but not the app and then choose smart install>clean mode.. Not saying it will work but those are the options I choose everytime.
Swizzle82 said:
I don't know if it was related to busybox, but I had been getting the same error until I reflashed a new system and factory reset. The first tine I had trouble getting the same busybox to load. After the second try it loaded in seconds and used smart install. Uninstall the busybox files through the app but not the app and then choose smart install>clean mode.. Not saying it will work but those are the options I choose everytime.
Click to expand...
Click to collapse
whoa!! out of all the times I've opened up busybox in the past, I may have opened that "smart install" section once or twice and that was after busybox had already been installed so I never bothered to go back to it. so to confirm you were getting the same WiFi calling issue previously and it didn't install with smart install, but the second try it did use smart install? does this mean you currently have busybox installed and WiFi calling is working?
dimm0k said:
whoa!! out of all the times I've opened up busybox in the past, I may have opened that "smart install" section once or twice and that was after busybox had already been installed so I never bothered to go back to it. so to confirm you were getting the same WiFi calling issue previously and it didn't install with smart install, but the second try it did use smart install? does this mean you currently have busybox installed and WiFi calling is working?
Click to expand...
Click to collapse
Like I said, I'm not sure if my problem was your problem, I did have trouble installing it the first time I had rooted (I always install busybox right after rooting) and also had wifi calling issues(again, not sure if related). After I re-rooted and did a factory reset I installed busybox again, no issues getting it to install properly that time, wifi calling was also working again. You say you traced your problem to busybox and so I would suggest trying the smart install and see if that works.. If not try a factory reset. I'm pretty sure my issue was on the data rather than system side of things because a factory reset took care of it.
Swizzle82 said:
Like I said, I'm not sure if my problem was your problem, I did have trouble installing it the first time I had rooted (I always install busybox right after rooting) and also had wifi calling issues(again, not sure if related). After I re-rooted and did a factory reset I installed busybox again, no issues getting it to install properly that time, wifi calling was also working again. You say you traced your problem to busybox and so I would suggest trying the smart install and see if that works.. If not try a factory reset. I'm pretty sure my issue was on the data rather than system side of things because a factory reset took care of it.
Click to expand...
Click to collapse
!! looks like this solved it for me! ran a TWRP backup just to be sure and then proceeded with an install using the options you've used and WiFi calling is still fully operational! thanks!
dimm0k said:
!! looks like this solved it for me! ran a TWRP backup just to be sure and then proceeded with an install using the options you've used and WiFi calling is still fully operational! thanks!
Click to expand...
Click to collapse
Good to hear!
Related
I installed the new OTA update earlier today and then did the one click mod.
Then installed CWM Recovery using the guide on this site.
Everything went perfectly the first try. I have ROM Manager installed also.
Browsing works fine.
When trying to download an app it errors out in the info bar and says, "Download was unsuccessful." Sometimes AppBrain will say connection error after opening.
Gmail app gives me a connection error, as does Google Talk.
I've tried clearing the data and cache for all these apps including the Download Manager and rebooting. I'm treading in unfamiliar waters and I'm not sure what to try next. I'd love some help please!
Was so excited that everything went flawlessly and now this...
I waited for the OTA update before rooting just so I'd be as legit as possible. I'm not sure if the root caused the problems or if flashing CWM caused the problems, so I've been trying to find a way to go in reverse and get rid of CWM, but I haven't found anything that's made sense yet. From what I gather I'd have to put the stock Recovery back, and I don't know how to do that. All I have is a ROM Manager backup that I performed after the CWM install.
I'm confused and I hope someone can point me in a safe direction.
Fixed itself. Glad I was patient enough not to try something stupid.
See, I was out of cell service while rooting. Once I got into 3g service this morning everything started working. Even turned airplane mode on and everything works via wireless now.
Haven't a clue why, but I'm thankful nonetheless. : )
I have been running GingerMOD v0.5 and wanted to change to Exynos Extreme. When it was done flashing and rebooted I could not connect to wifi and my su binary was wrong and titanium backup could not get root permission. I tried to update it with no luck.
Then I flashed back to gingerMOD and all is well. Then today I tried to flash Androidmeda-HyperDroid-v1.0.0 and ended up with the same problems as last time.
I do understand flashing well and have not had this kind of problem before. Seems to me like it has something to do with gingerMOD as my phone runs as it should on that ROM, but when I flash another the problems apear.
Edit: I also noticed that when I turn my phone off it just restarts itself. I am not rebooting but powering off. Alot of wierd stuff happening on my phone now.
Does anyone know what this could be, and what I can do to fix it?
Edit: Dont know what I did, but it started working again when I woke up
Update the SU binary.
I tried to do that but it just created a .zip file in my root folder and told me to flash it from recovery. When I did it failed.
You'll need CWM to flash that zip.
edit: Try downloading superuser from the market and you should be able to update the su binary using the app upon reboot.
That is what I am doing, but think I got the su problem fixed by flashing the ROM a few more times. Now I am having problems with superuser 3.0.1 FC when I try to remove permissions from an app.
Also the wifi problem is the same. Can connect with my original SGS but not with the SGS II. Im about 4 meters away from my router so signal should not be a problem, and I was connected when I was running gingerMOD.
What happens when I try to connect:
I type in my PW as allways, and then its trying to obtain IP and then it disables and keeps doing the same thing over and over.
Any idea what this could be? As of now I can live with superuser just FC when Im trying to do something in the app. Apps do get root permission so all is well.
But the wifi problem is worse, cant live without wifi on a smartphone
Thx for previous tips.
Are you selecting the right encryption method?
Yes, I am doing everything the same way I did it on the other ROM, but just keeps trying to obtain IP. Do you think this could be related to the ROM I am running now or the one I used before?
As I see it, it looks like the gingerMOD flash changed some settings because I am not having this problem on that ROM, but when I flash another the problem suddenly apears again. But what settings it could be I have no idea.
I just did a "hard reset" but it did not help. Have tried to flash the ROM a few more times as well with no luck.
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha)
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Mankey Magic said:
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha) <-- i think this one no need to do
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Click to expand...
Click to collapse
try check in: settings-- battery & data manager--battery mode ( see what presets u use).
then try check: settings--wireless & network settings--wifi settings--advanced (press menu key(the left touch key in bottom)--wifi sleep policy-- set to never.
btw, wetdream should be already rooted. correct me if im wrong.
hope this help.
benjat said:
hope this help.
Click to expand...
Click to collapse
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Mankey Magic said:
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Click to expand...
Click to collapse
maybe try reboot the phone after change the setting?
im not sure about busybox. what apps u running that require busybox? i want to try install it.
*i just try download root check basic. got message "your device isn't compatible with this item" hehe
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Mankey Magic said:
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Click to expand...
Click to collapse
last try.. remove all wifi network added.. double check all the things i post before.. switch off wifi.. power off ur phone.. 10 sec then switch it on back, then on wifi. if still cant, i dont have anymore idea..
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Mankey Magic said:
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Click to expand...
Click to collapse
nvm.. maybe do full wipe again..
what ver of WD u using? with what addon? im using WD 1.4.3 full
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Mankey Magic said:
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Click to expand...
Click to collapse
i cant tell if its problem with rom or what.. 1.4.3 is 2.3.6 base. and yes webtop work well with it.
here's normaly what i do..
Boot CWM Recovery
Wipe data/factory
wipe cache
wipe dalvik
flash rom
reboot to fastboot and do fastboot-w & then fastboot reboot.
let it boot for 1st time (until stable/full load) i left it around 10 mins
then reboot back to CMW to flash addon. usually i flash 1 then boot.. continues untill flash all.. maybe a bit fussy step.. but i prefer all loaded before flashing another
*i never tried webtop2sd yet.. still dont buy bigger mem card coz funding for lapdock
** maybe can try this one to make it clean wipe.. http://forum.xda-developers.com/showthread.php?t=1421522&highlight=fastboot+-w
Yeah I realized too late that everything cost me way more than I had originally intended to spend. SD cards have come down in price but still pretty pricey for a 32 GB card.
And thank you for the link. I'll try it out tomorrow and report back. It's 1:00 AM here in Seattle!
Hey Mankey,
Have you tested different Wifi networks to ensure that the issue is not with the phone or the ROM at all?
Also, check if someone else on Wet Dream thread had WiFi issues, if this happened with someone else, then they should have fix for sure!
Usually I do what bejnat mentioned and usually works.
Also, about the root, try to follow a root process again. It happened with me before, then I had to install a .zip file through Recovery mode to have root access again.
Hope this helps!
wouldn't just flashing the radio or a newer radio maybe fix his issue??
Yeah it doesn't work with other networks either. And as for root I don't think there's a direct way to root 2.3.6 yet.
Sk8trix, I think I'll try that after I flash back to stock 2.3.4. I've tried just about everything but the radio. Kernels don't fix it.
I'll post an update in a couple days. I really want to get this fixed.
I had the same problem with my dark side when I 1st got it and to fix it I flashed another ROM ,loaded it then flashed back ,cleaned delvik cache and flashed gapps then rebooted and 1st boot fixed my problem was using 2.3.6 with webtop2sd+nebtop app hope this helps you
Sent from my ics+darkside multiboot mb860 using xda premium
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues