Database Users

[Q] Need help, rooted S4, wifi not working anymore

So I rooted my sprint s4, following these instructions:
http://qbking77.com/development/how-to-root-the-sprint-and-international-exynos-samsung-galaxy-s4/
Which worked great. Then, I followed these instructions for the hotspot modification:
http://qbking77.com/development/how-to-get-free-native-wifi-hotspot-on-the-sprint-samsung-galaxy-s4/
I was running the MF9 firmware, so I used that. I made a backup of the two files before copying the new ones over. I reset it, and it stopped on the sprint screen, so I followed the unrooting instructions here:
http://qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4/
Now, my wifi isn't turning on. It flashes for a second, then disappears, showing a "The device has detected an application attempting unpermitted actions and has stopped loading. To protect your device, it is recommended you reboot." alert.
The backups I made weren't there, so I assume it rebuilds those files. What do I do? I've tried factory resetting, but nothing has helped so far. I've read a few forum postings but they seem to all revolve around issues with new roms. I only used the stock one, so I'm not sure exactly what to do.
So, can anyone help me out? I'm not too far into these things, so easier instructions are better.

That alert is because you have Knox installed and rooted. You need a root browser and go into the system/app folder and delete the two files that begin with the name Knox.
Sent from my SPH-L720 using Tapatalk 4

daniel4653 said:
That alert is because you have Knox installed and rooted. You need a root browser and go into the system/app folder and delete the two files that begin with the name Knox.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
I just did that, and the message is gone, but it still won't let me turn on wifi.

miron721 said:
I just did that, and the message is gone, but it still won't let me turn on wifi.
Click to expand...
Click to collapse
Flash diff kernel, this issue has been solved many times
Sent from my SPH-L720 using xda app-developers app

ROMANTiC KiD said:
Flash diff kernel, this issue has been solved many times
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
So to do that, I'd use the odin program? And where do I get the different kernel?

To be honest you shouldn't be flashing if you don't fully read and learn before getting a rooted phone. Kernels are in the original development thread.
And you flash the kernel zips in a custom recovery.
Sent from my SPH-L720 using Tapatalk 4

daniel4653 said:
To be honest you shouldn't be flashing if you don't fully read and learn before getting a rooted phone. Kernels are in the original development thread.
And you flash the kernel zips in a custom recovery.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
I had no intention of flashing a new rom, only wanting to root it to remove some useless stock software, and move some other stuff to the SD card.
I'm guessing I want the first file here, right? http://forum.xda-developers.com/showthread.php?t=2258107
I'm running MF9, so I want that to match up, right?

Yes that's the right file for u if u are on the software version mf9 like u mentioned. Good luck!
Sent from my SPH-L720 using xda app-developers app

Chevyblood561 said:
Yes that's the right file for u if u are on the software version mf9 like u mentioned. Good luck!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
So I put the new kernel on, and no change. Wifi still won't turn on.
What now? I've seen a bunch of people with this problem on the GSM one, but no real answers. No resolved ones on the CDMA version

miron721 said:
So I put the new kernel on, and no change. Wifi still won't turn on.
What now? I've seen a bunch of people with this problem on the GSM one, but no real answers. No resolved ones on the CDMA version
Click to expand...
Click to collapse
Try kt kernel
Sent from my SPH-L720 using xda app-developers app

gotablunt said:
Try kt kernel
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I can't find any instructions on how to install that kernel, since it's a zip instead of a tar so I can't use odin. Everyone just says "use recovery," which doesn't help me at all, since I don't know what that is or how to do it. I've tried a few other kernels I've found on xda, but none have fixed it.

Flash custom recovery tar thru odin, theres a couple threads in development section with different recoveries...then simple flash kt kernel zip thru your new recovery ( you can access your new recovery by booting up the phone and holding down the volume down button)...I suggest you learn how to back up and restore your rom b4 trying this
Odin this recovery http://d-h.st/O8s its agats
Here you can download kt touchwiz kernel http://forum.xda-developers.com/showthread.php?t=2288309 make sure to thank him..good luck
Sent from my SPH-L720 using xda app-developers app

