Ok guys. I browsed through the forums for this but can only find my issue on custom Roms. My issue is with my wife's phone on the Stock Rom. I rooted her phone the other night and since then her phone has no wifi signal til a reboot then her wifi comes back in nice and strong.
Is this a known root issue? Her phone is on 4.0.1, which I believe is the latest firmware for this phone to date. The only thing I did after rooting was, of course, install apps necessary for root and flashed a security program. Nothing else.
Related
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
A few days ago, the wifi connection to my Verizon Note II stopped working. I see a strong signal from my router, and it attempts to connect, but inevitably gets "Authentication Error". It did the same thing with other networks, so it's not just my home wireless.
This is a well-known problem with 4.1.2 - and has been for a while. Google it. I did, and quickly went down a rabbit hole, leaving me frustrated, confused and still no closer to a fix. So I installed a 4.3 ROM, which also required an updated firmware.
I was using Jelly Beans 22 (http://forum.xda-developers.com/showthread.php?t=2032447)
I wiped everything and installed JellyWiz 4.3 (http://forum.xda-developers.com/showthread.php?t=2564495) with TWRP and VRUEMJ9 WIfI Firmware via Odin.
And still the error persists.
F** it. I'll jump to KitKat.
So I wiped everything again, updated TWRP, and installed Gummy (http://forum.xda-developers.com/showthread.php?t=2592339)
STILL NO WORKING WIFI. Same "Authentication" error
In between the above steps, I have tried literally everything I could find to fix this problem. Restarting my router (duh), changing settings in the wifi menu, the hidden "service mode" menu, energy saving, even dropping the /etc/wifi directory and replacing with a copy from 4.1.1.
What silly, stupid, inane detail did I miss?
SCH-I605
Android Version 4.4.2
Baseband I605VRUEMJ9
Kernel 3.0.64-gummy...
Have you updated to the mj9 firmware?
Fine. I'm done dealing with this, I thought, and nuked the phone back to the stone age.
Using Odin and instructions here: http://forum.xda-developers.com/showthread.php?t=2024207 I flashed back to 4.1.1 and a full factory reset.
Still. No. F***g. Wifi.
I have now spent the entire weekend upgrading and downgrading my Note II, to no effect. I'm almost *almost* convinced it's a hardware problem. If it didn't match so many other examples of a 4.1.2 wifi bug, to a T.
Anyhow, to the Verizon store I shall venture on the morrow, and demand satisfaction.
Kil4Thril said:
Have you updated to the mj9 firmware?
Click to expand...
Click to collapse
Yep. As part of flashing to 4.3 and Jelly Wiz.
No dice.
Did you use Odin or the flashable zip? ONLY the Odin method works. I tried using the zip, and while my phone said it was on mj9, it didn't update anything but the modem. This left me unable to use my WiFi on anything over 4.1. I hope this can be of some help
Alright guys, this is gonna be kinda long so get ready. I was running stock 4.4.2 NEW and I saw that there was a way to get GPE 4.4.3 and 4.4.4 rom working on the s4. I followed all the instructions on RickGrimes's post and wifi didn't work. Not and big deal. I couldn't soft reboot, so I tried flashing gogolies nc2 wifi fix and this modem worked. I then tried to update to 4.4.4, also following the instructions and the wifi didn't work once again. I flashed gogolies nc2 wifi fix again but it did not work. I also realized that I had no service at all and that I couldn't send or receive any messages or calls. So I did the safe thing and used Odin to get back to stock. I am currently running stock but the service is still terrible in places where I usually get great signal. Also, my wifi strength seemed to go down from what it usually is. Another issue is that my contacts that were backed up in backup assistant aren't there anymore at all. I generally know what I'm doing when it comes to this stuff but for some reason I have no idea how to resolve these issues. Any help will be appreciated.
Reolved
Jessooca said:
The easiest way to fix your phone or any phone for this matter is always to download and flash the stock tar file of whatever version of Android you were last on in Odin.
Then visit towelroot.com in your browser on your phone and root it again. (Don't forget to enable usb debugging first)
Click to expand...
Click to collapse
I wound up going back to stock 4.4.2 via Odin, but the problem still persisted. I figured out the my network settings were changed to Global instead of CDMa/LTE. Changed it back and all is well! Thank you though!
Device: Galaxy S3
ROM: Slimkat
ROM version: Slim-4.4.4.build.6-OFFICIAL-5242
Build: slim_d2lte-userdebug 4.4.4 KTU84P 5242 test-keys
Kernel: 3.4.95-cyanogenmod-gd56ed95
I purchased my S3 in April of last year (4.1 Jellybean), and at the time the wifi worked perfectly. After the first (or second?) OTA that was pushed to my device, my wifi started acting up. It would cut out and I would have to cycle the wifi off and back on in hopes it would work again. I have been patient hoping they would push an OTA that would finally fix it. A year or so and a few OTA (I don't recall how many, or which versions) later and it still doesn't work properly, so I decided to finally try a custom rom to see if it would solve the issue. The last stock version of android I was using was the 4.4.2 OTA.
I rooted my device using towelroot, flashed CWM Recovery (CWM_6.0.4.7_Non-Touch_GT-I9300) using ODIN 3.04, then proceeded to flash the Slimkat rom listed above using CWM recovery. The wifi seems to be better, but it still cuts out and is unresponsive even though it says I have full wifi signal. A wifi cycle seems to fix it temporarily, but I'd like to solve this issue.
So as far as I can tell the last working modem I had was stock 4.1 or so. So I guess my question is, can I flash previous modems to try to get a working one with this rom? I have tried using WIFI Fixer from play store, and even with full signal on WIFI I get signal poor, signal hop scan messages spammed. Any and all help would be greatly appreciated!
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1