I have a I537 with the latest ML2 kernel. I have been lurking for a while enjoying other peoples work, But I couldn't find the right modules to get my wifi working on any rom that I flash in safestrap. I finally decided to pull the ML2 modules myself and try them. IT WORKED !! So i thought I would share with anyone else having problems getting roms to work on the latest kernel. I hope the helps. I can confirm that they work on my phone I537 with ML2 baseband with Wicked romv10 flashed with safestrap 3.71. Will try other roms as well.
Thanks
RB8720
Related
Hi. I have an AT&T Galaxy S4 Active which was (supposedly) factory unlocked. It does accept another SIM so I know it was at least partially unlocked. I have also rooted the phone thanks to your help here. (Big thanks for that!!!) But I would like to be able to use the phone as a hotspot and can't seem to get it to perform. I get an error message that there is a network error please try again later. It occurred to me that this might be due to the AT&T APN still being listed as "default", although I have entered my carrier's APN info.
Is there a way to remove the AT&T APN? Or, alternatively, does anyone have another trick I might use? Any and all assistance would be greatly appreciated!
Is your phone sgh-i537 ?
We have several of those and all are unlocked. They arrived (large shipment) from vendor, all rooted with a locked down android 4.3 (ML2) and mobile hotspot would not work......system update would not work....
Here's what I finally did:
1. Installed Odin 3.09
2. Downloaded full image (1.2 GB) for ATT ML2 (Android 4.3)
3. Reflashed over *existing* ML2 the official ML2 which killed root and any other customizations (desired!)
4. At this point, connected to ATT System Update, it found automatically the 444 MB update to Android 4.4.2
5. Rooted with towelroot.com
6. Hotspot works now fine on all of them.
Mine is an i537 and I`m in almost the same boat. I can not enable a wifi hotspot. My phone was originally branded AT&T but I am running it on Wind which uses AWS frequency like TMobile. My phone is rooted with towel and the radio file has been modified for AWS.
Can I do what xdafly said but still modify the radio file for AWS? How about the 444mb update from AT&T? Can I update that way even tho I'm using a sim from another provider? Is there a file I can download with the same update in it?
Unable to comment on the radio file but perhaps someone else has more details on that and will post.
However, as to your question on the 444 MB update, I also tried on a few of our i537 the download links found in the ATT Stock Firmware thread
As you will discover there, if you have an unmodified ML2 (Android 4.2) or WISH TO make it so, you can install Odin (links are there) and you can download the ML2 image (links are there) and THEN you can download the 444 MB file, place it on a microSD card, drop into Stock Recovery and select the (renamed) update.zip and your ML2 will now be NE3 (Android 4.4.2).
At this point you have the official ATT i537 firmware and you can root with towelroot.com and make any other desired changes.
xdafly said:
Unable to comment on the radio file but perhaps someone else has more details on that and will post.
However, as to your question on the 444 MB update, I also tried on a few of our i537 the download links found in the ATT Stock Firmware thread
As you will discover there, if you have an unmodified ML2 (Android 4.2) or WISH TO make it so, you can install Odin (links are there) and you can download the ML2 image (links are there) and THEN you can download the 444 MB file, place it on a microSD card, drop into Stock Recovery and select the (renamed) update.zip and your ML2 will now be NE3 (Android 4.4.2).
At this point you have the official ATT i537 firmware and you can root with towelroot.com and make any other desired changes.
Click to expand...
Click to collapse
I537UCUBML2 (4.3) Released 2014-01-07 is the right ML2 to use? It is the 1.2GB Oden file. Sorry for such a simple question. I'm pretty new to this and don't want to use the wrong file and brick my phone.
HalfinchWrench said:
I537UCUBML2 (4.3) Released 2014-01-07 is the right ML2 to use? ...
Click to expand...
Click to collapse
Yes, that is the one for i537. The 1.2 gb download will contain 4 parts and you will need to find Odin (easy to find as there are many filehosts). Read the discussion threads to alleviate any concerns but it is simply a matter of opening the archive somewhere on your system, installing Odin and then just inside Odin open and point each of the 4 parts, reboot your phone to Downloading....mode (Vol Down, Power, Home) and connecting USB cable....
Thanks xdafly! I'm gonna download a couple of big files and do some reading till my eyes bleed!
I have an i537 running 4.4.2 (NE3) with the MF1 baseband (to be useable on AWS) and I still have the same issues with WiFi tethering (hotspot) that I had on ML2.
@xdafly your suggestion of 4.4.2, was that to help hotspot run while using non-ATT SIM cards? If so, am I missing a step? (I am currently not rooted, how does that help in this case?)
Hi, Well like my title says, My phone won't connect to my computer.. I tried everything ..ithink..
A list of things I Tried
-Changed the chords
-Changed from MTP to PTP and back to MTP
-Installed kies & kies 3
-Installed Samsung USB Drivers
-Unistalled these things, installed USB drivers only , installes KIES only
-Debug on
-Deleted UpperFilter in Regedit
Tried everything I could still nothing what works (After deleting UpperFilter it working but after taking it off the chord it again stopped working)
Please helpme
had same problem on a boxload of ATT i537 with Android 4.3 ML2 installed. they had been heavily modded and rooted.
kies3 would not work.
solved it by reimaging ML2 over ML2 using Odin 3.09 and updated to android 4.4 NE3
now kies3 works
xdafly said:
had same problem on a boxload of ATT i537 with Android 4.3 ML2 installed. they had been heavily modded and rooted.
kies3 would not work.
solved it by reimaging ML2 over ML2 using Odin 3.09 and updated to android 4.4 NE3
now kies3 works
Click to expand...
Click to collapse
i'm sorry but uh, Can you give me more information about those ML2 things, I don't understand anything thanks for your help
btw I have version 4.4.2 And I Can't even open it up in Odin when my phone is in Download mode
Read the ATT Stock Firmware thread
I followed the ATT ML2 image update steps to NE3 (I537UCUCNE3) and also used the manual microSD method in addition to allowing ATT Software Update automatically handle some phones from 4.3 to 4.4.2 (that is the 444 MB update)
xdafly said:
had same problem on a boxload of ATT i537 with Android 4.3 ML2 installed. they had been heavily modded and rooted.
kies3 would not work.
solved it by reimaging ML2 over ML2 using Odin 3.09 and updated to android 4.4 NE3
now kies3 works
Click to expand...
Click to collapse
have you tried to connect to another usb port or another computer?
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.
This is a Verizon Samsung Note 3 SM-N900V.
I recently installed Lolipop with Odin to ipgrade.Jasmine ROM 3.5
Safestrap we working until I upgraded to Lolipop. Root is intact, but SS just aren't there. I can't get SS to would at all, it says it is installed in the app, but it doesn't come up on reboot anymore.
Is there any way to get my SS working again? The phone is fine and still rooted, but SS adds a layer of data integrity that we can all deal with more of.
This this no matter
Thanks!!
Gundie said:
This is a Verizon Samsung Note 3 SM-N900V.
I recently installed Lolipop with Odin to ipgrade.Jasmine ROM 3.5
Safestrap we working until I upgraded to Lolipop. Root is intact, but SS just aren't there. I can't get SS to would at all, it says it is installed in the app, but it doesn't come up on reboot anymore.
Is there any way to get my SS working again? The phone is fine and still rooted, but SS adds a layer of data integrity that we can all deal with more of.
This this no matter
Thanks!!
Click to expand...
Click to collapse
I just wanted to add some info that might help:
The phone is a SM-N900V
Kernel version 3.4.0
JasmineROM-V5.1.1-lrx21v.n900vvrue0b6
Se enforcement enabled
Running Knox 2.3
Is there any way that I can put Safestrap back on?
Thanks in advance.
Yes, you need to install NC2 flasher...but before you do this, find the kernel for Lollipop and put it on your phone. That way you can flash it from safestrap so when you reboot it will work correctly. Switching back and forth between kernels is the only way! If you don't have the kernel on your phone, you need to put the phone in download mode and ODIN the kernel over.
Ok so first let me apologize if I overlooked a similar post but I've been having root issues for weeks now and haven't found my exact situation yet.
Here's the background. I have an AT&T Note 3 N900A. When I got the phone I had no issue using towel root to root the device. Worked first try. I'm new to rooting and I was in love with all the new options. I started small playing with xposed and fonts overclocking etc. Then started researching custom Roms. Discovered cwm twrp wouldn't work with my locked boot loader so researched and got safestrap. Did the backup made my new Rom slot and with a guide I attempted my 1st custom Rom flash. FAIL. bootloop. Revert to stock Rom via Odin. Download towel root. Rooted. No problem.
2nd attempt at custom Rom flash with safe strap. fail. Download another stock firmware (at this point I was still dumb to the difference between NL1 NC2 OC2 etc). And in still dumb to oxed and deoxed. But apparently I got out of bootloop with a different firmware version this time around. First I decided to run lollipop 5.0. Towel root said device not suported. Now I'm running 4.4.4 NL1. device not supported. Also can't get kingoroot king root(pc or non pc) cf or anything else I've tried to work. From what I've read I need to go back to the NC2 4.4.2 and run towel root from there.
My current issue is I have no windows pc to run Odin on and my wife's MacBook refuses to install the Mac version correctly nor will it load the Web based version on the casual page.
I just figured out that I can't use safe strap to flasthe nc2 until I'm rooted. And without Odin to revert I'm scared to try any other method without some guidance.
First off... Is there any way to root my current 4.4.4 without going to the nc2 or if I allow my phone to upgrade to 5.o again is there a non pc root method on lollipop yet?
Or would I be able to download a nc2. Zip to my phone save to sd and use the note 3 stock recovery to revert? ?
I'm open to any suggestions you guys may have even if I haven't mentioned it in my post. Hope to get some answers asap and thanks in advance!!
I'm not familiar with the Note 3 for AT&T but Heimdall (in place of Odin on a PC) may work on your mac to flash ROMs.
http://glassechidna.com.au/heimdall/
Yeah I tried that a while back but it was b4 I knew this much. Maybe j can get it working now. I was just hoping there was an easier way.