[fixed] NC1 - Bluetooth won't start, logcat provided, phone calling issue too - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I've never been good at pulling and producing logcats, and I'm using some Logcat Extreme app I found on the Play Store, so I'm not sure if this is going to help at all.... here's the background on the subject:
I just went from NB1 to NC1 by doing a full Odin of stock NB1, then flashing the NC1 update file, then got root and recovery from these steps here, all went very smoothly. The reason I did this was to fix a problem I've been having with placing and receiving calls - for some reason, my phone will make a call one minute and then not make one the next, usually connecting to whoever it is I'm calling, but no audio is produced at all. I use Bluetooth in the car, but that isn't the issue, it happened regardless of where I was.
So, I figured something was screwed up in the ROM, and since I don't have the time to reinstall everything even with using Titanium Backup as help, I got NC1 on the phone and then restored my data using Safestrap recovery from NB1 - while I'm very aware that I most likely brought my problem with me, I do believe that restoring data from TiBU would likely do the same thing, and I hate to be so busy right now that I can't even get my phone working by starting clean and then adding back everything one by one in order to ensure working condition, I just have to fix the problem on the back end of this right now....
So now that my phone is on NC1, calls are working okay right now (that may change) but the Bluetooth module will not come on at all. I turn it on, it turns it right off. I can't figure it out and don't even want to pretend I know what I'm doing with reading logcats, so I've attached it below. It contains a filtered logcat using the term "Bluetooth" as a filter. If someone can point me in the right direction, that would be great and I really appreciate it!
EDIT - I have wiped the ROM and installed everything from TiBU, everything works as normal now, just wish I didn't have to set my phone all back up from scratch again, I like using the restore data function of recovery, while not foolproof, it works great to quickly change ROMs and put all the data back on the phone as before

What baseband do you have or did you flash a modem?

Gage_Hero said:
What baseband do you have or did you flash a modem?
Click to expand...
Click to collapse
I did flash a modem, previous to getting NC1, I flashed the NC1 baseband.

Sounds like either something got restored from System data incorrectly or a hardware issue. The only way to confirm is the flash back to oute stock and see if it all works correctly. Then do not restore data from previous ROM and see if it works. Then use Tibu and restore one app at a time and check if it is/is not working.
Also the flash able modems do not contain the non-hlos.bin, so possibly if you have the NC1 or NB1 non-hlos.bin installed from flashing the stock rom, then flashing the modem that ONLY contains the modem.bin it may be a conflict? I do not recall that issue happening on previous firmwares that HAD TO use the matching modem.bin and non-hlos.bin but maybe Sammy did something in the newest releases?
I have used ALL the modems in my thread with no issues. But I am STILL on MDB boot loader, never flashed a non-hlos.bin, and ONLY flashed the modem.bin. I have not had ANY issues at all on any like you describe.
Sent fron I337 Red BadAss Themed ShoStock 7.0

I also have yet to flash non-hlos.bin with any modem.... only modem.bin. I used odin pc 3.07, uncheck the auto reboot, flash the modem, reboot back to download mode, flash the modem again and it has always been good to go.
If it was me, I would download the moden again, check the md5 to ensure the download is good and flash it twice... if that doesn't work.. I would go back to stock..... typically, if I flash a rom, I skip trying to restore anything.... I just let the apps redownload...