Installed the recovery, as well as the kt touchwiz kernel, and no change. Still no wifi.

miron721 said:
Installed the recovery, as well as the kt touchwiz kernel, and no change. Still no wifi.
Click to expand...
Click to collapse
Tell us what does it say in your settings about phone
Sent from my SPH-L720 using xda app-developers app

Software version: L720VPUAMDC
Hardware version: L720.08
Android 4.2.2
Baseband version: L720VPUAMDC
Kernel version:
3.4.6.2--KT-SGS4-JB4.2-TW-SPR-09.17.2013---ga0a3e11
[email protected] #1
Tue Sep 17 19:06:25 MST 2013
Build Number: JDQ39.L720VPUAMDP
SELinux status: permissive

miron721 said:
Software version: L720VPUAMDC
Hardware version: L720.08
Android 4.2.2
Baseband version: L720VPUAMDC
Kernel version:
3.4.6.2--KT-SGS4-JB4.2-TW-SPR-09.17.2013---ga0a3e11
[email protected] #1
Tue Sep 17 19:06:25 MST 2013
Build Number: JDQ39.L720VPUAMDP
SELinux status: permissive
Click to expand...
Click to collapse
Hmm weird, well here update to the newer update to this for here. Will be a pain in the ass but believe me this will solve all your problems.
http://forum.xda-developers.com/showthread.php?t=2375523
Flash that in Odin and make sure you just get the huge file that's the only one you need. Extract what is inside and you will get a .tar.md5 file. Next do a factory reset of your phone. Boot into download mode. Flash that file. If you get any errors just delete the .md5 extension and reboot your computer and try again. Once done, it should boot will take awhile no more than 10 mins. If it doesn't boot take off battery and boot into recovery. You should stock recovery with the little green dead android. Its OK don't freak out just do a factory reset and reboot. Once that is done.
Download either odex or deoxeded tar file which ever you want here
http://forum.xda-developers.com/showthread.php?t=2357471
Once that is done you can flash that through Odin and you should be rooted and updated to the latest version.
You can also download twrp recovery here
http://techerrata.com/browse/twrp2/jfltespr
All versions there. You can download stabled twrp 2.5.0.2 or download the newer one 2.6 0.3 as people have said it has been working for them and there you go. Its a lot but it gets the job done and all your problems go away.

ROMANTiC KiD said:
Hmm weird, well here update to the newer update to this for here. Will be a pain in the ass but believe me this will solve all your problems.
http://forum.xda-developers.com/showthread.php?t=2375523
Flash that in Odin and make sure you just get the huge file that's the only one you need. Extract what is inside and you will get a .tar.md5 file. Next do a factory reset of your phone. Boot into download mode. Flash that file. If you get any errors just delete the .md5 extension and reboot your computer and try again. Once done, it should boot will take awhile no more than 10 mins. If it doesn't boot take off battery and boot into recovery. You should stock recovery with the little green dead android. Its OK don't freak out just do a factory reset and reboot. Once that is done.
Download either odex or deoxeded tar file which ever you want here
http://forum.xda-developers.com/showthread.php?t=2357471
Once that is done you can flash that through Odin and you should be rooted and updated to the latest version.
You can also download twrp recovery here
http://techerrata.com/browse/twrp2/jfltespr
All versions there. You can download stabled twrp 2.5.0.2 or download the newer one 2.6 0.3 as people have said it has been working for them and there you go. Its a lot but it gets the job done and all your problems go away.
Click to expand...
Click to collapse
I followed all the steps, and wifi still won't turn on. Frustrating.

miron721 said:
I followed all the steps, and wifi still won't turn on. Frustrating.
Click to expand...
Click to collapse
Then it is probably the phone. Take it to sprint for them to check it out? Make sure your back to stock tho
Sent from my SPH-L720 using xda app-developers app

