I just purchased a new AT&T Galaxy S4 via Amazon. Came with MDB software installed. I used the CASUAL root procedure and was successful. That left me with rooted MDB + TWRP recovery.
I am intending to stay with a stock ROM, not a complete custom ROM.
My question is: Should I try to update to a newer version of software? I believe right now I am two releases behind (MDB -> MDL -> MF3?)
I haven't been able to find much talking about the MDL version, so I don't know if there is anything useful in it (perhaps radio updates?). I did see some references to a performance enhancement which is always good.
I'm assuming I want to stay away from MF3 as there seems to be a lot of rapidly changing/conflicting information at this point about if and how one can get to that release (and keep root).
If I wanted to go to the MDL version, how would I go about it? I found two threads here:
http://forum.xda-developers.com/showthread.php?t=2348859&highlight=mdl
http://forum.xda-developers.com/showthread.php?t=2307157&highlight=mdl
Preferably, this would be done just as an update instead of wiping what I have now. But neither of those threads indicate if a wipe is necessary or if they can simply be installed on top of the stock MDB.
Appreciate any feedback!
cabadam said:
I just purchased a new AT&T Galaxy S4 via Amazon. Came with MDB software installed. I used the CASUAL root procedure and was successful. That left me with rooted MDB + TWRP recovery.
I am intending to stay with a stock ROM, not a complete custom ROM.
My question is: Should I try to update to a newer version of software? I believe right now I am two releases behind (MDB -> MDL -> MF3?)
I haven't been able to find much talking about the MDL version, so I don't know if there is anything useful in it (perhaps radio updates?). I did see some references to a performance enhancement which is always good.
I'm assuming I want to stay away from MF3 as there seems to be a lot of rapidly changing/conflicting information at this point about if and how one can get to that release (and keep root).
If I wanted to go to the MDL version, how would I go about it? I found two threads here:
http://forum.xda-developers.com/showthread.php?t=2348859&highlight=mdl
http://forum.xda-developers.com/showthread.php?t=2307157&highlight=mdl
Preferably, this would be done just as an update instead of wiping what I have now. But neither of those threads indicate if a wipe is necessary or if they can simply be installed on top of the stock MDB.
Appreciate any feedback!
Click to expand...
Click to collapse
You cannot OTA update to MF3 without ODINing back to stock - your custom recovery will prevent the update from working.
If you want to update to MDL, you can ODIN the stock MDL package and redo the CASUAL script.
I would suggest you stay on MDL until MF3 has not only root, but also custom recovery. At this point it's still too early to take the risk, even with a root access exploit now available.
If you want the updates, there are several ROMs available that incorporate updates...there's one that is almost completely stock MF3 without the bootloader (which is the main problem with it)...there's multiple based off of stock MF3 with some optimizations...and even some based on the latest Galaxy S4 International firmware which is several updates ahead of MF3.
Of course all that requires your willingness to install a custom ROM.
+1
I think you confirmed most of what I gathered - thanks for the clarifications.
jeffreii said:
If you want to update to MDL, you can ODIN the stock MDL package and redo the CASUAL script.
Click to expand...
Click to collapse
I did this, and it didn't do quite what I expected (although maybe it is better than I expected). I downloaded the MDL firmware from:
http://galaxys4root.com/galaxy-s4-stock-firmware/
AT&T Galaxy S4 SGH-I337 UCUAMDL (Android 4.2.2)
After flashing it with Odin, and my phone rebooted, I was surprised to note that it didn't actually WIPE my device. Everything was still in place, except now the device reports that it is in fact updated to MDL.
Is that right? I was expecting it to basically be in factory-new state after flashing.
cabadam said:
I think you confirmed most of what I gathered - thanks for the clarifications.
I did this, and it didn't do quite what I expected (although maybe it is better than I expected). I downloaded the MDL firmware from:
http://galaxys4root.com/galaxy-s4-stock-firmware/
AT&T Galaxy S4 SGH-I337 UCUAMDL (Android 4.2.2)
After flashing it with Odin, and my phone rebooted, I was surprised to note that it didn't actually WIPE my device. Everything was still in place, except now the device reports that it is in fact updated to MDL.
Is that right? I was expecting it to basically be in factory-new state after flashing.
Click to expand...
Click to collapse
Yes that's normal. It doesn't wipe your internal or external sd card. The parts you store info on
jd1639 said:
Yes that's normal. It doesn't wipe your internal or external sd card. The parts you store info on
Click to expand...
Click to collapse
Too easy, that basically gave me exactly what I wanted. I think I'm squared away until MF3 settles down.
Thanks for your time!
cabadam said:
Too easy, that basically gave me exactly what I wanted. I think I'm squared away until MF3 settles down.
Thanks for your time!
Click to expand...
Click to collapse
When you ODIN an upgrade to the same firmware, you don't get a wipe. It's nice to keep your settings in those situations!
Now just make sure you root/recovery so you can avoid the OTA...otherwise make sure you freeze the OTA apps.
jeffreii said:
When you ODIN an upgrade to the same firmware, you don't get a wipe. It's nice to keep your settings in those situations!
Now just make sure you root/recovery so you can avoid the OTA...otherwise make sure you freeze the OTA apps.
Click to expand...
Click to collapse
Haha yeah, I had spent some time backing up some settings via TB, nice to know I don't have to deal with that (at least for now )
Already re-applied the CASUAL root process. I froze the "AT&T Software Update" app. Is there anything other than that?
cabadam said:
Haha yeah, I had spent some time backing up some settings via TB, nice to know I don't have to deal with that (at least for now )
Already re-applied the CASUAL root process. I froze the "AT&T Software Update" app. Is there anything other than that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44022554&postcount=74
Hmm, so I went and also froze LocalFOTA, but I dont have anything called FW Upgrade
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Good post.
I'm also on MDB. Do you think it's actually worth it to install the MDL update?
I'm currently running Kangabean with 4.3, if it matters.
Do not update ota may bypass mdl and go to mf3
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
deron37129 said:
Do not update ota may bypass mdl and go to mf3
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nope. Would flash the MDL through Odin and immediately run Motochopper. Just trying to figure out if it's even worth it.
trunzoc said:
Nope. Would flash the MDL through Odin and immediately run Motochopper. Just trying to figure out if it's even worth it.
Click to expand...
Click to collapse
Definitely worth it. MDL irons out the issued that the S4 had upon release.
Sent from my SGH-I337 using Tapatalk 4
sd_N said:
Definitely worth it. MDL irons out the issued that the S4 had upon release.
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Thanks!.
Here goes nothing
***EDIT***
Flashed the MDL image. I pulled the SIM to avoid any kind of OTA crap and booted. Got stuck at the AT&T logo though.
I had to go into stock recovery and do a factory reset. Did that and it booted up. Ran Motochopper fine and was able to boot into TWRP.
I restored by backup, but wouldn't boot past the Samsung Logo. Did another factory reset, but still wouldn't boot. Restored a backup I had of rooted stock. That worked.
Reset again and reinstalled Kangabean from scratch. That worked. Went back to recovery again and just restored my data partition. that worked too. yay
Pain in the arse, but let's see if MDL has any noticeable differences.
Thank you ALL!! I am also on MDB firmware and was wondering about all of this.
I do have some questions if you don't mind. (sorry for the thread hijack)
On MDB firmware, can you install a stock modded rom w/o updating the firmware?(such as MDOB and Goldeneye)
Is the MDB modem compatible with these roms or will I have to flash to a newer firmware to use them?
Knowing its working perfectly now, I'd like to stick with my current setup, but Id like the ability to use a stock modded TW rom, as I have a Samsung smart TV and use most of the Samsung bloatware.
Is there really any reason to go to MDL over MDB?
custommx3 said:
Thank you ALL!! I am also on MDB firmware and was wondering about all of this.
I do have some questions if you don't mind. (sorry for the thread hijack)
On MDB firmware, can you install a stock modded rom w/o updating the firmware?(such as MDOB and Goldeneye)
Is the MDB modem compatible with these roms or will I have to flash to a newer firmware to use them?
Knowing its working perfectly now, I'd like to stick with my current setup, but Id like the ability to use a stock modded TW rom, as I have a Samsung smart TV and use most of the Samsung bloatware.
Is there really any reason to go to MDL over MDB?
Click to expand...
Click to collapse
Check the roms you want to use. Most of them require mdl firmware.
Related
I rooted my AT&T Galaxy S4 i337 a while back using Motochopper and it worked absolutely fine. After installing Cyanogenmod, I decided to go back to stock. I used triangle away and Odin to return myself back to stock, however, I always had issues. When I would recovery boot, I got an error and I couldn't wipe my cache partition. I tried to re-root my phone today using Motochopper and then Odin, but neither of them worked. I got a fail on both of them. Motochopper installed Supersu on my device, but didn't actually give me root access, and Odin just gave me a fail. Now, my phone is working with stock, but I still get errors in recovery mode and I can't root. Can someone please help!?
What is your baseband and build number on settings, more, about phone?
jd1639 said:
What is your baseband and build number on settings, more, about phone?
Click to expand...
Click to collapse
Baseband - I337UCUAMF3
Build Number - JDQ39.I337UCUAMF3
I
cfoughty7 said:
Baseband - I337UCUAMF3
Build Number - JDQ39.I337UCUAMF3
Click to expand...
Click to collapse
That's what i was afraid of. With mf3 you can't root with motorchopper or flash roms like you could on mdl. You also can't put on a custom recovery. Give me a second and I'll give you some links.
http://forum.xda-developers.com/showthread.php?p=44165374
http://forum.xda-developers.com/showthread.php?p=42478710
http://forum.xda-developers.com/showthread.php?p=45186518
http://forum.xda-developers.com/showthread.php?p=45971194
Read these before you do anything else and get familiar with them.
cfoughty7 said:
Baseband - I337UCUAMF3
Build Number - JDQ39.I337UCUAMF3
Click to expand...
Click to collapse
MF3 has a completely different root and recovery method now. Search the threads and you'll find them. Unfortunately it's pretty risky as you won't be able to flash back to stock using ODIN on MF3.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
jd1639 said:
I
That's what i was afraid of. With mf3 you can't root with motorchopper or flash roms like you could on mdl. You also can't put on a custom recovery. Give me a second and I'll give you some links.
http://forum.xda-developers.com/showthread.php?p=44165374
http://forum.xda-developers.com/showthread.php?p=42478710
http://forum.xda-developers.com/showthread.php?p=45186518
http://forum.xda-developers.com/showthread.php?p=45971194
Read these before you do anything else and get familiar with them.
Click to expand...
Click to collapse
I'm just confused as to why I was able to do it perfectly before?
cfoughty7 said:
I'm just confused as to why I was able to do it perfectly before?
Click to expand...
Click to collapse
Because you were on mdl firmware. After you Odin'd it had to have taken the ota update to mf3.
shall plyinuf
jd1639 said:
Because you were on mdl firmware. After you Odin'd it had to have taken the ota update to mf3.
Click to expand...
Click to collapse
Ohhh, ok. I understand! There's no way to get it back? Is that what I should read those links for?
cfoughty7 said:
Ohhh, ok. I understand! There's no way to get it back? Is that what I should read those links for?
Click to expand...
Click to collapse
Ok, so I read the links. Now, I'm not so much interested in rooting as I am getting my phone straight. Is there any way to get back to mdl? Will the rumored 4.3 update this month fix that? When I tried to update or recover with Samsung Kies, it said my phone wasn't compatible to recover. Does that mean I won't be able to get the update?
jd1639 said:
Because you were on mdl firmware. After you Odin'd it had to have taken the ota update to mf3.
Click to expand...
Click to collapse
Ok, so I read the links. Now, I'm not so much interested in rooting as I am getting my phone straight. Is there any way to get back to mdl? Will the rumored 4.3 update this month fix that? When I tried to update or recover with Samsung Kies, it said my phone wasn't compatible to recover. Does that mean I won't be able to get the update?
cfoughty7 said:
Ok, so I read the links. Now, I'm not so much interested in rooting as I am getting my phone straight. Is there any way to get back to mdl? Will the rumored 4.3 update this month fix that? When I tried to update or recover with Samsung Kies, it said my phone wasn't compatible to recover. Does that mean I won't be able to get the update?
Click to expand...
Click to collapse
First, there is no way to go back to mdl. Idk if you'll be able to get the 4.3 update but I would assume so since you are on the stick firmware now. But, each new update is going to make it harder to root your phone or run custom roms. So you probably need to choose whether you want to keep your phone stock and take updates if and when they come out. Or have some snooty to run custom roms and root your device and put safestrap on.
jd1639 said:
First, there is no way to go back to mdl. Idk if you'll be able to get the 4.3 update but I would assume so since you are on the stick firmware now. But, each new update is going to make it harder to root your phone or run custom roms. So you probably need to choose whether you want to keep your phone stock and take updates if and when they come out. Or have some snooty to run custom roms and root your device and put safestrap on.
Click to expand...
Click to collapse
I'm going to stay with stock. Will the mdl thing effect anything if I have an issue with warranty sterf?
Shouldn't, your stock mf3 right now.
Newbie here. I rooted the S4 a couple of months ago. Now that 4.3 is out, can experts post some step-by-step guide on how to upgrade it on rooted devices? Thanks.
Are you sure you want to update? Why not just flash a 4.3.1 rom to your device instead and stock to AMDL firmware.
However if it hasn't manually updated to MF3 you can go into your settings and search for updates, or it should automatically update on it's own. The only thing that would prevent it would be if you've flashed a non TW based ROM, changed the framework + kernel, or froze there processes needed to update. Just a stand alone root won't prevent it.
Sent from my SGH-I337 using XDA Premium 4 mobile app
I am not on MF3. I tried to install the AT&T minor update before, but it failed twice. I did freeze some stock apps. If I unfreeze those apps, the automatic update should work then? That's very good to know. Thanks!
Br4nd3n said:
Are you sure you want to update? Why not just flash a 4.3.1 rom to your device instead and stock to AMDL firmware.
However if it hasn't manually updated to MF3 you can go into your settings and search for updates, or it should automatically update on it's own. The only thing that would prevent it would be if you've flashed a non TW based ROM, changed the framework + kernel, or froze there processes needed to update. Just a stand alone root won't prevent it.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just to be clear you never got/took the OTA update to mf3?
If you still have the mdl bootloader then you will be able to update to a new rom that is based off the new att firmware MJ6 soon. I would wait until a good rom is out to flash rather than getting any OTA update. Once you go to mf3 firmware you cannot go back to a previous firmware and you are limited on what can be flashed to your phone. If you take the new OTA (whenever att actually releases it) you will be stuck on that firmware and not able to go back to a previous firmware.
So like in my situation I have the mdb or mdl bootloader still, rooted, and I can flash any rom I want whether it is a mdl/mf3/ international firmware/ or when available the MJ6 firmware. All of this is harder/not able to do if you ever get OTA updates.
Sent From My Spiderman Themed I337
I never got the MF3 update. As I mentioned, I did try it twice, but the update failed, either because I froze some apps, or because I installed the CWM custom recovery. It's good to hear that it is actually a good thing. I noticed that the 4.3 firmware is out (the general forum), should I just install that one? How should I start? Thanks.
RockRatt said:
Just to be clear you never got/took the OTA update to mf3?
If you still have the mdl bootloader then you will be able to update to a new rom that is based off the new att firmware MJ6 soon. I would wait until a good rom is out to flash rather than getting any OTA update. Once you go to mf3 firmware you cannot go back to a previous firmware and you are limited on what can be flashed to your phone. If you take the new OTA (whenever att actually releases it) you will be stuck on that firmware and not able to go back to a previous firmware.
So like in my situation I have the mdb or mdl bootloader still, rooted, and I can flash any rom I want whether it is a mdl/mf3/ international firmware/ or when available the MJ6 firmware. All of this is harder/not able to do if you ever get OTA updates.
Sent From My Spiderman Themed I337
Click to expand...
Click to collapse
wxiao said:
I never got the MF3 update. As I mentioned, I did try it twice, but the update failed, either because I froze some apps, or because I installed the CWM custom recovery. It's good to hear that it is actually a good thing. I noticed that the 4.3 firmware is out (the general forum), should I just install that one? How should I start? Thanks.
Click to expand...
Click to collapse
What until one of the devs creates a flashable zip that you can flash in cwm. It'll probably be only a couple of days now that the leak is out.
Hey all, I just acquired the SGH-I337 as an upgrade to my Galaxy S3. I can not for the life of me get a custom ROM running on it. My goal is SlimKAT because I like the ROM and have been using it on every phone since my Samsung Vibrant. Any time I'm flashing something in ODIN that has anything to do with ABOOT, it fails, soft bricks the device, and I have to reflash in ODIN all over again.
Please let me know what information I can provide to help with this. I've never had so much trouble with a phone before.
zeusakatkm said:
Hey all, I just acquired the SGH-I337 as an upgrade to my Galaxy S3. I can not for the life of me get a custom ROM running on it. My goal is SlimKAT because I like the ROM and have been using it on every phone since my Samsung Vibrant. Any time I'm flashing something in ODIN that has anything to do with ABOOT, it fails, soft bricks the device, and I have to reflash in ODIN all over again.
Please let me know what information I can provide to help with this. I've never had so much trouble with a phone before.
Click to expand...
Click to collapse
Please tell us the firmware of your phone (baseband, modem, etc..)
I337 has locked bootloader if your firmware is MF3 and above (MK2, NB1, NC1). You have to use the safestrap as a recovery if you want to flash the custom roms. If you want to flash SlimKAT you have to the SlimKAT safestrap version if they have one.
If he had to use Safestrap he can't use Slimkat as it's AOSP and he can't change the kernel. Chances are if he was getting issues flashing aboot then he's on a newer version. Confirm it in the about phone section of the settings though.
Sent from my SGH-I337 running GPE
I believe when I got the phone, it was updated all the way. Although I'm not entirely sure what the latest firmware is. I tried using Odin to go back, which worked sort of
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
zeusakatkm said:
I believe when I got the phone, it was updated all the way. Although I'm not entirely sure what the latest firmware is. I tried using Odin to go back, which worked sort of
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can't go back to older bootloaders ever. Sounds like you are updated to something that you can't flash custom anything to. So safestrap is the only way to go with modded touchwiz based roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
You can't go back to older bootloaders ever. Sounds like you are updated to something that you can't flash custom anything to. So safestrap is the only way to go with modded touchwiz based roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to successfully unbrick the phone by using Odin to get it to MK2, although Wifi didn't work. Now I'm trying to get it back to the latest firmware so that I can sell it.
UPDATE!
Phone had been successfully reflashed to firmware NB1, with everything seemingly working. This phone seems so much more complicated than the S3 was, thanks locked bootloader.
zeusakatkm said:
I was able to successfully unbrick the phone by using Odin to get it to MK2, although Wifi didn't work. Now I'm trying to get it back to the latest firmware so that I can sell it.
UPDATE!
Phone had been successfully reflashed to firmware NB1, with everything seemingly working. This phone seems so much more complicated than the S3 was, thanks locked bootloader.
Click to expand...
Click to collapse
use this to get to the NB1 firmware then take the NC1 OTA
http://forum.xda-developers.com/showthread.php?t=2674223
shamelin73 said:
use this to get to the NB1 firmware then take the NC1 OTA
http://forum.xda-developers.com/showthread.php?t=2674223
Click to expand...
Click to collapse
Does it matter if I use the rootable version?
I would use the non root one then let phone take the NC1 OTA update.
That shod give you a clean slate to sell the phone or you can root NC1 with towelroot
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I've already flashed the stock one, but it says there is no software update available
I've already flashed the stock one, but it says there is no software update available
UPDATE!
Success! I am successfully running this rom
http://forum.xda-developers.com/showthread.php?t=2767026
4.2.2 / MDL here. I'm rooted to freeze the metric ton of bloatware/greenify/xposed. Didn't get into ROMs because I'm afraid of bricking my only phone.
Been sidelined for several months with health issues, wondering if there's been any new stuff down the pipeline or if I should stay at 4.2.2/MDL? TIA.
Sliced bread has come out. Jk, given the time taken for someone to answer you, nothing new has come out that's earth shaking. Other than new firmware. If everything works for you it probably isn't worth upgrading.
You're on mdl which allows you to flash a number of different roms which you aren't taking advantage of. The latest firmware, nc1, is rootable with towel root. You can flash touch wiz based roms but that doesn't seem to be an interest to you So you might consider updating to nc1 if you want the latest firmware. But many people would like to be in your shoes with mdl firmware.
Sent from my Nexus 5 using XDA Free mobile app
If you have root and custom recovery (TWRP or CWM) and want to update to newer firmware I would suggest Sho-Stock-i V7.0 Then you w I uld have the newest firmware without having to use Safestrap and be limited to what you can do with your phone.
I would STAY AWAY from updating to the newest firmware (stock firmware) NC1 as right now you can do ANYTHING you want with your phone. That is why I suggested ShoStock to have the best of both worlds. Personally there is NOT MUCH different between your MDL 4.2.2 firmware and the newest 4.4.2 firmwares. Maybe a little smoother.
Sent From My ATT S3 i747 Dark Blue BadAss Theme
Would reception be better with 4.4.2? We recently took a road trip and on a very long stretch my hubby on 4.4.2 had coverage the whole time while I had 0 service for about 1/2 of the stretch. Other areas he was pulling data fine while my phone showed no service or a G and up and down arrows which was completely new to me. It's bizarre.
RockRatt said:
If you have root and custom recovery (TWRP or CWM) and want to update to newer firmware I would suggest Sho-Stock-i V7.0 Then you w I uld have the newest firmware without having to use Safestrap and be limited to what you can do with your phone.
I would STAY AWAY from updating to the newest firmware (stock firmware) NC1 as right now you can do ANYTHING you want with your phone. That is why I suggested ShoStock to have the best of both worlds. Personally there is NOT MUCH different between your MDL 4.2.2 firmware and the newest 4.4.2 firmwares. Maybe a little smoother.
Sent From My ATT S3 i747 Dark Blue BadAss Theme
Click to expand...
Click to collapse
I don't think I have recovery? I only remember rooting, no option for twrp or cwm. Am I hosed now?
Wittyusernametaken said:
I don't think I have recovery? I only remember rooting, no option for twrp or cwm. Am I hosed now?
Click to expand...
Click to collapse
If you are still in fact on MDL then you can get TWRP or CWM recovery and flash as I stated above. You can use ShoStock-i once you have a custom recovery. First VERIFY you have MDL bootloaders. Then if you do look into "Motochopper +Loki" which will give you the custom recovery. Then flash to ShoStock-i. Then you can flash any of the modems in my thread to find which works best for your phone in your area. Maybe see which "baseband" (baseband=Modem) your husbands phone has (if it is also a i337 S4).
Sent fron I337 Red BadAss Themed ShoStock 7.0
do you have a link for the Sho-Stock-i V7.0? I can't find it? Also would any version of CyanogenMod work? I can't find one that would work without me upgrading to 4.4 if my google searches are correct. Sorry for the delay in replying... health issues are a PITA.
Wittyusernametaken said:
do you have a link for the Sho-Stock-i V7.0? I can't find it? Also would any version of CyanogenMod work? I can't find one that would work without me upgrading to 4.4 if my google searches are correct. Sorry for the delay in replying... health issues are a PITA.
Click to expand...
Click to collapse
You do NOT need to update to run ShoStock. Just flash his newest in recovery (TWRP/ cwm/etc.) It will give you the newer firmware of 4.4.2 but NOT give you the 4.4.2 bootloader. So you can always flash back to your MDL stock firmware via odin. Like I said, the best of both worlds. Keeping the bypassed bootloader while running newer firmware. Just use ShoStock 8.1 (NOT THE SAFESTRAP VERSION)
Note: Relevant device info will be provided below.
Dear techwizards,
I've been trying to root my phone for a while, I've done it before: both my S II and S III were international variants, and rooting those devices was very simple. But after getting an S IV from America and consensually downloading a samsung issued update -- I had yet to read up on the disadvantages of knox -- my rooting and android experience took a turn for the worse.
Long story short -- I know developers are a proud bunch who value their time -- I tried rooting my phone yesterday after almost smashing my phone on a coffee table. They say it's a well known side effect of Touchwiz, but I'll leave that to you.
I used a towelroot.com root -- a wonderful tool, if I may say so. After that, I visited the CM website and picked out the compatible CM11. I never got to flashing it though, as my problems arose while installing a recovery.
I had downloaded an app, a something recovery or another. They had an option to flash recoveries on there--it would download your recovery for you and do all the work, which seemed plausible as most video tutorials demonstrated. To my astonishment, doing so bricked my phone.
I tracked back, looked for the samsung stock rom, downloaded all 2.2 gb's of it and flashed it. It worked. My phone was functional but I suspect something within it stinks. My device, apparently for security reasons, wont let my wifi or 4g to establish a connection. It's making it impossible for me to fix this problem as I can't root my device or flash a custom rom.
About Device:
Pre problem I was running a:
SGH-I337UCUFNC1 baseband. Build Number ending with: NC1.
Android version: 4.2.2
Post problem:
Baseband: I337UCUFNC1
Build Number: JSS15J.I337UCUEMK2
Android version 4.3.
If I could find my original stock 4.2.2 NC1 version and get simple instructions on how to re-install it back to stock version, I'd be very grateful.
If you know how I could fix the internet issue on the MK2 one, and provide some simple instructions of how to root it, I'd be grateful too.
If you think neither would work, and have something else in mind, Im open to your suggestions.
Much Regards,
Y
You can only use safestrap for the recovery. See in the general forum index, all things at&t....
You can't flash cm, only touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You can only use safestrap for the recovery. See in the general forum index, all things at&t....
You can't flash cm, only touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I never got to installing or attempting to install CM.
Things took a turn for the unexpected after I tried installing CMW recovery.
Please reread my post
I've read it. You can't install cwm. That's what had messed up your device. The only recovery you can use is safestrap
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
jd1639 said:
I've read it. You can't install cwm. That's what had messed up your device. The only recovery you can use is safestrap
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Click to expand...
Click to collapse
I see. Thanks for the info. Do you know what could be done to restore my device to stock? As of now I'm running a MK2 Android 4.3 on a NC1 4.2.2 device and the wifi/4g connection aren't working.
androidshmandroid said:
I see. Thanks for the info. Do you know what could be done to restore my device to stock? As of now I'm running a MK2 Android 4.3 on a NC1 4.2.2 device and the wifi/4g connection aren't working.
Click to expand...
Click to collapse
Did you look for the thread I pointed you to? In the general forum index, all things at&t... You're going to want to start there. That'll link you to this
http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Since your bootloader is already locked, you might as well Odin to stock. Odin to NB1 then use stock recovery to flash the NC1 update from a zip file on a microSD.
Part of the problem is that the NC1 is not 4.2.2 like you listed, but 4.4.2. That's the update you applied that started the sordid tale. When you were on 4.2.2, with bootloader MD<something>, you could have flashed CM or whatever, because you would be able to have TWRP or CWM recovery. When Samsung pushed out a 4.3 update (MK2 I believe) all the unlocked bootloader fun was over, probably permanently for this phone.
When you flashed MK2 firmware (4.3) onto the phone, parts of it don't work with the NC1 baseband, causing the problems you've seen. If you Odin NB1, then do the quick zip update from stock recovery to get all the way to NC1, you'll be back to stock and everything should work.
Once that's done, you can go through this process:
1. Root with Towelroot.
2. Install SuperSU to manage root access. (You might have to reboot, it's a 50%/50% shot... sometimes it hangs trying to disable Knox... no worries just reboot)
3. Install SafeStrap... it will create the safestrap recovery. You might need to install SELinux Mode Changer app (from play store) and set to permissive, to get Safestrap installed.
4. Boot to the SafeStrap recovery. Install any touchwiz rom. Only touchwiz compatible roms will work. I liked GoldenEye.
When installing touchwiz ROMs, typically one flashes the ROM, then SuperSU, then the NC1 modules, then the ATT BuildProp/APN file. Sounds complex but goes quickly. Some roms have some of these things built in.
Good luck! I eventually decided I didn't like the ATT Samsung restrictions of the locked boot loader, and bought a T-Mobile M919 variant of the S4. Unlocked boot loader. Woo hoo. And works fine on ATT.
Marc