[Q] Please Help! S4 Active i537 Wi-Fi problem - Galaxy S 4 Active Q&A, Help & Troubleshooting

Just picked up this phone yesterday. It was a Galaxy S4 Active from AT&T model i537 build number UCUCNH3 running 4.42. I wanted to root it so I scoured the internet and came upon this thread:
http://forum.xda-developers.com/showthread.php?t=2629093
which explained how I needed to flash the NE3 kernel in order to exploit the root and then I could flash NH3 back (although I did not realize this last part until later )
I rooted my phone which was successful. Then I loaded safestrap which was also successful and I attempted to load some roms that I had heard some had limited success with. I did not have success with the ROMs but I also didn't brick my phone so no harm no foul. However, I after doing a factory reset I realized my Wi-Fi is not working. It will work right after a factory reset briefly but then it just kind of disappears and the Wi-Fi screen will perpetually say it is turning on.
I tried turning back the clock by getting rid of safestrap and re-flashing the NH3 kernel and doing many more factory resets (both through recovery mode and from system) but no luck
TLR; Please Help me get my Wi-Fi back!

Let me know if you found a solution.
I have a similar problem. My i537 Wifi configuration is not remembered by NH3 and after a few reboots, it will fail to turn on completely.

Related

[Q] S5 Stuck at Boot Animation With Blue LED After Stock Flash

I searched and found nothing exactly like what I was experiencing and nothing I hadn't already tried. Hopefully someone has seen this before. I HAD a nice rooted stock SM-G900A 4.4.4 and now I have a flashy gold brick (soft). I rooted by downgrading the kernel to use towelroot then flashed stock kernel back. Everything worked fine for about a week or so. I'm not sure at what point I started having issues exactly so I'm not sure if an app or mild mod could have caused my issues. The only thing I had done was use SuperSU to block Knox and change the terrible TW stock sounds to standard ogg clicks and what not. The trouble started with the camera. I opened my camera and the screen would flash green then I would have red ghost images in a pattern on the screen. The pictures I took had the same effect when viewed in the gallery. If I switched modes the problem would go away with the camera until I closed then opened the camera app again so I assumed it was a software rather than hardware problem. I couldn't find any info on a fix so I did a factory reset. The problem persisted. I decided finally to flash back to stock. That's when it really got bad. After flashing to stock the phone will boot to the Samsung animation with the swoosh, freeze there for a few seconds without completing the boot animation then the screen shuts off and the phone becomes unresponsive. The only signs of life is the blue LED is constant lit. I have to do a battery pull to start over. I have flashed just the PDA and I have flashed the whole shootin match (except for BL) and I get the same results. I have tried stock tar files from a couple different sources. It will go into download mode as well as stock recovery where I tried a factory reset after flashing. PLEASE HELP!
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Acer904 said:
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Click to expand...
Click to collapse
Go here and flash back to NCE. Then take the OTAs.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Acer904 said:
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Click to expand...
Click to collapse
If you take the 5.0 ota you won't be able to root. Just FYI. There is no root for it yet. There is a pay however in the general section on how to upgrade to 5.0 and keep root.

[Q] Wifi not turning on after flashing Lollipop Root