Downloaded again, checked MD5, flashed three times (I'm not flashing through Odin, just using the ones RR provided through Safestrap), and still no Bluetooth....
Sounding more and more like I'm going to have to start from scratch instead of dealing with it here, and if I have to do this now and get a new phone in the next few months (come ON Sammy, hurry up with the S5 Prime / Galaxy F / Galaxy Alpha already!), I'm gonna be pissed!

KryptosXLayer2 said:
Downloaded again, checked MD5, flashed three times (I'm not flashing through Odin, just using the ones RR provided through Safestrap), and still no Bluetooth....
Sounding more and more like I'm going to have to start from scratch instead of dealing with it here, and if I have to do this now and get a new phone in the next few months (come ON Sammy, hurry up with the S5 Prime / Galaxy F / Galaxy Alpha already!), I'm gonna be pissed!
Click to expand...
Click to collapse
I don't follow Safestrap too much but don't you have to flash a certain module to get it to work correctly? Again I am not up on Safestrap but I know I have seen a module talked about
Sent fron I337 Red BadAss Themed ShoStock 7.0

RockRatt said:
I don't follow Safestrap too much but don't you have to flash a certain module to get it to work correctly? Again I am not up on Safestrap but I know I have seen a module talked about
Sent fron I337 Red BadAss Themed ShoStock 7.0
Click to expand...
Click to collapse
I have seen something about that too, but like you, I don't know enough about it.... I thought for a modem file, I don't need that, but I've been wrong before!
EDIT - I have wiped the ROM and installed everything from TiBU, everything works as normal now, just wish I didn't have to set my phone all back up from scratch again, I like using the restore data function of recovery, while not foolproof, it works great to quickly change ROMs and put all the data back on the phone as before

Related

[Q] The Ultimate BRICKED Samsung Galaxy S4 Challenge =)

Long Story As Short As Possible:
1-I Rooted my Sprint Galaxy S4 (with MF9) using Qbking77's You tube instructions (No Probs) !!
2-I dropped the Services.Odex, and Services.Jar into the systems/folder to replace the ones in there using root explorer to get the native hot spot working (It did NOT work) !!!
3-So I flashed via oden a "New" hot spot for rooted roms: "MDCHotspotMod-Odexed" onto the system, and now I am bricked...
I can boot into TWRP, BUT can't flash a rom to the system as it Fails.
I can flash the root "CF-Auto-Root-jfltespr-jfltespr-sphl720.tar" via oden which puts the stock recovery back onto the phone, BUT that wont't flash roms either.
SO, at a complete loss, I factory reset the device wiping everything, and it just boots to the Samsung Galaxy S4 Logo.
I downloaded the following: L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 to try and flash back to stock in Oden, BUT, when I hit "Start" it doesn't do anything but say "The Parameter is incorrect"
This is the Stock MDC File, NOT the MF9 that my phone was currently on...
ANY SUGGESTIONS !!! Thanks guys.
Solved !!! Used MF9 Stock Tar file in Oden !!!
Glad you got it working!
Just in case you were wondering why it didn't work initially - you were on MF9, and you tried to flash the MDC hotspot mod.
And yes, flashing the stock MF9 in ODIN was the right step to fix this. If you now want to install the hotspot mod, make a nandroid backup, download the MF9 version and flash it in TWRP.
jj14 said:
Glad you got it working!
Just in case you were wondering why it didn't work initially - you were on MF9, and you tried to flash the MDC hotspot mod.
And yes, flashing the stock MF9 in ODIN was the right step to fix this. If you now want to install the hotspot mod, make a nandroid backup, download the MF9 version and flash it in TWRP.
Click to expand...
Click to collapse
Any word on getting the hot spot feature working on the MF9 ?? Either Wifi Tether (specific settings), OR the regular built in Hot Spot?? Thanks... Also, I def know about the different software versions I.E. MDL, MDC, and MF9, the site said that particular file would take me back to stock & I would just have to OTA !!! Guess they were wrong, lol...:laugh: Anywho, thanks again, it's nice being able to get help when needed !!!
Ar3ohdee said:
Any word on getting the hot spot feature working on the MF9 ?? Either Wifi Tether (specific settings), OR the regular built in Hot Spot?? Thanks... Also, I def know about the different software versions I.E. MDL, MDC, and MF9, the site said that particular file would take me back to stock & I would just have to OTA !!! Guess they were wrong, lol...:laugh: Anywho, thanks again, it's nice being able to get help when needed !!!
Click to expand...
Click to collapse
Here you go bro, this should do the trick and get a working hotspot mod for you on that s4
http://forum.xda-developers.com/showthread.php?p=40860639
[MOD][Deodex][Odex][MDC][MDL][MF9]Hotspot Mod
gs4 stock rooted running mf9
MENACE_69 said:
Here you go bro, this should do the trick and get a working hotspot mod for you on that s4
http://forum.xda-developers.com/showthread.php?p=40860639
[MOD][Deodex][Odex][MDC][MDL][MF9]Hotspot Mod
gs4 stock rooted running mf9
Click to expand...
Click to collapse
Yep - this is the one that I use as well.
@Ar3ohdee Just make sure that you get the correct version depending on your ROM - odex/deodex and MDC/MDL/MF9
BTW, if you were on stock MDC, you could update OTA to MDL and then to MF9 - that option would have worked too. But flashing the stock MF9 is quicker.
just bricked my galaxy s4 and its stuck at samsung custom screen.. cant get it out of it.... what do i do.. i'm new to this and i new i was going to do this sooner or later....
wahlmart said:
just bricked my galaxy s4 and its stuck at samsung custom screen.. cant get it out of it.... what do i do.. i'm new to this and i new i was going to do this sooner or later....
Click to expand...
Click to collapse
you may need to give us more info than that. what did you try flashing? were you already running a custom rom? mdc, mdl, mf9? did you try manually booting to recovery? (power + vol up)
open a new thread too, may have better luck
Ar3ohdee said:
Solved !!! Used MF9 Stock Tar file in Oden !!!
Click to expand...
Click to collapse
Where'd you find the MF9 Stock Tar file? I screwed up my phone with the wrong version of the hotspot files....
jm1fd said:
Where'd you find the MF9 Stock Tar file? I screwed up my phone with the wrong version of the hotspot files....
Click to expand...
Click to collapse
You mean like from here?
http://forum.xda-developers.com/showthread.php?t=2357471
Bricked on mk2
So I was on stock rooted mk2 with twrp recovery. Did a nand. Flashed kt kernel. Phone wouldn't get passed Samsung splash screen. Couldn't even boot into recovery. Took it to best buy. Tech, if you can call him that, said was bricked and I needed a replacement. Luckily just bought it so free replacement. Played dumb. Probably could have recovered if I Odin the stock firmware. My question is, what do you think caused the brick? Mk2 bootloader? Twrp? The kernel? I flashed plenty of roms and kernels on my s2 without problems. BTW flashed Hotspot mod with cwm and worked.

Can only connect to LTE; can't make or get calls/text

I'm running Triforce 4.0 on MJA. My phone acts like it's looking for a signal but can only find LTE. The data on LTE works fine. Wifi also works. In my settings, it says my phone number is unknown (I have gotten it to also just say 0 while trying to get it to work) and my MIN is also unknown. It says my PRL version is 1, even after updating it. Everything worked fine until I tried flashing a new rom which wouldn't even boot. I restored my nandroid backup and that's where this whole mess started. Tried flashing the MK2 modem in odin, and even though it flashed successfully, it changed nothing and my settings also still say I'm on MJA.
I even went to the Sprint store, and a helpful fellow tried to flash it back to complete out of the box stock using Kies but it threw up an error and soft bricked me. Fudged up the flash counter somehow, too. He said he couldn't get me a replacement because he obviously knows I voided the warranty, but told me to go to another store and just tell them it was a 4.3 update gone awry and they'd get me a replacement because it was in a state where you really couldn't tell it was rooted. It worked, and they ordered a new one but said it'll take two days. In the meantime, I decided that I could get to the bottom of this because I still have data on my internal storage I want. I unbricked it, got my nandroid backup running and now I'm pretty much right back where I was earlier today. And I'm out of ideas. Does anyone know what it means when the phone forgets its own number? What can cause this? How can it be remedied? How can it be avoided?
Since you already tripped the counter and the Sprint guy you took it to was a boob..
You could grab the MK2 .tar from here (the tar.md5 is in the zip, just extract the .tar.md5 and put that one file in the PDA slot of Odin) and flash it via Odin. It'll reset everything (all partitions and modem etc.) Then re-root via CF-Autoroot, add recovery using GooManager and then do what ever you want.
leaderbuilder said:
Since you already tripped the counter and the Sprint guy you took it to was a boob..
You could grab the MK2 .tar from [snip]snip[/URL] (the tar.md5 is in the zip, just extract the .tar.md5 and put that one file in the PDA slot of Odin) and flash it via Odin. It'll reset everything (all partitions and modem etc.) Then re-root via CF-Autoroot, add recovery using GooManager and then do what ever you want.
Click to expand...
Click to collapse
I was going to try downloading that, but I've already downloaded two other firmwares and I have an extremely small amount of data I can use per month (10GB) because I'm using Verizon's LTE. Nothing else is available where I live. My bill is already going to be $200, so I made one last ditch effort to get things to work without wasting ANOTHER gigabyte because not only did I not want to wait 7 hours for that download, I didn't want to download it at all because the previous firmwares I downloaded wouldn't even flash. They fail in Odin. Er, one of them does, anyway. The other one I downloaded was just not the right firmware.
So I tried just random things and typed ##72786# into the dialer. Phone rebooted, and everything works now, somehow. I'm still not sure what causes this, but as long as I can reliably fix it any time it happens then it's not a big problem. Now I just have to tell the guys at the other Sprint store that I don't need the replacement. Thanks for the help, by the way!
Skeezixmccat said:
I was going to try downloading that, but I've already downloaded two other firmwares and I have an extremely small amount of data I can use per month (10GB) because I'm using Verizon's LTE. Nothing else is available where I live. My bill is already going to be $200, so I made one last ditch effort to get things to work without wasting ANOTHER gigabyte because not only did I not want to wait 7 hours for that download, I didn't want to download it at all because the previous firmwares I downloaded wouldn't even flash. They fail in Odin. Er, one of them does, anyway. The other one I downloaded was just not the right firmware.
So I tried just random things and typed ##72786# into the dialer. Phone rebooted, and everything works now, somehow. I'm still not sure what causes this, but as long as I can reliably fix it any time it happens then it's not a big problem. Now I just have to tell the guys at the other Sprint store that I don't need the replacement. Thanks for the help, by the way!
Click to expand...
Click to collapse
Glad you got it back with Activation.
Thanks for reporting the solution too! Helps the community.
leaderbuilder said:
Since you already tripped the counter and the Sprint guy you took it to was a boob..
You could grab the MK2 .tar from here (the tar.md5 is in the zip, just extract the .tar.md5 and put that one file in the PDA slot of Odin) and flash it via Odin. It'll reset everything (all partitions and modem etc.) Then re-root via CF-Autoroot, add recovery using GooManager and then do what ever you want.
Click to expand...
Click to collapse
What do you mean he was a boob? Lol
Sent from my SPH-L720 using Tapatalk
I would like to add that simply going to the option in settings to activate the device never worked, nor did updating PRL, profile, etc. Any time I tried to just reactivate the device using the option to do so, it would say there was an error.
sorry if this is a dumb question, but...
if you go into your mobile network settings, is your cdma subscription set to nv? if not, try switching that.
edit: sorry if i came a little late but i think that's the problem.

[Q] WiFi not working after update via Kies from 4.3. to 4.4.2

Hi there,
i have a rooted S4 i9505 with cwm installed.
yesterday i did an update from stock rom 4.3 to 4.4.2 (I9505XXUEMKE) via KIES.
the problem now....I cant turn on the wifi anymore. whenever i try to use the on/off switch for the wifi it instandly switches back to off.
is anyone else experiencing the same problem? has someone already a solution for that, before i will do a factory reset.
SDA1979 said:
Hi there,
i have a rooted S4 i9505 with cwm installed.
yesterday i did an update from stock rom 4.3 to 4.4.2 (I9505XXUEMKE) via KIES.
the problem now....I cant turn on the wifi anymore. whenever i try to use the on/off switch for the wifi it instandly switches back to off.
is anyone else experiencing the same problem? has someone already a solution for that, before i will do a factory reset.
Click to expand...
Click to collapse
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Jimsilver73 said:
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Click to expand...
Click to collapse
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
SDA1979 said:
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
Click to expand...
Click to collapse
Its correct
SDA1979 said:
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
Click to expand...
Click to collapse
you are on the new bootloader so you can flash the complete package - it has everything in it all in one package! - you won't brick your phone even if you flash the wrong modem, that is unless you did some thing real dumb like flash i9500 modem and even then I think its recoverable not that I suggest you try!!
depends where you are in the world - I used NB8 and it worked well for me in the UK - I'm on NB9 now and that seems nice also.
so to be clear flash this:
Combined package
For NewBootloader
GSM_Modem_XXUFNB8_and_LTE_Modem_XXUFNB8
https://mega.co.nz/#!3dR30JiT!cP5WrUCfz9L4h8doY7KTTV6fq4pFL85EkJBG6T-Gqhc
Jimsilver73 said:
you are on the new bootloader so you can flash the complete package - it has everything in it all in one package! - you won't brick your phone even if you flash the wrong modem, that is unless you did some thing real dumb like flash i9500 modem and even then I think its recoverable not that I suggest you try!!
depends where you are in the world - I used NB8 and it worked well for me in the UK - I'm on NB9 now and that seems nice also.
so to be clear flash this:
Combined package
For NewBootloader
GSM_Modem_XXUFNB8_and_LTE_Modem_XXUFNB8
https://mega.co.nz/#!3dR30JiT!cP5WrUCfz9L4h8doY7KTTV6fq4pFL85EkJBG6T-Gqhc
Click to expand...
Click to collapse
hey guys, thank you!!!
the Wi-Fi is working again.
Nonetheless i still have one problem remaining, which i thought it would have been fixed as well.
but, when GPS is turned on, it tries to find the GPS position and the icon on the status bar continues appearing and disappearing permanently (every half of a second).
Beside the fact that it is really annoying having this icon flashing all the time it also causes the display to freeze.
Especially when scrolling from top to the bottom to open the notification area.
It sometimes also lets the system crush completely.
any idea what this could be?
thanks for your effort so far.
SDA1979 said:
hey guys, thank you!!!
the Wi-Fi is working again.
Nonetheless i still have one problem remaining, which i thought it would have been fixed as well.
but, when GPS is turned on, it tries to find the GPS position and the icon on the status bar continues appearing and disappearing permanently (every half of a second).
Beside the fact that it is really annoying having this icon flashing all the time it also causes the display to freeze.
Especially when scrolling from top to the bottom to open the notification area.
It sometimes also lets the system crush completely.
any idea what this could be?
thanks for your effort so far.
Click to expand...
Click to collapse
hmmm......... thats not right!
Suggest you find a stock sammy ROM and flash anew in odin - then root using cf root, then flash recovery - (TWRP is very good :good then go into recovery and wipe cache, dalvik, system and data - reboot and see what happens on nice new shiny sammy stock - if all is good pick the ROM/kernel you want (if you want) and go back to odin to reflash modem.
The only other thing I can think is that you have an app that is messing with gps?? Do the above though and you should be golden :good:
EDIT: don't wipe system unless you planning flashing a different ROM through recovery!
Jimsilver73 said:
hmmm......... thats not right!
Suggest you find a stock sammy ROM and flash anew in odin - then root using cf root, then flash recovery - (TWRP is very good :good then go into recovery and wipe cache, dalvik, system and data - reboot and see what happens on nice new shiny sammy stock - if all is good pick the ROM/kernel you want (if you want) and go back to odin to reflash modem.
The only other thing I can think is that you have an app that is messing with gps?? Do the above though and you should be golden :good:
Click to expand...
Click to collapse
Hi, right way to flash the stock Samsung package, but after flashing a custom recovery, do not wipe system. There's no ROM after that so phone will not boot. And the newest modem is integrated in the stock package, so no need to flash it again.
And another advice: NEVER use Kies to update your phone. It has bricked 3 of mines.:cyclops:
speedwayfan75 said:
Hi, right way to flash the stock Samsung package, but after flashing a custom recovery, do not wipe system. There's no ROM after that so phone will not boot. And the newest modem is integrated in the stock package, so no need to flash it again.
And another advice: NEVER use Kies to update your phone. It has bricked 3 of mines.:cyclops:
Click to expand...
Click to collapse
Oops, well spotted! Yes, don't wipe system unless you have another ROM to flash through recovery. 3 phones bricked from kies huh? I never used it SVD don't think I ever will lol. Good old Sammy stock stuff, tbh that's why I steer well clear of anything stock Sammy unless absolutely necessary and last resort - I look at the farce they have made by forcing us to accept Knox pox!
Jimsilver73 said:
Oops, well spotted! Yes, don't wipe system unless you have another ROM to flash through recovery. 3 phones bricked from kies huh? I never used it SVD don't think I ever will lol. Good old Sammy stock stuff, tbh that's why I steer well clear of anything stock Sammy unless absolutely necessary and last resort - I look at the farce they have made by forcing us to accept Knox pox!
Click to expand...
Click to collapse
my thought was to go into recovery mode and wipe everything and start from beginning in order to exclude that it could depends on some wrong settings or any software already installed....
I updated to 4.4.2 using Mobile Odin and my wifi was borked too.
I did notice after the update that there was a mismatch between my Baseband version (still the old 4.3 XXUEMKE) and the Build number XXUFNB8, and I recall seeing some message during the flashing process that security had blocked the kernel update and Triangle Away might help solve it.
I therefore ran Triangle Away to reset my flash counter, and then used Mobile Odin to have a second go at flashing just the Kernel, Recovery and Modem parts.
This was successful and I now have matching Baseband and Build, both XXUFNB8.
And my wifi now works again...
ok.. after making a factory reset wifi and gps are working fine again.
guess there was some missconfigured third party app...
but now, with a fresh system i do not understand why i am not able to assign a PIN for my lockscreen...
everything is greyed out except PIN and Password.
but even though setting up a PIN, the screen lock is always set to use Swipe......
damn, i shouldnt have updated to 4.4.2.... until now.. only problems with this new build....
SDA1979 said:
ok.. after making a factory reset wifi and gps are working fine again.
guess there was some missconfigured third party app...
but now, with a fresh system i do not understand why i am not able to assign a PIN for my lockscreen...
everything is greyed out except PIN and Password.
but even though setting up a PIN, the screen lock is always set to use Swipe......
damn, i shouldnt have updated to 4.4.2.... until now.. only problems with this new build....
Click to expand...
Click to collapse
Try slimkat 3.2 from here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/909-jfltexx remember to download gapps and flash after you have flashed ROM. You won't be disappointed
Jimsilver73 said:
Try slimkat 3.2 from here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/909-jfltexx remember to download gapps and flash after you have flashed ROM. You won't be disappointed
Click to expand...
Click to collapse
hey thanks for your suggestion. but i want to keep using the stock rom. sufficent for my needs....
anyway.. finally i was able to get everything working after flashing the rom with odin again.
Jimsilver73 said:
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Click to expand...
Click to collapse
I feel compelled to express my gratitude for the post. Two days ago i updated from 4.3 to 4.4.2 on my rooted gt-i9505 via KIES and just like that no more wifi. This solution works like charm!!!
:good::good::good::good::good::good:

[Q] "Downloading.... Do not turn off target!" after TWRP

Can I get a little help here? I have a rooted, otherwise stock i337 that I just used the TWRP root app. I wanted to make a backup of my phone before I flashed a new rom. It downloaded jflteatt and I verified and installed it to /dev/block/mmcblk0p21. then i tried to make a backup, and i'm stuck at "Downloading.... do not turn off target!!!" In the upper left corner there's a "Could not do normal boot. ODIN Mode.
I found the post "[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3" but am hesitant to use it, as I am not sure that is what I need to do. I also found some other similar posts, but for different devices so I am again hesitant to rely on those.
I tried pressing home, power and volume down, but it just resets back to this screen. Also, I originally posted this request on the TWRP page, but I think it should be here. If so, I will delete it there.
Please help?
@kamikazees
If you could give more detail that would also help other to help u....such as what firmware that u are running before bricked...... well seem to me that u are either MF3 or MK2 firmware and u installed TWRP ...... u can only install safestrap recovery if u are on MF3 or MK2 firmware. ....Follow my thread http://forum.xda-developers.com/showthread.php?t=2621279 it should get u back to MK2 firmware. .....goodluck
Swyped From MK2 Dark Venom SS Edition
Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.
kamikazees said:
Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.
Click to expand...
Click to collapse
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.
DeadlySin9 said:
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.
Click to expand...
Click to collapse
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
The first one is in img format and won't work through ODIN, but you can use those commands from terminal emulator to flash it if you download it. Otherwise, the TAR files do work just fine.
kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
If you are rooted and can actually boot the phone then I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery. I've been using Safestrap and TWRP since I was on MF3. I have also successfully flashed the tar files through Odin to get to MK2 with no problems. If you are rooted then its a really good idea to use Safestrap with TWRP for a recovery. Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable. The stock recovery on this phone is pretty much useless.
megamanDJ said:
...I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery... Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable.
Click to expand...
Click to collapse
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!
kamikazees said:
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!
Click to expand...
Click to collapse
There is actually a way to flash a rom to the stock slot, but I haven't done it. Somewhere in the Safestrap threads explains how to do it. I think you can even get it back to normal if you change your mind.

I337 AT&T S4 - Return to Stock (No WiFi)

I recently bit off more than I could chew with my S4 (I337). I had 4.4.2 KitKat on it and wanted to root it to add teathering. I decided thought there was no root for 4.4.2 so I thought I would try downgrading to 4.3 then root. This seemed best because I didn't like the way the SD card is handled in 4.4.2 and some of my apps (like ftp server) have stopped working.
When I got the phone back up from flashing with Odin it says it has version 4.3. My WiFi will not turn on. If I slide the switch to on it slides right back to off and the phone tells me that an operation was block (can't remember the full verbage. I have installed and attempted to install many things on my phone. I have used recovery mode / Odin3 and Kies (Kies doesn't allow much).
At this point I just would like to get my phone back to 4.4.2 with the WiFi working. Then I can restore my backup and be back to square one with a lesson learned.
I have an I337 that currently thinks it has version 4.3 on it. The baseband version is I337UCUFNC1 currently. The build number is JSS15J.I337UCUEMK2.
If anyone can help I would greatly appreciate it. I have read and tried many things over a two day period and finally decided to ask for help.
Had this issue before on my Bell Canada S4, but don't recall exact way to fix it.
Think the solution was to find an older (might be newer) stock. I think I used a different version like the Telus Canada version as well and it ended up working. Then you update through kies after.
jbrudda said:
I recently bit off more than I could chew with my S4 (I337). I had 4.4.2 KitKat on it and wanted to root it to add teathering. I decided thought there was no root for 4.4.2 so I thought I would try downgrading to 4.3 then root. This seemed best because I didn't like the way the SD card is handled in 4.4.2 and some of my apps (like ftp server) have stopped working.
When I got the phone back up from flashing with Odin it says it has version 4.3. My WiFi will not turn on. If I slide the switch to on it slides right back to off and the phone tells me that an operation was block (can't remember the full verbage. I have installed and attempted to install many things on my phone. I have used recovery mode / Odin3 and Kies (Kies doesn't allow much).
At this point I just would like to get my phone back to 4.4.2 with the WiFi working. Then I can restore my backup and be back to square one with a lesson learned.
I have an I337 that currently thinks it has version 4.3 on it. The baseband version is I337UCUFNC1 currently. The build number is JSS15J.I337UCUEMK2.
If anyone can help I would greatly appreciate it. I have read and tried many things over a two day period and finally decided to ask for help.
Click to expand...
Click to collapse
Root, install safestrap then flash this ROM and you will be good to go: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Thanks
muniz_ri said:
Root, install safestrap then flash this ROM and you will be good to go: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Click to expand...
Click to collapse
Quite a few steps in those threads but I got it working again. I really appreciate all the help/advice given. Now to decide if I want to remove the safestrap screen on boot. Again Thanks.
Same problem,need help plz
Hi guys,
I have the same problem as jbrudda.i wiped everything using Odin3_v3.09 and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar . and now my wifi is not working. when i try to turn it on a security message pop up (the device has detected an application attempting to perform actions that are not permitted these actions have been blocked)and ask me to reboot, then it does a factory reset on its own. but the problem is still there no wifi. my baseband is diffrent than jbrudda's. mine is I337UCUAMDB. can someone plz help. thank you
karim8888 said:
Hi guys,
I have the same problem as jbrudda.i wiped everything using Odin3_v3.09 and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar . and now my wifi is not working. when i try to turn it on a security message pop up (the device has detected an application attempting to perform actions that are not permitted these actions have been blocked)and ask me to reboot, then it does a factory reset on its own. but the problem is still there no wifi. my baseband is diffrent than jbrudda's. mine is I337UCUAMDB. can someone plz help. thank you
Click to expand...
Click to collapse
Wifi does not work because of the modem/kernel mismatch, i.e. MDB modem and MK2 kernel. Not sure what your goal was when you began flashing your phone but since you fortunately did not flash teh MK2 bootloader you are still able to locate the MDB full odin tar and flash back to stock which will resolve your issue.
muniz_ri said:
Wifi does not work because of the modem/kernel mismatch, i.e. MDB modem and MK2 kernel. Not sure what your goal was when you began flashing your phone but since you fortunately did not flash teh MK2 bootloader you are still able to locate the MDB full odin tar and flash back to stock which will resolve your issue.
Click to expand...
Click to collapse
I did Root it with saferoot and safestarp.the wifi didnt work so i had to find a script here on xda and i run it throughout universal init.d . i didnt like the way my phone was running . so i decided to unroot it . so you think im using the wrong TAR file ???
karim8888 said:
I did Root it with saferoot and safestarp.the wifi didnt work so i had to find a script here on xda and i run it throughout universal init.d . i didnt like the way my phone was running . so i decided to unroot it . so you think im using the wrong TAR file ???
Click to expand...
Click to collapse
It depends on what you are trying to accomplish. Are you trying to upgrade to MK2 or higher while maintaining your unlocked MDB bootloader?
muniz_ri said:
It depends on what you are trying to accomplish. Are you trying to upgrade to MK2 or higher while maintaining your unlocked MDB bootloader?
Click to expand...
Click to collapse
I'm just trying to take it back to the why it was. and upgrade to kitkat. i have now build number JSS15J.I337UCUEMK2 baseband : I337UCUAMDB
what do you think i should do?? I appreciate your help.
karim8888 said:
I'm just trying to take it back to the why it was. and upgrade to kitkat. i have now build number JSS15J.I337UCUEMK2 baseband : I337UCUAMDB
what do you think i should do?? I appreciate your help.
Click to expand...
Click to collapse
If you don't care about losing your MDB unlocked bootloader you can get to the latest kitkat firmware by flashing the NB1 full odin tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223, then once flashing is complete go to settings/more/about phone/software update then take the ota update to NC1 which is the latest kitkat version for our phone.
But what I would do is keep your unlocked MDB bootloader and since you already flashed the MK2 AP file you can get your phone running well again by flashing the MK2 modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg
From there, there are still a number of options available to get to kitkat which I won't get into.
muniz_ri said:
If you don't care about losing your MDB unlocked bootloader you can get to the latest kitkat firmware by flashing the NB1 full odin tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223, then once flashing is complete go to settings/more/about phone/software update then take the ota update to NC1 which is the latest kitkat version for our phone.
But what I would do is keep your unlocked MDB bootloader and since you already flashed the MK2 AP file you can get your phone running well again by flashing the MK2 modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg
From there, there are still a number of options available to get to kitkat which I won't get into.
Click to expand...
Click to collapse
I will try this steps and let you know.thanks a lot.
It worked "muniz_ri". Thanks a lot for your help, I really appreciate it. :laugh::good:
karim8888 said:
It worked "muniz_ri". Thanks a lot for your help, I really appreciate it. :laugh::good:
Click to expand...
Click to collapse
Hey guys.
I lost al sounds on my phone now.Wifi is running , I thought the fix worked but the sound is out now. any suggestions???
Thank you.
jbrudda said:
I recently bit off more than I could chew with my S4 (I337). I had 4.4.2 KitKat on it and wanted to root it to add teathering. I decided thought there was no root for 4.4.2 so I thought I would try downgrading to 4.3 then root. This seemed best because I didn't like the way the SD card is handled in 4.4.2 and some of my apps (like ftp server) have stopped working.
When I got the phone back up from flashing with Odin it says it has version 4.3. My WiFi will not turn on. If I slide the switch to on it slides right back to off and the phone tells me that an operation was block (can't remember the full verbage. I have installed and attempted to install many things on my phone. I have used recovery mode / Odin3 and Kies (Kies doesn't allow much).
At this point I just would like to get my phone back to 4.4.2 with the WiFi working. Then I can restore my backup and be back to square one with a lesson learned.
I have an I337 that currently thinks it has version 4.3 on it. The baseband version is I337UCUFNC1 currently. The build number is JSS15J.I337UCUEMK2.
If anyone can help I would greatly appreciate it. I have read and tried many things over a two day period and finally decided to ask for help.
Click to expand...
Click to collapse
I told you not to drink and root.
jbrudda said:
Quite a few steps in those threads but I got it working again. I really appreciate all the help/advice given. Now to decide if I want to remove the safestrap screen on boot. Again Thanks.
Click to expand...
Click to collapse
excited to give this a try. rooted with the downgrade method a couple months ago but left with a non-wifi device. my only issue is that the thread says it's for I337UCUFNC1 and our devices are on jss15j.i337ucuemk2. will this fix still work? I've heard on other threads on the subject that the modem kernel doesn't match up with the flashed rom or build number or something.
bux
karim8888 said:
Hi guys,
I have the same problem as jbrudda.i wiped everything using Odin3_v3.09 and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar . and now my wifi is not working. when i try to turn it on a security message pop up (the device has detected an application attempting to perform actions that are not permitted these actions have been blocked)and ask me to reboot, then it does a factory reset on its own. but the problem is still there no wifi. my baseband is diffrent than jbrudda's. mine is I337UCUAMDB. can someone plz help. thank you
Click to expand...
Click to collapse
Do you already fix it??? cause i have the same problem
Same question, different thread!
Not even an hour ago did I answer the same question in a different thread: How do I get WiFi working on my S4?
Well here you go.
My original answer: http://forum.xda-developers.com/gal...-4-4-2-nb1-t2850878/post54978150#post54978150
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks!
Click to expand...
Click to collapse
Those are my exact words. Also, the attached files (NB1 modules, SuperSU, Towelroot, etc.) can be found attached to my post in the link above. Have a good night, and best of luck! :good::good::good:
Had the Wifi Not Working - Fixed
muniz_ri said:
If you don't care about losing your MDB unlocked bootloader you can get to the latest kitkat firmware by flashing the NB1 full odin tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223, then once flashing is complete go to settings/more/about phone/software update then take the ota update to NC1 which is the latest kitkat version for our phone.
But what I would do is keep your unlocked MDB bootloader and since you already flashed the MK2 AP file you can get your phone running well again by flashing the MK2 modem: https://mega.co.nz/#!pwESna5I!YK7EKG37xXIG1ReB-Z-mfSMoXNkXQ9t2EdMK9ofgJKg
From there, there are still a number of options available to get to kitkat which I won't get into.
Click to expand...
Click to collapse
I just flashed I337MK2StockModem.tar.md5 and now it works!! I'm on the MK2 and rooted with saferoot and safestrap recovery 3.72
iqcomputers said:
I just flashed I337MK2StockModem.tar.md5 and now it works!! I'm on the MK2 and rooted with saferoot and safestrap recovery 3.72
Click to expand...
Click to collapse
See the thread I started with a similar problem.
http://forum.xda-developers.com/galaxy-s4-att/help/rogers-samsung-s4-4-2-2-i337m-wifi-t3256535
Would I be able to use this fix?

Categories

Resources