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.
Related
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
tr10 said:
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
Click to expand...
Click to collapse
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
xBeerdroiDx said:
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
Click to expand...
Click to collapse
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
tr10 said:
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
Click to expand...
Click to collapse
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice, I have done that countless times. I'm hoping that it changes one of these times though.
I took your advice regarding re-flashing the image and ticking the bootloader update option, odin stated it was successful and auto-rebooted. I pulled the battery and tried to enter recovery, no cigar.
Perhaps try the Heimdall route: http://forum.xda-developers.com/showthread.php?t=2374441
When attempting to flash TWRP recovery, my phone says in the top right hand corner:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enabled
START [224, 1440]
SECURE CHECK FAIL: recovery
Don't know what that means.
I haven't tried the heimdall method yet, not sure if I wanna give it a shot because it seems a lot more complex only to accomplish the same thing odin would. I can imagine something is stopping odin from putting a bootloader, or kernel. That same thing would stop heimdall. But, I have no idea what I'm talking about. Waiting to hear more advice before I make the hole I dug deeper.
Thank you for your time guys.
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Febby said:
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
xBeerdroiDx said:
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Click to expand...
Click to collapse
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
tr10 said:
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
Click to expand...
Click to collapse
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Febby said:
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Aou said:
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Click to expand...
Click to collapse
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Febby said:
I actually considered switching to a ONE today.
Click to expand...
Click to collapse
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
Either way. Also, if one fails, try the other of course.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
I converted the .img to a .tar and I sadly had the same results =( Thank you for the idea though, definitely helped.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
Thank you, I attempted to reflash the stock kernel included in the MDL package. No avail. Same problem. Good advice though!
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
I just reflashed the stock kernel, no cigar =( It is very strange to me that I can't get the phone to respond to anything other than download mode. Especially considering that I odin'd to stock. I'm starting to think I made it worse by going back to stock after flashing slimbean's weekly update.
Thank you for your time guys, keep the ideas coming, I'm definitely trying to come up with my own ideas.
I have so far done the following:
Odin'd MDL, MDB, Stock Kernel, Stock Recovery (All through download mode, as I don't have access to recovery.)
I've also tried to odin TWRP but I fail in Odin since download mode blocks the illegal recovery.
Thank you again for your time.
tr10 said:
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Click to expand...
Click to collapse
Im not so sure how everyone just over looked this but the rom in that link is for the att S3. So you flashed an S3 rom to your S4.
D2att is the s3 for att.
Jflteatt is the att variant.
http://www.slimroms.net/index.php/downloads/all/viewcategory/620-jflteatt
Thats the correct link to weekly roms for slim rom for our device. your partitions might just be corrupted in case maybe having a jtag or using the pit file for MDL would fix? :/ im not an expert haha just observations.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------
xBeerdroiDx said:
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Click to expand...
Click to collapse
You sure? On the att one majority of devs dont post on the att htc one section but eather "HtC one" section since all roms work vice versa on that phone international roms > works on all models of the one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hi,
I have looked all over this website and others for the solution to my problem. If there is a thread for this then I am sorry, but I couldnt find it.
I recently moved from the US to Mexico. I took my SPH-L720 to a phone technician to get my SIM unlocked and am now using it on the Iusacell network. Everything was working fine until I tried to install the MK2 update. The OTA update downloaded just fine, but when it is installing it gets about halfway and then displays a dead Android robot with a red triangle and an exclamation mark and the word "Error".
I do not believe that the phone technician rooted my phone. I think he flashed my modem to MDC. My build number is MJA. My software version is MDC.
Can anybody help me? My phone seems quirky after the MJA update, especially battery life. I am hoping MK2 will fix everything. Also, I have a Mac and not a PC.
newyorkcfc said:
Hi,
I have looked all over this website and others for the solution to my problem. If there is a thread for this then I am sorry, but I couldnt find it.
I recently moved from the US to Mexico. I took my SPH-L720 to a phone technician to get my SIM unlocked and am now using it on the Iusacell network. Everything was working fine until I tried to install the MK2 update. The OTA update downloaded just fine, but when it is installing it gets about halfway and then displays a dead Android robot with a red triangle and an exclamation mark and the word "Error".
I do not believe that the phone technician rooted my phone. I think he flashed my modem to MDC. My build number is MJA. My software version is MDC.
Can anybody help me? My phone seems quirky after the MJA update, especially battery life. I am hoping MK2 will fix everything. Also, I have a Mac and not a PC.
Click to expand...
Click to collapse
Sounds like there is a whole lot going on with your phone setup with so many inconsistancies.
If the Modem(baseband) is MDC - which it woul probably have had to be to do the SIM unlock stuff, and your build is MJA but your software version is MDC you've got a lot of stuff to look at.
How did the tech flash your phone? PC Odin? or via a zip/recovery. If it was flashed via a custom recovery (meaning you have one on your phone) then the OTA will fail/error. Same thing with a custom kernel - failure of OTA. Stock boot/kernels are required for OTAs to work.
The latest update is actually MK2 and not MJA by the way.
You can flash a .tar using Heimdal. Sammobile has the full MK2 one here.
BUT you'll probably need to do some fancy stuff with you APNs to get it to work on your current network - time to see tech who helped you again.
leaderbuilder said:
Sounds like there is a whole lot going on with your phone setup with so many inconsistancies.
If the Modem(baseband) is MDC - which it woul probably have had to be to do the SIM unlock stuff, and your build is MJA but your software version is MDC you've got a lot of stuff to look at.
How did the tech flash your phone? PC Odin? or via a zip/recovery. If it was flashed via a custom recovery (meaning you have one on your phone) then the OTA will fail/error. Same thing with a custom kernel - failure of OTA. Stock boot/kernels are required for OTAs to work.
The latest update is actually MK2 and not MJA by the way.
You can flash a .tar file using Heimdal. Sammobile has the full MK2 one here.
BUT you'll probably need to do some fancy stuff with you APNs to get it to work on your current network - time to see tech who helped you again.
Click to expand...
Click to collapse
Thanks for replying so quickly! I am very new to all of this stuff. If I flash the .tar file will that fix everything? Do I need to root my phone to flash the .tar file? Also, will my SIM remain unlocked or will it relock?
As for the APN, I think I already know all of the necessary info to input because when the tech unlocked the SIM he didn't input the APN info.
BY the way I know MK2 is the latest build and that is why I am trying to update from MJA to MK2. I'm sorry if I didn't make that clear in the OP.
Sorry, I also forgot to mention that I don't know if the technician flashed it with Odin or a zip/recovery because I left my phone there for a few hours. Is there a way to check?
newyorkcfc said:
Sorry, I also forgot to mention that I don't know if the technician flashed it with Odin or a zip/recovery because I left my phone there for a few hours. Is there a way to check?
Click to expand...
Click to collapse
See if you have a custom recovery.
Boot to recovery - Power off. Then Power on+Volume Up+Home button and see if something like CWM, TWRP or Philz recovery loads.
If it is just Spring/Samsung recovery then he flashed the modem via Odin and not a custom recovery. Either way just power off to boot again.
leaderbuilder said:
See if you have a custom recovery.
Boot to recovery - Power off. Then Power on+Volume Up+Home button and see if something like CWM, TWRP or Philz recovery loads.
If it is just Spring/Samsung recovery then he flashed the modem via Odin and not a custom recovery. Either way just power off to boot again.
Click to expand...
Click to collapse
It is the stock Samsung recovery. I guess he used Odin.
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?
I have two ATT I337's and wanted to root them both. The first and newest one worked fine but it has a busted screen and is locked. It was my test run and went very well except for the wifi problem that many others had trying to load towelroot from the net. Btw, it would be helpful to all going forward if someone would edit those instructions to download say towelroot first!!! I found a solution that I will post later.
Unfortunately my second and primary phone failed early in the process. After I loaded NC1_Stock, it would only boot to either the Recovery menu or the Odin menu. I have tried loading NC1 again, tried NJ4, tried safe mode (will not load), pulling the batt, factory wipe (ouch) and then tried emergency recovery in Kies. NOTHING is working. I did notice that the sticker in this I337 has NO serial number! So with Kies I used the serial from my broken one, on the second one. Unlike my other one which has a serial number on the sticker. So I am not sure if this is an older model, a refurb or what.
I must admit that I did NOT check the original firmware version when I started this process.
In any case I am looking for ANY options to get my i337 working again. Are there any other firmware versions to try? (link pls) Anyone? A phone that only goes into recovery or Odin mode is not much fun!
Honestly, I'm not sure what you did with the two phones with IMEI and stuff lol.
You have to back to NB1 firmware and work from there. Follow this guide until 3rd section on whichever phone you can Odin.
Make sure to completely close or remove Kies software. It's known to cause problems with Odin.
xymic said:
Honestly, I'm not sure what you did with the two phones with IMEI and stuff lol.
You have to back to NB1 firmware and work from there. Follow this guide until 3rd section on whichever phone you can Odin.
Make sure to completely close or remove Kies software. It's known to cause problems with Odin.
Click to expand...
Click to collapse
I have gone back to NB1 multiple times(see orig post) and I get the same result. How do I disable Kies if I can only get to recovery or Odin menus? No matter what I do, I can only get to those two menus.
avgjoeuser said:
I have gone back to NB1 multiple times(see orig post) and I get the same result. How do I disable Kies if I can only get to recovery or Odin menus? No matter what I do, I can only get to those two menus.
Click to expand...
Click to collapse
I don't see any mention of NB1 in your original post. If you use the guide I linked to, you don't need to do anything with NC1. You flash NB1 and go straight to OC3.
Just to be sure, you're using this Odin (3.09), right? Because that's the one you need. By disabling Kies, I mean just close the program or remove it from your computer. Both Kies and Odin are independent so you don't need Kies to use Odin and vice versa.
OC3
Apologies. I did not notice that you were saying NB1 instead of NC1. I was able to recover by loading NB1. Thanks! I am using odin 309.
I did try going to NJ4 after recovery, but I lose wifi. Where do I get OC3???
xymic said:
I don't see any mention of NB1 in your original post. If you use the guide I linked to, you don't need to do anything with NC1. You flash NB1 and go straight to OC3.
Just to be sure, you're using Odin (3.09), right? Because that's the one you need. By disabling Kies, I mean just close the program or remove it from your computer. Both Kies and Odin are independent so you don't need Kies to use Odin and vice versa.
Click to expand...
Click to collapse
Apologies. I did not notice that you were saying NB1 instead of NC1. I was able to recover by loading NB1. Thanks! I am using odin 309.
I did try going to NJ4 after recovery, but I lose wifi. Where do I get OC3???[/QUOTE]
Found it in the link from your first post. After reading through the process I am not sure I really want to go to OC3. Any issue with staying on NB1? Is there a more stable 4.x.x release that I should go to?
avgjoeuser said:
Found it in the link from your first post. After reading through the process I am not sure I really want to go to OC3. Any issue with staying on NB1? Is there a more stable 4.x.x release that I should go to?
Click to expand...
Click to collapse
OC3 is newest Android version 5.0 (Lollipop). Some people say it eats more battery, but I don't feel any difference. To me, it feel more smoother, faster, and much more fluid. Even my father, who is not tech savvy at all, told me it was faster than before. It's as stable as any 4.x.x. I'd say the update is worth it.
The guide feels longer than it actually takes. You only need to follow sections 1-3 if you want OC3 update. Actually only Section 2 Section 3 since you already have NB1 working. Section 4 is optional. You'll be done within 10 minute max. :good:
xymic said:
OC3 is newest Android version 5.0 (Lollipop). Some people say it eats more battery, but I don't feel any difference. To me, it feel more smoother, faster, and much more fluid. Even my father, who is not tech savvy at all, told me it was faster than before. It's as stable as any 4.x.x. I'd say the update is worth it.
The guide feels longer than it actually takes. You only need to follow sections 1-3 if you want OC3 update. Actually only Section 2 since you already have NB1 working. Section 4 is optional. You'll be done within 10 minute max. :good:
Click to expand...
Click to collapse
You did mean section 3 right? "Upgrading to ROOTED STOCK OC3 (Lollipop) using "keep root" method". Maybe I will give it a try. The download took a while and I still need to go the whole G+ thing.
avgjoeuser said:
You did mean section 3 right? "Upgrading to ROOTED STOCK OC3 (Lollipop) using "keep root" method". Maybe I will give it a try. The download took a while and I still need to go the whole G+ thing.
Click to expand...
Click to collapse
Yep, I meant Section 3 Root your NB1 if it's not already.
You can avoid G+ thing and download the Flashfire APK directly from here.
My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
StephenTiz said:
My s4 was rooted about a year ago with the logo SAMSUNG and Unlocked with an open lock below it when it boots up. I gave this phone to my girlfriends daughter and forgot to tell her not to try and update it. I don't remember the way i rooted it or what software it had on it at the time.
So when I go to recovery after it loads into an AT&T logo and tries to install it and it gets to 24%. After this it bootloops. Any help would be appreciated. My phone model is SGH-I337 , also not sure of what the original firmware is.
Click to expand...
Click to collapse
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
No recovery options
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
No recovery options
sway8966 said:
Open lock symbol means your phone is rooted not unlocked.
If you could go to the recovery mode (voloume-up+home+power) it would tell you your firmware version. You could try clear cache, factory reset in recovery mode. If it still gives you the bootloop, you might need to flash the firmware via odin.
You can find instructions and necessary files in here and here.
Click to expand...
Click to collapse
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
StephenTiz said:
Sorry I left that part out. When it goes to recovery i get the blue text that say recovery then it goes straight to the AT&T installing. So no recovery options. I can still get to the Odin dowloading screen though and it says im running Samsung Original software
Click to expand...
Click to collapse
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Woop Woop!
sway8966 said:
One reason I asked you to go to the recovery option was to know what version of firmware you were on before .
Do you remember you were on jelly bean or kick-kat or lollipop? If you do you can find the firmware for jelly bean and kit-kat on the links I mentioned in the previous message.
If you could not recall your firmware, the latest odin flashable firmware we have is kit-kat NB1.
You can flash that one to revive your phone. Then use twoel root to root the phone. After that you can go to lollipop if you want. All the instructions are there.
Click to expand...
Click to collapse
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
StephenTiz said:
It worked. I have tried so many different firmware and kit-kat NB1 worked perfectly. Thank you so much, my girlfriends daughter will be so happy. I think i will leave it unrooted for now. I hope this post helps someone else in the future.
Click to expand...
Click to collapse
I am glad that it works out for you.
Rooting is so easy from that point. Just get towel root and root it. The link also included in my previous post. After the root you might need to disable the AT&T OTA update too. The instructions are also in that post too.