I have a Sprint variant of the S4 and I want to unroot it. But I used Triangle Away and it's not resetting the binary count. TA is says that "Status cannot be determined..."
Why do all the tutorials say that this will work on the Sprint S4 when TA reboots the device, it says "Could not find triangle and counter date..."
What the heck is going on????
heyjoojoo said:
I have a Sprint variant of the S4 and I want to unroot it. But I used Triangle Away and it's not resetting the binary count. TA is says that "Status cannot be determined..."
Why do all the tutorials say that this will work on the Sprint S4 when TA reboots the device, it says "Could not find triangle and counter date..."
What the heck is going on????
Click to expand...
Click to collapse
You're probably on MF9. I believe Triangle Away only works for MDL and earlier.
Sent from my SPH-L720 using XDA Premium 4 mobile app
heyjoojoo said:
I have a Sprint variant of the S4 and I want to unroot it. But I used Triangle Away and it's not resetting the binary count. TA is says that "Status cannot be determined..."
Why do all the tutorials say that this will work on the Sprint S4 when TA reboots the device, it says "Could not find triangle and counter date..."
What the heck is going on????
Click to expand...
Click to collapse
You have to be on MDL or MDC for triangle away to work. You also need the stock kernel and recovery installed to reset everything.
This message brought to you in part by Sprint and the letters GS and the number 4
So am I stuck? or is there a way to reset my binary count?
I keep trying to flash the current kernel (MF9) with a MDL but after rebooting, the device still shows MF9.
GiantJay said:
You have to be on MDL or MDC for triangle away to work. You also need the stock kernel and recovery installed to reset everything.
This message brought to you in part by Sprint and the letters GS and the number 4
Click to expand...
Click to collapse
I keep trying to flash the rom with MDL roms but they're not sticking. I've tried several MDL ROMs. I also tried flashing just the kernel via Odin and no change in the MF9.
heyjoojoo said:
I keep trying to flash the rom with MDL roms but they're not sticking. I've tried several MDL ROMs. I also tried flashing just the kernel via Odin and no change in the MF9.
Click to expand...
Click to collapse
I have a thread on this in q and a. Good luck is all I can say. Last time I tried to get rid of mf9 I couldn't figure it out.
This message brought to you in part by Sprint and the letters GS and the number 4
GiantJay said:
I have a thread on this in q and a. Good luck is all I can say. Last time I tried to get rid of mf9 I couldn't figure it out.
This message brought to you in part by Sprint and the letters GS and the number 4
Click to expand...
Click to collapse
The problem is that I'm trying to reset the binary counter. All these youtube videos and tutorials indicate that it can be done. But I have had no success thus far. And it seems that the MF9 update is the culprit.
heyjoojoo said:
The problem is that I'm trying to reset the binary counter. All these youtube videos and tutorials indicate that it can be done. But I have had no success thus far. And it seems that the MF9 update is the culprit.
Click to expand...
Click to collapse
Here's how I did it the other day. I was going from rooted MDL (stock rom with some tweaks) to MF9. So I had to get back to unrooted MDL first. I followed the "Reverting to Unmodified Stock MDL to update to Stock MF9" section of this thread to do it:
http://forum.xda-developers.com/showthread.php?t=2277480
I did a factory reset first. ODIN'd the MDL tar in that section. That did not set me all the way back to official on the download screen, though. I ran Triangle Away at that point, but it made no difference. So I did another factory reset and that did the trick. I was all back to official and unrooted.
I then installed MF9 using the very next section of the above thread. It was also showing official in the download screen.
jejb said:
Here's how I did it the other day. I was going from rooted MDL (stock rom with some tweaks) to MF9. So I had to get back to unrooted MDL first. I followed the "Reverting to Unmodified Stock MDL to update to Stock MF9" section of this thread to do it:
http://forum.xda-developers.com/showthread.php?t=2277480
I did a factory reset first. ODIN'd the MDL tar in that section. That did not set me all the way back to official on the download screen, though. I ran Triangle Away at that point, but it made no difference. So I did another factory reset and that did the trick. I was all back to official and unrooted.
I then installed MF9 using the very next section of the above thread. It was also showing official in the download screen.
Click to expand...
Click to collapse
So, I should unroot back to MDL stock (but not the MF9 stock). Then root with a MDL or MDC based ROM. Run Triangle Away but do a Factory reset?
heyjoojoo said:
So, I should unroot back to MDL stock (but not the MF9 stock). Then root with a MDL or MDC based ROM. Run Triangle Away but do a Factory reset?
Click to expand...
Click to collapse
No, follow the directions to get back to MDL unrooted, stock rom. Do not root it once there. You may have to do a couple of factory resets for the binaries to get reset so that it's all "official" on the Download screen. Once you get to that point - all official - then take the OTA to go to MF9. That will give you stock rom, unrooted, all official MF9.
From there you can root or not, up to you. I did. But my download screen says custom again of course, now that I've rooted my MF9.
The issue that I had was getting rid of the mf9 software and baseband. Whenever I flashed mdl the mf9 software and baseband would still be there. I gave up but I need to unroot still and get back to all stock with no custom binary too. I think I might try today again.
This message brought to you in part by Sprint and the letters GS and the number 4
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
Here's the thread I created a while ago. http://forum.xda-developers.com/showthread.php?t=2382188
This message brought to you in part by Sprint and the letters GS and the number 4
jejb said:
No, follow the directions to get back to MDL unrooted, stock rom. Do not root it once there. You may have to do a couple of factory resets for the binaries to get reset so that it's all "official" on the Download screen. Once you get to that point - all official - then take the OTA to go to MF9. That will give you stock rom, unrooted, all official MF9.
From there you can root or not, up to you. I did. But my download screen says custom again of course, now that I've rooted my MF9.
Click to expand...
Click to collapse
Success!!!! Thank you so much for your help!!!!
Product Name: SPH-L720
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Glad it worked for you. Remember to hit the "Thanks" button, if you would be so kind.
jejb said:
Glad it worked for you. Remember to hit the "Thanks" button, if you would be so kind.
Click to expand...
Click to collapse
Lol. I don't think 99% of the people on this website even know that there is a thanks button, or don't know how to use it. Gave up a long time ago on that one.
This message brought to you in part by Sprint and the letters GS and the number 4
I think MF9 locks the baseband in odin when you trip the counter. I found the easiest way to downgrade was to odin MDL or MDC and then let it boot up. It will show as baseband of MF9 still. Go back into odin one more time and load the same version as the first time. The second time will change the baseband because the bootloader is using the MDL or MDC version and not the MF9 version so the second time everything will change and when you re-boot you won't see MF9 anymore. At least this works for me. Hope it helps someone else.
Related
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.
hello, so, ive had the s4 (att) for a while and i have a small problem, i rooted it (and confirmed the root with rootchecker) and at some point decided to try to install a custom mod on it. issue is i am on MF3 and read of all the dangers and kinda stopped. but i stopped after attempting to get CWM on the phone using rom manager (from teh google play store) now when all this happened it was months ago and i had just started on android exploits and the dangers scared me off, i used a jailbroken and unlocked iphone before.
needless to say currently i want to get cyanogenmod on the phone. its rooted, but im not sure what to do next. ive been reading materials for about 2 days now. threads keep contradicting eachother some say use loki and odin others say you cant because its gonna brick mf3.
looking for a quick answer on what exactly i need to get a custom rom installed. the guides here are great but again most say mf3 will be bricked while others say otherwise.
also currently the phone randomly displays a "custom" boot screen right after bootup. sometime it does sometime it doesnt. im guessing from teh CWM. but not sure.
help.
vampirekid13 said:
hello, so, ive had the s4 (att) for a while and i have a small problem, i rooted it (and confirmed the root with rootchecker) and at some point decided to try to install a custom mod on it. issue is i am on MF3 and read of all the dangers and kinda stopped. but i stopped after attempting to get CWM on the phone using rom manager (from teh google play store) now when all this happened it was months ago and i had just started on android exploits and the dangers scared me off, i used a jailbroken and unlocked iphone before.
needless to say currently i want to get cyanogenmod on the phone. its rooted, but im not sure what to do next. ive been reading materials for about 2 days now. threads keep contradicting eachother some say use loki and odin others say you cant because its gonna brick mf3.
looking for a quick answer on what exactly i need to get a custom rom installed. the guides here are great but again most say mf3 will be bricked while others say otherwise.
also currently the phone randomly displays a "custom" boot screen right after bootup. sometime it does sometime it doesnt. im guessing from teh CWM. but not sure.help.
Click to expand...
Click to collapse
I read this and i'm not sure in what stage you are? What firmware you are on ( asume stock rooted MF3). Did you phone bootup all the way or not? All i can help is just start fresh from here: http://forum.xda-developers.com/showthread.php?t=2502003 if you on MF3. If you not on MDL just go to sammobile find firmware and flash with odin.
After you back to stock firmware root you phone (look for correct metod on firmware you have) install SafeStrip for MF3 or CMW for MDL ( do not install CMW if you on MF3) SafeStrip post here http://forum.xda-developers.com/showthread.php?t=2448925 and more info here :http://forum.xda-developers.com/showthread.php?t=2428254. But first of all READ, READ, READ : http://forum.xda-developers.com/showthread.php?t=2314494
norbarb said:
I read this and i'm not sure in what stage you are? What firmware you are on ( asume stock rooted MF3). Did you phone bootup all the way or not? All i can help is just start fresh from here: http://forum.xda-developers.com/showthread.php?t=2502003 if you on MF3. If you not on MDL just go to sammobile find firmware and flash with odin.
After you back to stock firmware root you phone (look for correct metod on firmware you have) install SafeStrip for MF3 or CMW for MDL ( do not install CMW if you on MF3) SafeStrip post here http://forum.xda-developers.com/showthread.php?t=2448925 and more info here :http://forum.xda-developers.com/showthread.php?t=2428254. But first of all READ, READ, READ : http://forum.xda-developers.com/showthread.php?t=2314494
Click to expand...
Click to collapse
well the short version is this
bought phone (it auto updated to mf3)
rooted phone while on mf3
installed rom manager off the play store, which installed CWM.
i uninstalled rom manager but im more than sure that CWM stayed.
currently i want to start over, hopefully flash the phone back to stock and re-root it and try again using a better method (like safestrap)
so all i have to do is get odin + mf3 pda/csc/phone/modem files and flash the phone right? then its gonna be back to stock rom. so i will have to reroot it and try again...
will this also reset the flash counter?
So from what I read, you're not in a great position. MF3 CANNOT have a custom recovery, sure you can install one like you did but it won't work. That being said what you mentioned should work, flashing MF3 via ODIN. After that, root it and install SafeStrap, it's the only option for MF3 (currently no options for the latest firmware AFAIK).
Link to Odin thread:
http://forum.xda-developers.com/showthread.php?t=2504311
read the entirety of it, it's only 5 pages long.
http://forum.xda-developers.com/showthread.php?t=2314494
Read post 2 thoroughly, it has lots of good information. IGNORE THE FIRST POST, it doesn't apply to your phone
Lastly if you don't want the phone to update itself, what I did was install Titanium backup and froze the following apps:
1. AT&T Software update Vxx_x_xxxx_x_x
2. FWUpgrade x.x.x
3. LocalFOTA vx_xxxx_x_x
as for the flash counter, I'm not sure. I hope this helps a little.
What i would suggest is to odin bak to UCUAMDL and then use casual to root back.
Then you will have TWRP recovery and can flash any rom (loki'd) , Also keep in mind never do a data format using twrp.
s4shyam95 said:
What i would suggest is to odin bak to UCUAMDL and then use casual to root back.
Then you will have TWRP recovery and can flash any rom (loki'd) , Also keep in mind never do a data format using twrp.
Click to expand...
Click to collapse
He's on mf3, how's he going to do that?
Sent from my Nexus 5 using xda app-developers app
jd1639 said:
He's on mf3, how's he going to do that?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Cant one odin back to mdl from mf3 ?
s4shyam95 said:
Cant one odin back to mdl from mf3 ?
Click to expand...
Click to collapse
No, a qfuse is blown. No way to go backwards.
Sent from my Nexus 5 using xda app-developers app
s4shyam95 said:
Cant one odin back to mdl from mf3 ?
Click to expand...
Click to collapse
Even if you update to last leak (MJ6) or official (MJ9) you can not return back to MF3
---------- Post added at 02:32 PM ---------- Previous post was at 02:30 PM ----------
vampirekid13 said:
well the short version is this
bought phone (it auto updated to mf3)
rooted phone while on mf3
installed rom manager off the play store, which installed CWM.
i uninstalled rom manager but im more than sure that CWM stayed.
currently i want to start over, hopefully flash the phone back to stock and re-root it and try again using a better method (like safestrap)
so all i have to do is get odin + mf3 pda/csc/phone/modem files and flash the phone right? then its gonna be back to stock rom. so i will have to reroot it and try again...
will this also reset the flash counter?
Click to expand...
Click to collapse
Yes flash with odin back to MF3 root install triangle away if you want to reset flash counter then reset.
Good luck.
norbarb said:
Even if you update to last leak (MJ6) or official (MJ9) you can not return back to MF3
---------- Post added at 02:32 PM ---------- Previous post was at 02:30 PM ----------
Yes flash with odin back to MF3 root install triangle away if you want to reset flash counter then reset.
Good luck.
Click to expand...
Click to collapse
umm for the mf3 sgh-i337 i need odin3 v185 right?
thats what i read someplace but i forgot where.
vampirekid13 said:
umm for the mf3 sgh-i337 i need odin3 v185 right?
thats what i read someplace but i forgot where.
Click to expand...
Click to collapse
This one i post in attachment
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.
Okay, so long story short AT&T has cockblocked me from recovering my phone. I know, it has a locked bootloader. I get that. But let me start from the beginning. I was rooted (4.3), and my phone auto updated to KK, and essentially soft-bricked my phone. Well, I had to flash my 4.3 firmware (or so I thought) back onto my phone through Odin. The firmware turned out to be 4.2.2, and all of it failed to flash except the modem. It still started up fine, but I couldn't connect to wifi. It wasn't even an option to turn it on. Turns out I was still on 4.3, with a baseband of MF3, and a build number ending in MK2. I didn't know how to fix this, so I've kinda flashed it with all sorts of things hoping it would help. I've tried all variations of 4.2.2 seeing if I can get things to be all either MF3 or MK2, so far no luck. Well today I tried to flash it with MK2 firmware, and it went like 95% through, and failed. Restarted, and it says "System software not authorized by AT&T has been found on your phone."
This is because of the bootloader, I get it.
The 4.2.2 modem is the only thing to successfully flash. Any clues why? Any clues onto how to recover my phone at all? You guys are true geniuses, please help.
Also, my device status is still on "custom" with the unlocked icon.
Any help would be tremendous, as I feel like a complete and utter moron. I have both Windows 7 & Linux Mint my use, so suggest anything. Please. I'm begging you.
I had the same problem i soft bricked my phone by installing MF3 and i was already on MK2. Just download MK2 http://forum.xda-developers.com/showthread.php?t=2621279 flash first only AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 by using PDA on oDin see if that fixes your problem.
jeff7790 said:
I had the same problem i soft bricked my phone by installing MF3 and i was already on MK2. Just download MK2 http://forum.xda-developers.com/showthread.php?t=2621279 flash first only AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 by using PDA on oDin see if that fixes your problem.
Click to expand...
Click to collapse
Do you know of a good repository or place were i can download basebands updates (Modem.bin) for my i337?
If i upload a phone baseband i337 with a i337m, would it work?
Never mind found the solution in the forum. Thx
Sent from my GT-I9505G using xda app-developers app
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?