miron721 said:
I followed all the steps, and wifi still won't turn on. Frustrating.
Click to expand...
Click to collapse
Just to clarify, do you by any chance mean wifi hotspot?
Sent from my SPH-L720 using xda app-developers app

gotablunt said:
Just to clarify, do you by any chance mean wifi hotspot?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
No, I mean wifi at all. Also, I just noticed when I insert a microsd, it says it's safe to remove immediately. Loading from the SD card on recovery works though.
And I doubt sprint will help me, I've had the phone for a while and they wouldn't do anything for issues with my last phone, since it was the 15th day I had it. If I send it to samsung with the stock recovery, kernel and rom, will they be able to tell?

[Q] Unable to boot Stock based ROMS [D800]

Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA

vish9 said:
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
Click to expand...
Click to collapse
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?

sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also

joebob296 said:
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
Click to expand...
Click to collapse
Exactly, AOSP ROMs are booting up fine but not the Stock based ones.. I am not flashing any kernels, just the ROM, so I'm assuming it will run on either the stock kernel or the kernel included in the ROM zip?
Have you been successful in installing such ROMs? Am I missing something in the wiping part? Only been doing the factory reset in TWRP before installing any ROM.

Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk

rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Oh, I hadn't thought about anything being wrong with the recovery.. Always assumed it gets the work done
How do I find previous versions of TWRP compatible with D800?

joebob296 said:
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yes I am on 10o.. Does it have issues with installing other Stock ROMs? If yes, I'll try to follow the thread on using LGFlash tools, I've never done that before. Hopefully its not much difficult to follow the instructions.

That is one of the easiest guides to follow. Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk

joebob296 said:
That is one of the easiest guides to follow. Me sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Thanks.. I'll try to do it tonight and post my results here.

joebob296 said:
Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I'm stuck in the process! Can't change the com port number to 41. The guide is pretty easy to understand. But when I put my phone is download mode and try to change the com port number, it says I don't have the write privileges for this device's setting. I've tried it on both Win 7 and Win 8 laptops, with LG mobility drivers installed.
Is there something in the phone settings I need to enable so that I get the write privileges to change com port number?

Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk

SOLVED!
joebob296 said:
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yay!!! Finally did it!
Issue 1: If faced with write privileges for com port (tried successfully in Win 8)
Solution: After going in to com port properties, click "change settings" and there is the option to change com port number.
Issue 2: Once the port number was changed to 41, rest of the instructions are easy to follow on this thread http://forum.xda-developers.com/showthread.php?t=2633150
Once on D80010d, I rooted with ioroot22, and installed recovery using FreeGee. Just installed Rayglobe 3.2 minutes ago, and it finally booted up!!!
So, the bottomline is that go back to D80010d if you wanna play with Stock based ROMs! I flashed with TWRP 2.6.3.3, so the fault is not with the recovery. That much I can confirm
Thanks for the suggestions guys. Thread solved I guess.

Great. Glad to hear it.
Sent from my LG-D801 using Tapatalk

rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Thanks for the input. Before I flashed back to D80010d today, I installed older versions of Philz and TWRP but neither helped. So downgrading was sort of a compulsion, in my case at least.

and the moral of the story is, unless you are getting an android version upgrade in the update, do not take the update.

Help Needed - Downgrading 4.4.2 to 4.2.2, and Rooting after downgrade - AT&T S4

