[Q] can't tether on rooted stock? - HTC Rezound

Anyone else having issues with running WiFi tether on Rezound (stock, rooted)? It used to work all the time, then I did a factory data reset, reinstalled (can't remember if it was before or after latest OTA that was installed), and it doesn't work anymore. I have it set to Galaxy S III CDMA/LTE, SSID changed, password set, router fix on...it says:
"Tethering started with errors! Please check 'Show log'."
...then when I turn it off, it says "Unable to start tethering. Is your device 'rooted'?"
Then it says "Your phone is currently in an unknown state - try to reboot!"
Yes, to my knowledge, it's rooted. I rooted before the factory data reset, and it was my understanding that I should be able to do the FDR and not lose root. I tried a battery pull, uninstalling and reinstalling the app, trying it under different settings, and etc. Nothing seems to work. Any ideas?
Thanks
Chris

chrisrach3 said:
Anyone else having issues with running WiFi tether on Rezound (stock, rooted)? It used to work all the time, then I did a factory data reset, reinstalled (can't remember if it was before or after latest OTA that was installed), and it doesn't work anymore. I have it set to Galaxy S III CDMA/LTE, SSID changed, password set, router fix on...it says:
"Tethering started with errors! Please check 'Show log'."
...then when I turn it off, it says "Unable to start tethering. Is your device 'rooted'?"
Then it says "Your phone is currently in an unknown state - try to reboot!"
Yes, to my knowledge, it's rooted. I rooted before the factory data reset, and it was my understanding that I should be able to do the FDR and not lose root. I tried a battery pull, uninstalling and reinstalling the app, trying it under different settings, and etc. Nothing seems to work. Any ideas?
Thanks
Chris
Click to expand...
Click to collapse
When I got it to work you needed the wifi tether app treve mod. I had it set to HTC Rezound.

mamismo said:
When I got it to work you needed the wifi tether app treve mod. I had it set to HTC Rezound.
Click to expand...
Click to collapse
Just found it and downloaded it...no luck. Does it have to do with Verizon's latest OTA? Did they do something to prevent it?

chrisrach3 said:
Just found it and downloaded it...no luck. Does it have to do with Verizon's latest OTA? Did they do something to prevent it?
Click to expand...
Click to collapse
Not sure about it. I am currently running Viperrez. It might be easier to just switch your rom.

Eventually I'll have to do that. Just too chicken now Just strange that I used to be able to do it and now I can't. I wonder if their latest OTA had something to do with it.
Sent from my ADR6425LVW using xda app-developers app

Related

[Q]Wifi issue still present factory reset fixed.

So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App

[Q] mobile hotspot

Hello all,
I have searched the various posts and threads relating to my issue but have not been able to find and answer so here it goes.
I am all of sudden having a tethering issue with my s2. I used to be able to tether my laptops and any other cell phone to my s2 as a wifi hotspot. I am rooted with the stock 2.3.4 rom. uckh7, kernal version 2.6.3.5.7 that has CWM. I have titanium backup pro installed and have always had the tethering mangager app frozen. Now my laptops and other phones will show connected to my s2 network but will not connect to internet even after rebooting ipad and laptops.. I can connect ok using usb tethering. I have tried configuring the hotspot app with and without security, tried various passwords with and without alpha numerical sequences, I have tried FoxFi, and the latest WiFi tether app, and all have same results. I have removed the tether manager completly using TB and still same. I also performed a restore from CWM and still the same. I have not performed a factory reset yet because I believe all that does is remove all user data, not change the system data. I don't want to bring it to an ATT service store because I don't want an exchange unit that will more than likely have the 2.36 rom.
I don't know if I should try to reflash with the stock 2.3.4 or what??
I am at a loss right now.. Sorry for being so wordy, I just didn't want to forget anything if i could.
Any and all thoughts, advise, recommendations appreciated
Thanks
Did you flash the zedomax kernel? It's known to mess up wifi. Flash back to stock.
thanks for the reply,
I flashed codeworkx kernel 5.0.2.3 with cwm. used supeoneclick root to root phone.
wifi has always worked and still is.
?????
mrwhsskers
Maybe try unfreezing what's "always frozen"? Might be worth a try.
Clay
Sent from my SGH-I777 using XDA
I have unfrozen tethering manager, unistalled it thru tb and reinstalled. If I try to use mobile hotspot without tethering manager frozen or uninstalled I get the warning that my account is not provisioned for tethering. If I freeze or uninstall the tethering manager than I can use the mobile hotspot and other devices see my network and connect, but no data is transferred.
Should I just reflash the stock 2.3.4 rom?
I can use tethering ok with my rooted captivate running Cog 5 gingerbread rom ok.
any thoughts??
Full wipe is going to be easier than bug hunting. And yes, a full wipe does clear out ROM settings and files which brings it back to its "default" state. To do a full wipe make sure you:
1.Wipe data/factory reset
2.Wipe Cache
Under Advanced in CWM
3.Wipe Dalvik Cache
4.Wipe /system
You should flash jivy's kernel cleaning script as well before flashing entropy's kernel (mostly just a good practice to have). Hopefully this will clear up your issue.
Sent from my SGH-I777 using xda premium
Thanks,
will try this evening and report back on results.
quick question regarding wiping and clearing cache, etc.
will I loose root after cleaning??
mrwhsskers said:
quick question regarding wiping and clearing cache, etc.
will I loose root after cleaning??
Click to expand...
Click to collapse
No, as long as the rom you're already on is rooted it will stay. Again this just resets THE ROM to default essentially. The personal data on your internal SD will be for the most part untouched, just the app data will be gone, and a essentially fresh rom install.
Edit note:5 mins is a rediculous waiting period TO EDIT A POST.
Sent from my SGH-I777 using xda premium
thanks for that.
sorry for the delay in reposting question, posting between clients at work.
appreciat the help
ok. wiped everything cleaned kernel, installed entropy's kernel.
still the same.
I did notice something peculiar this afternoon. tried using the hotspot app at work where signal is poor. co-workers phone was able to connect to my hotspot and get on internet until i noticed my signal jumped to Hspa+ then he lost internet?? any relevance to that??
I wiped, did reset, cleaned existing kernel, installed entropy's kernel. Tried again but still no devices could get data signal thru my hotspot although the connected to my network. I was playing with a coworkers phone later and his phone was able to connect and receive data. I noted at that time that my phone was only on 3g data not 4g. As soon as I moved the position of my phone to where it received a 4g signal then my coworkers phone would no longer receive data thru my network??? any significance to that????
thanks in advance for all your time.
:thanks for all the responses. Finally solved. On a whim I went into mobile network settings, went into APNs and hit "reset to default" and retried the mobile hotspot again and now everything works, all my devices now receive data and can connect to internet again.
thanks again to all.
mrwhsskers
You're welcome from all of us.
Clay
Sent from my SGH-I777 using XDA

Stuck on boot screen and have tried many, many times...

The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.

WIFI keeps getting on and off

Hi,
I've updated the phone to the newer firmware from KIES, and the phone was connected to the WIFI network but signal connection keeps switching on and off, is there anyway to fix this issue so I can have a stable connection?
Have test with my iPhone and Ipad, both connectect to the same WIFI and only my samsung S3 having this problem.
PS: WIFI power saver mode is already <<off >>, keep Wifi on during Sleep mode is set to <<always>>, Network notification is <<un-tick>>
This is my current ROM (Rooted)
AP: I9300BUBLG3
CP: I9300BULG2
CSC: I9300VFGBLG3
settting > wireless & network > more > mobile network > automatic connections > sprint connection optimizer.. unchecked?
This is the international version is Samsung S3, I can't find such settings.
Sent from my GT-I9300 using xda app-developers app
I had the same issue when I reverted to stock. I thought it was this and that but really, all I did was
Backed up everything
Well mine was rooted and stuff so I triangled away the flash counter, probally dont need that if your on stock anyways
I wiped everything from the phones settings, back and restore, reset
I then booted up in recovery, doesnt matter if you are cwm or stock recovery, wipe again plus cache
Now I loaded up Odin and flash the original stock rom for my phone, I waited till it was complete, I then updated it through settings till I got to the latest update and then started reinstalling my apps from google play store or whenever else I had apps. So far all is well and no wifi issues.
Other advise would be instead of all the above, wait for another update or flash a new modem. That also worked for me when I was running another countries stock rom, Bad wifi, so I flashed my countries modem and it was fine! so good luck!
go to dialler
*#0011# will take you into Service Mode
click on menu
click on wifi
you will see a button that says "on" click on it
it will say off this stops the wifif connect/dis-connect problem.
If you shut down your phone you have to reset it to off.
jetbruceli said:
I had the same issue when I reverted to stock. I thought it was this and that but really, all I did was
Backed up everything
Well mine was rooted and stuff so I triangled away the flash counter, probally dont need that if your on stock anyways
I wiped everything from the phones settings, back and restore, reset
I then booted up in recovery, doesnt matter if you are cwm or stock recovery, wipe again plus cache
Now I loaded up Odin and flash the original stock rom for my phone, I waited till it was complete, I then updated it through settings till I got to the latest update and then started reinstalling my apps from google play store or whenever else I had apps. So far all is well and no wifi issues.
Other advise would be instead of all the above, wait for another update or flash a new modem. That also worked for me when I was running another countries stock rom, Bad wifi, so I flashed my countries modem and it was fine! so good luck!
Click to expand...
Click to collapse
This was the latest stock rom from KIES update (also rooted). But thanks for the reply, I'll try to flash different ROM and see what will happen.
colint3 said:
go to dialler
*#0011# will take you into Service Mode
click on menu
click on wifi
you will see a button that says "on" click on it
it will say off this stops the wifif connect/dis-connect problem.
If you shut down your phone you have to reset it to off.
Click to expand...
Click to collapse
I already set it <<off>>, still having issue with the wifi.
superfilm968 said:
I already set it <<off>>, still having issue with the wifi.
Click to expand...
Click to collapse
I've got the exact same problem. Do you have a BT Home Hub 3 by any chance?
I've just rooted mine so am going to try and flash a new modem and see if this fixes the issue
jonjuk said:
I've got the exact same problem. Do you have a BT Home Hub 3 by any chance?
I've just rooted mine so am going to try and flash a new modem and see if this fixes the issue
Click to expand...
Click to collapse
Sorry I don't have BT Home HUB 3, my connection is very simple, just connecting the S3 to a DrayTek Vigor2710Vn Router via Wifi. Please let me know the result after you flash with a new modem. If is working, please provide the link and file name where you got your file so I can flash it too.
Thanks!!!!
***By the way, what ROM version are you using at the moment? Please provide your AP, CP and CSC details if is different to my S3. ***
Repeat Modem has nothing to do with WiFi.
jje
I had the exact same issue, but ONLY after rooting the device (which I did just a day or two after I got it). I tried every possible fix, flashed new roms 3 or 4 times, wiped data and everything else in recovery, but no luck.
However, my final solution was to simply follow a guide to unroot the device, which I did today - and it did indeed work, I guess this issue is mainly happening to rooted phones, for unknown reason. Until I know this is fixed with an update (maybe in 4.1 JB), I won't be rooting this device again.
Link to guide on how to unroot
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
haenraets said:
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
Click to expand...
Click to collapse
did you reset the flash counter?
haenraets said:
Are there actually people who can't fix it like me?
Also done everything I possible could but never got wifi working again.
Returned it to Samsung. I unrooted it and flashed the firmware again with KIES.
The day after there was also an official update for the BENELUX I guess. Also updated this with KIES.
So is it still possible they see that the modem was changed?
Click to expand...
Click to collapse
Yeah as the guy above me said, you always have to reset the flash counter before unrooting (as this requires superuser access).
If you don't do this, it's easy to see the phone has been modified in either download mode or by checking status in settings.
After successfully unrooting you'll also have to re-enter CWM recovery and wipe data+cache.
After doing this you'll see the device being "normal" and it should show "stock" in download mode.
ph10m said:
Yeah as the guy above me said, you always have to reset the flash counter before unrooting (as this requires superuser access).
If you don't do this, it's easy to see the phone has been modified in either download mode or by checking status in settings.
After successfully unrooting you'll also have to re-enter CWM recovery and wipe data+cache.
After doing this you'll see the device being "normal" and it should show "stock" in download mode.
Click to expand...
Click to collapse
Forgot to mention it but I did this yes.
I also think KIES would not update when this is not a zero.

busybox and WiFi calling on MM

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!

Categories

Resources