So just to summarize what I've done so far, I have a Moto G (2014) which has been updated to Lollipop through normal means. I started off following this guide: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818/page12
The guide then lead me to this one, as my model is XT1064, a Moto G from Windmobile. I had no issues unlocking my bootloader. http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
With the guide above, after I flashed that file, my wifi would not turn on. Every time I pressed the toggle, it would immediately switch back to off. I then flashed the TWRP Recovery, and used that to finally root my device with SuperSU.
I checked my root, and my device is confirmed to be rooted, but the wifi is still not working. I looked around a little, and found this: http://forum.xda-developers.com/moto-g-2014/general/guide-lollipop-xt1064-north-edition-t2955076
The problem with the guide above is that its for a phone that was kitkat, while my phone is already lollipop. The guide does mention the wireless issue though, so I was thinking of trying out the steps outlined in that guide, also using that file (though that file is for 4.4).
Would this work? Or is the safer bet finding an 5.0.1 stock rom, and flashing back to that?
Edit: I found a link to a 5.0.2 stock rom (which is the version my phone currently is) I think downloading that and using that to fix the modem files is the better thing to do. (link: http://www.filefactory.com/file/53c1pepzp9cp/RETCA_XT1064_5.0.2_LXB22.99-24.2_cid14_CFC.xml.zip)
Thanks for all and any help.
I recommend flashing the stock images, that will almost certainly fix your issue with Wifi.

SM-G870A stuck at logo

I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.
We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?
I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.
Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk
If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.
Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.
The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.
Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.
Delete

Uninstalling SuperSU caused S5 Active to brick, Odin flash failing

My last post got no attention, so here is my second attempt.
A software update rolled out for my 5.1 Lollipop S5 Active, and since I wasn't really utilizing my root extensively, I decided I'd get rid of it to receive this update. Unfortunately, I didn't do a whole lot of research and decided I should start by uninstalling my SuperSU. After all, it seemed harmless. I then rebooted, and the thing will not surpass the AT&T boot animation.
The symptoms pointed towards a simple soft brick (i.e. gets to animation, recovery and bootloader not locked). However, I have not been able to successfully flash a fresh firmware onto the device with Odin. SamMobile only has one firmware release for this device, and it is the 4.4.2 version. Is this why the file is failing to flash? If so, how can I get around this issue? Thanks in advance!
sk8chkn said:
My last post got no attention, so here is my second attempt.
A software update rolled out for my 5.1 Lollipop S5 Active, and since I wasn't really utilizing my root extensively, I decided I'd get rid of it to receive this update. Unfortunately, I didn't do a whole lot of research and decided I should start by uninstalling my SuperSU. After all, it seemed harmless. I then rebooted, and the thing will not surpass the AT&T boot animation.
The symptoms pointed towards a simple soft brick (i.e. gets to animation, recovery and bootloader not locked). However, I have not been able to successfully flash a fresh firmware onto the device with Odin. SamMobile only has one firmware release for this device, and it is the 4.4.2 version. Is this why the file is failing to flash? If so, how can I get around this issue? Thanks in advance!
Click to expand...
Click to collapse
Now if I remember correctly (if i am wrong someone please correct me) if your phone was on 5.0+ then you can not downgrade. Same thing with the build number where the old is NF4 i think, and the newest is OF3 with 5.0. my advice is to scour the internet and find the newest flash file. i know there is a 5.0 out there somewhere.

Note 4 problems after marshmallow and tmobile update, am trying to root/problems

My note 4 was bought used, no warranty. When I bought it, it was rooted, but no custom rom, worked great. Once lollipop came out, I wiped and returned to non-root and was able to get the update through tmobile. Didn't bother rerooting as things were ok. Marshmallow udpate came, and I noticed a lot of screen lag. Less than a week ago, tmobile did some sort of update and now, the phone shuts off and restarts on it's own, has very slow screen response (nothing, and then tries to do the same function 10 times in a row, messaging is very slow, types the same words several times over). I did a factory re-set twice. Once, I reloaded all my favorite apps, etc. still bad, so then I did factory reset but did not add anything or bring in my contacts, etc. I am planning on buying the note 7 in a 3-4 months, but in the meantime, would like to continue to use my note 4. I tried doing the rooting method using odin, it appeared to work ok (got the successful notice), triggered the knox thing, but..when I use a root checker, it says phone is not rooted. I am hoping that by rooting and putting a new rom on there I can fix this thing in the interim. So..suggestions on what to do next? Let me know what additional information you need. Could it be the phone itself and not the software? Suggestions on a cheap interim phone? links to relevant threads also appreciated. Is there a better way to wipe everything and start new that I am did not do? I did a factory reset. I have two batteries, which I changed out intermittently to see if it as a bad battery. Android version 6.0.1, security patch level july 1, 2016 Kernel 3.10.40-7804088
Knox version 2.6
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
more info
goosa23 said:
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
Click to expand...
Click to collapse
No to supersu? it's sm N910t, I think what finally worked what odin 3.9 version and flashed the stock that is meant to go with this particular phone to downgrade it down to lollipop. The first few times, I got fail with Odin, but realized that I had marked the option on the phone to keep it from being wiped/flashed if someone found it, once I got that off, I got a successful message. I used the following link and did all of the things mentioned on a link that I am too newbie to be allowed to post, apparently.
but it goes with 3.7 odin, flash the stock firmware from the phone model, and get to the reset button, if successul and then supersu appears.
I got as far as step 8, with odin showing the green 'reset'. But when I went back to the phone, I did not have supersu.
I've tried to do it again, but I get 'fail'
Try out the toolkit that is in the forum. https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
The link takes me to a 404 page not found, is part of it missing?
send me the link by private message so i can see what you are doing?

Categories

Resources