Hi all!
I am a noob in need of some help with downgrading my phone, back to 4.2.2 (Jellybean).
My current situation is as follows:
I initally got the S4 from AT&T with the stock 4.2.2 rom (with the Build # ending in MF3, and the Baseband version of i337). Soon after sometime I had rooted that version on my phone and everything was alright.
After a couple of months 4.4.2 was released and AT&T started pushing it out/releasing it for download. So I went ahead with the download without doing a proper backup of the then current rom (4.2.2) (a really dumb idea on my part! ) - so I don't have a snapshot of the 4.2.2 rom.
Anyways, after the update I current have the S4 with (Kitkat 4.4.2 - Build # NB1 and the baseband is still the same - i337). I know there are some threads out there somewhat outlining what needs to be done and so forth, with people tested it out as well. But I am having a hard time following the instructions, also I haven't found one that has a clear instruction set for downgrading 4.4.2 to 4.2.2.
The reason I need this soon is because my phone has started glitching big time now (seems like it may not be able to handle the switch) - it has started overheating with basic functionalities such as calling/text/charging, and having random 'black screens', and all this began happening only after the upgrade.
What I'm looking for (if possible):-
A non-rooted method of backing up application data from the phone before the downgrade
A way to downgrade 4.4.2 to 4.2.2 (I should be able to figure out how to root it once its back to jellybean)
A way to retain emoji's
Any help will be appreciated regarding this! Please try not to be too harsh, I'm trying hard to learn properly and not screw up with the process.
Thanks!

There is no way to downgrade to 4.2.2. Don't even waste your time.
Sent from my Nexus 5 using XDA Free mobile app

zdarkangel said:
Hi all!
I am a noob in need of some help with downgrading my phone, back to 4.2.2 (Jellybean).
My current situation is as follows:
I initally got the S4 from AT&T with the stock 4.2.2 rom (with the Build # ending in MF3, and the Baseband version of i337). Soon after sometime I had rooted that version on my phone and everything was alright.
After a couple of months 4.4.2 was released and AT&T started pushing it out/releasing it for download. So I went ahead with the download without doing a proper backup of the then current rom (4.2.2) (a really dumb idea on my part! ) - so I don't have a snapshot of the 4.2.2 rom.
Anyways, after the update I current have the S4 with (Kitkat 4.4.2 - Build # NB1 and the baseband is still the same - i337). I know there are some threads out there somewhat outlining what needs to be done and so forth, with people tested it out as well. But I am having a hard time following the instructions, also I haven't found one that has a clear instruction set for downgrading 4.4.2 to 4.2.2.
The reason I need this soon is because my phone has started glitching big time now (seems like it may not be able to handle the switch) - it has started overheating with basic functionalities such as calling/text/charging, and having random 'black screens', and all this began happening only after the upgrade.
What I'm looking for (if possible):-
A non-rooted method of backing up application data from the phone before the downgrade
A way to downgrade 4.4.2 to 4.2.2 (I should be able to figure out how to root it once its back to jellybean)
A way to retain emoji's
Any help will be appreciated regarding this! Please try not to be too harsh, I'm trying hard to learn properly and not screw up with the process.
Thanks!
Click to expand...
Click to collapse
The only way is sending it for service to see if they could downgraded for you, which I doubt it. You can downgrade to Mk2 which is possible and try to isolate your problems.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

jd1639 said:
There is no way to downgrade to 4.2.2. Don't even waste your time.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your response jd! Can I ask why there isn't a way so far? Is it because of the kernel lock or something?
netomel said:
The only way is sending it for service to see if they could downgraded for you, which I doubt it. You can downgrade to Mk2 which is possible and try to isolate your problems.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for your response netomel! What instructions/thread can I follow to revert to mk2? Also is there a possible youtube video outlining the workable downgrade?

zdarkangel said:
Thank you for your response jd! Can I ask why there isn't a way so far? Is it because of the kernel lock or something?
Thank you for your response netomel! What instructions/thread can I follow to revert to mk2? Also is there a possible youtube video outlining the workable downgrade?
Click to expand...
Click to collapse
It is because of the locked bootloader. You can not downgrade the firmware, except from nb1/nc1 to mk2
Sent from my Nexus 5 using XDA Free mobile app

zdarkangel said:
Thank you for your response jd! Can I ask why there isn't a way so far? Is it because of the kernel lock or something?
Thank you for your response netomel! What instructions/thread can I follow to revert to mk2? Also is there a possible youtube video outlining the workable downgrade?
Click to expand...
Click to collapse
Sorry I did not provided before I though you would look for it. Anyway here is the link to a thread I follow.
http://forum.xda-developers.com/showthread.php?t=2663545
1. Usually you need first to flash full NB1 found on post # 2.
2. Downgrade to mk2 post#1 before reboot pull battery and back on. Put in recovery mode by pressing Vol up+ Home+ power at same time. Then factory reset and reboot to system.
Root using safe root
Install safe strap then install recovery within safestrap.
Flash Bypasslkm in safestrap.
Reboot fix wifi in universal init.d : turn on, tap on wififix then hit play.
Finish setup.
Once you are here you can choose any TW base rom.
Sent from my SCH-I545 using XDA Premium 4 mobile app

netomel said:
Sorry I did not provided before I though you would look for it. Anyway here is the link to a thread I follow.
http://forum.xda-developers.com/showthread.php?t=2663545
1. Usually you need first to flash full NB1 found on post # 2.
2. Downgrade to mk2 post#1 before reboot pull battery and back on. Put in recovery mode by pressing Vol up+ Home+ power at same time. Then factory reset and reboot to system.
Root using safe root
Install safe strap then install recovery within safestrap.
Flash Bypasslkm in safestrap.
Reboot fix wifi in universal init.d : turn on, tap on wififix then hit play.
Finish setup.
Once you are here you can choose any TW base rom.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's such a goofy way to fix wifi. I've never actually had to do that (mostly because it never actually worked for me). Flash this instead after you flash your TW based rom: NC1 wifi modules. Much more noob friendly, in my opinion! Domination and PurifieD both let you keep Androids emoji's instead of Samsung's.
A rough idea of how to flash a custom rom (PurifieD, in this example) would be:
Downgrade to MK2 as detailed above
Install and boot into Safestrap 3.72, flash PurifieD (wipe not necessary)
If you wish to keep Knox happy with 0x0, do not let PurifieD modify the kernel during the Aroma installer when it asks
Flash an i337 build.prop in order to get 4G LTE working again (you have service without this, but this lets you access LTE again) (you can find this here!)
Flash the WiFi module in order to get wifi working again (WiFi will NOT work unless you flash this) (you can find this here!)
(Optional, I had to do this as I had issues with keeping root on PurifieD, though you might not!) Flash SuperSU again (you can find this here!

Rhymey said:
That's such a goofy way to fix wifi. I've never actually had to do that (mostly because it never actually worked for me). Flash this instead after you flash your TW based rom: NC1 wifi modules. Much more noob friendly, in my opinion!
Click to expand...
Click to collapse
That's after you have flash NC1 rom, but this is when you downgrade to mk2 from there he could flash any TW rom. Actually it would be his choice. Maybe he can flash the mk2 modules before he flash other rom.
Sent from my SCH-I545 using XDA Premium 4 mobile app

netomel said:
Sorry I did not provided before I though you would look for it. Anyway here is the link to a thread I follow.
http://forum.xda-developers.com/showthread.php?t=2663545
1. Usually you need first to flash full NB1 found on post # 2.
2. Downgrade to mk2 post#1 before reboot pull battery and back on. Put in recovery mode by pressing Vol up+ Home+ power at same time. Then factory reset and reboot to system.
Root using safe root
Install safe strap then install recovery within safestrap.
Flash Bypasslkm in safestrap.
Reboot fix wifi in universal init.d : turn on, tap on wififix then hit play.
Finish setup.
Once you are here you can choose any TW base rom.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! That's a good start for me I guess. I still need to understand what each step means, and how to do them. Another thing, do you know if there's a way to retrieve all application data/backup my current rom state, without root, from my current NB1 build?

zdarkangel said:
Thanks! That's a good start for me I guess. I still need to understand what each step means, and how to do them. Another thing, do you know if there's a way to retrieve all application data/backup my current rom state, without root, from my current NB1 build?
Click to expand...
Click to collapse
This is more of a summary because some of the step cover separate threads for each. You got to do some reading. I gave you a link any how you will find the threads on the general section.
http://forum.xda-developers.com/showthread.php?t=2735644
Sent from my SCH-I545 using XDA Premium 4 mobile app

Thank you all for the information! I will go through the links you guys gave me and respond on here if I have any questions or if I need any more help. :fingers-crossed:

Can I install cm 11 or a stock kitkat rom that does not have touchwiz on my NB1?

I have a att s4 sgh-1337 with android 4.4.2. baseband version 1337UCUFNB1. I'm trying to put on CM 11. or another rom that looks like stock android with no touchwiz and 100% working and stable. if I downgrade to android 4.3. can I then root, install CWM recovery, and install CM 11?
what would happen if I booted into android system recovery and installed the cm 11 rom for my phone?

Gabe3 said:
I have a att s4 sgh-1337 with android 4.4.2. baseband version 1337UCUFNB1. I'm trying to put on CM 11. or another rom that looks like stock android with no touchwiz and 100% working and stable. if I downgrade to android 4.3. can I then root, install CWM recovery, and install CM 11?
what would happen if I booted into android system recovery and installed the cm 11 rom for my phone?
Click to expand...
Click to collapse
Short answer: No. You'll void your warranty and bootloop.
As for 'stock android look', I can recommend PurifieD or Google Play Edition ROM although it has a few bug that I'm going to work on once this semester ends..

Gabe3 said:
I have a att s4 sgh-1337 with android 4.4.2. baseband version 1337UCUFNB1. I'm trying to put on CM 11. or another rom that looks like stock android with no touchwiz and 100% working and stable. if I downgrade to android 4.3. can I then root, install CWM recovery, and install CM 11?
what would happen if I booted into android system recovery and installed the cm 11 rom for my phone?
Click to expand...
Click to collapse
No CM for now. You cannot replace the stock recovery. The only working recovery we have is safestrap.
You can use DVKM Tool and install BlackBox3.0 (Check post 3 of All things ATT thread)

thanks. hm, don't know what I should do. I bought this phone last week used on ebay so I dont think I have a warranty to void. another reason I wanted CM is so i could easily get updates. I dont really want to be messing with roms all the time. do you guys think cm will work soon? in the next few months? maybe I should stick with what I have till that happens. I'd rather wait for that then cause my self more headache.
does PurifieD come with the stock kitkat widgets?

Gabe3 said:
in the next few months? maybe I should stick with what I have till that happens. I'd rather wait for that then cause my self more headache.
does PurifieD come with the stock kitkat widgets?
Click to expand...
Click to collapse
No, probably not. The i337s bootloader is locked so we can't flash kernels. A lot of devs have moved onto newer devices so I doubt anything new will happen. And I'm not sure what the stock kitkat widgets are.

Rhymey said:
No, probably not. The i337s bootloader is locked so we can't flash kernels. A lot of devs have moved onto newer devices so I doubt anything new will happen. And I'm not sure what the stock kitkat widgets are.
Click to expand...
Click to collapse
what android version would the i337 need to have to be able to install cm 11? 4.2.x ? I'm thinking of asking the guy I bought mine from to see if he has any others that still have an older android version that would let me install cm on.

Gabe3 said:
what android version would the i337 need to have to be able to install cm 11? 4.2.x ? I'm thinking of asking the guy I bought mine from to see if he has any others that still have an older android version that would let me install cm on.
Click to expand...
Click to collapse
You'd need 4.2.2, mdb or mdl bootloader and firmware
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You'd need 4.2.2, mdb or mdl bootloader and firmware
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
in about device. is baseband version the firmware and build number the bootloader?
thanks.

Gabe3 said:
in about device. is baseband version the firmware and build number the bootloader?
thanks.
Click to expand...
Click to collapse
no. download 'phone info samsung' off the appstore and it'll tell you your bootloader version

Rhymey said:
no. download 'phone info samsung' off the appstore and it'll tell you your bootloader version
Click to expand...
Click to collapse
ok thanks. and baseband version is firmware?
will the att update automatically install if I connect to wifi?

Yes, it'll update on its own unless you root and delete or freeze the system update app.
Sent from my SGH-I337 using XDA Free mobile app

Thr33-F0ur said:
Yes, it'll update on its own unless you root and delete or freeze the system update app.
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
hm. Im not sure how to have the seller check for me then. if the phone has android 4.2.2, it should be on mdb or mdl, right?

Or it might have MF3. To find out, just go into Settings > About Phone (if the phone is complete stock unrooted, then the build number/baseband should match the boot loader)
Sent from my SGH-I337 using XDA Free mobile app

Thr33-F0ur said:
Or it might have MF3. To find out, just go into Settings > About Phone (if the phone is complete stock unrooted, then the build number/baseband should match the boot loader)
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
ok, thanks. i dont think the seller knows if its stock. if the phone got connected to the internet and updated automatically would the android version number change and baseband/build numbers?

Gabe3 said:
ok, thanks. i dont think the seller knows if its stock. if the phone got connected to the internet and updated automatically would the android version number change and baseband/build numbers?
Click to expand...
Click to collapse
yes. that's exactly what updating does.

[Q] Need Help Flashing Roms

I'm extremely new at rooting and flashing roms, so please excuse my ignorance. I have a Verizon Note 3 SM-900V. I'm running Android 4.4.2 and my Baseband version is NC4. I've rooted it using"TowelRoot" and have installed Safestrap 3.72. I've booted into recovery partitioned slot 1 and wiped it. Then I installed HyperdriveRLS7.zip I hit reboot after it says it's finished installing the rom. Whenever I try to boot into the rom (slot 1), my screen goes black and my blue LED light stays on. I also tried flashing the rom named "hltevzw.Jellybeans.zip" and it does the same thing. Am I doing something wrong or is anything incompatible with the other? Any input would be greatly appreciated. Thanks in advance for your help.
Sent from my SM-N900V using XDA Free mobile app

ElectroJoe said:
I'm extremely new at rooting and flashing roms, so please excuse my ignorance. I have a Verizon Note 3 SM-900V. I'm running Android 4.4.2 and my Baseband version is NC4. I've rooted it using"TowelRoot" and have installed Safestrap 3.72. I've booted into recovery partitioned slot 1 and wiped it. Then I installed HyperdriveRLS7.zip I hit reboot after it says it's finished installing the rom. Whenever I try to boot into the rom (slot 1), my screen goes black and my blue LED light stays on. I also tried flashing the rom named "hltevzw.Jellybeans.zip" and it does the same thing. Am I doing something wrong or is anything incompatible with the other? Any input would be greatly appreciated. Thanks in advance for your help.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
First of all you need to know that you cannot use rom slots on NC4 only the stock slot. You can use the stock slot to flash custom roms.
Second you need to update you firmware to the so-called unified firmware which is simply what you currently have and the NC2 kernel which can be found here. Just follow the instructions and you'll be good to go.
Third you should upgrade to Safestrap 3.75 found here.
If you have soft bricked your phone (this will be the case if after pulling the battery you cannot boot into Safestrap, you'll need to flash the stock firmware via odin which can be found here, reroot, and then follow the above directions.
Now once you get all this taken care of you can flash a custom rom. Any rom based on NC2/NC4 will work, however any rom based on any earlier firmware will not work and may softbrick your phone, Jellybeans being one of them. Make sure you read the OP (Original Post) before flashing anything. Know what you are flashing, if you are unsure there are many many forum posts to read through that are full of info.
If you have any other questions just ask.

Many Thanks!

Glad to help.

I have purchased a Moto X. Do you have any knowledge on flashing roms on it? I hate to be a bother.
Sent from my SM-N900V using XDA Free mobile app

ElectroJoe said:
I have purchased a Moto X. Do you have any knowledge on flashing roms on it? I hate to be a bother.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
Did you know the new Moto X was just announced and should be out in a couple months? Oh well, check out these forums. I don't know anything about the Moto X so I won't be able to help you sorry.