Softbrick/other questions - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix

nola mike said:
Just got my I337, using with simple mobile. Managed to sim unlock via this method, and was feeling pretty good. I think I had (have?) MK2. So using the stock ROM, it kept on asking to autoupdate. Didn't know if that would screw anything up, so attempted to install a kitkat venom ROM. I now can't get out of safestrap recovery. I'm not sure if the issue was trying to install a kitkat ROM, or if I mistakenly put it in the primary ROM slot. Anyway, I'm on a linux box without any immediate access to windows, so it looks like ODIN is out of the question. Been scouring the forums, but I have a few questions:
1. What are the limitations of the locked bootloader? Not really sure what I'm sidestepping by using a custom recovery. I had read that it limited me to TW ROMS (which is fine by me actually), but I see AOSP and other ROMs posted...
2. What exactly is meant by MK2, NC1, MF3, etc? I understand that they are progressions of SOMETHING, but not sure what--guessing it's the whole AT&T update, including ROM, modem, kernel? And I can't seem to find what exactly the progression is...
3. Is there a ROM that I should try to flash to get me back up and running before I start trying to screw with something else? Like I said, I have access to safestrap 2.71, adb, and an SD card, so I feel like this shouldn't be TOO hard to fix
Click to expand...
Click to collapse
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.

nola mike said:
Well, fixed my problem, though still don't have all the answers to my questions. I couldn't find a way to unbork without odin. Luckily my mom was in town visiting, and had a windows box that I used--I think I would have been hosed otherwise. Anyway, managed to revert to MK2 stock, and then upgrade to Goldeneye kit kat ROM via this method (my baseband is now listed as xxxxxxMLD).
I guess that MLD/NC1/NB1/MK2 are just ROM/radio firmware versions (kernel too, or is that completely unchangeable)? Still don't know the exact order of release, and if anyone could enlighten me a bit as to my other questions, I'd appreciate it...
I'll probably hold off on trying to change anything else until I have reliable access to windoze, unless someone can give me the steps using linux/adb.
Click to expand...
Click to collapse
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.

jmjoyas said:
The order of firmware versions with Android version - MDB(4.2.x) -> MDL(4.2.x) - > MK2(4.3)->MLD(4.4 leak)->NB1(4.4.x)->NC1(4.4.x)
The bootloader for SGH-I337 was always locked.
1. This means that the stock kernel and recovery cannot be replaced.
2, The bootloader cannot be downgraded.
But, there was a bug in the first 2 releases, that loki exploited and provided a workaround for #1.
When flashing a firmware that contains the bootloader (aboot.mbn), it does a version check. The version check is through a fuse count maintained in the bootloader. MLD and MK2 although are different Android versions, have the same bootloader version. That means you can flash one over the other (go back and forth). The same with NB1 and NC1. But, once you update to NB1, you cannot go back to MK2.
Since the kernel cannot be replaced, all the ROMs we flash have to be compatible with the kernel that we have on the phone. Hence the mention of TW only ROMS. We cannot flash CM/AOSP/AOKP/GPE (most) ROMS. The AOSP ROMS you are seeing are themed TW roms only.
Click to expand...
Click to collapse
Thanks for that, very enlightening.

nola mike said:
Thanks for that, very enlightening.
Click to expand...
Click to collapse
Just as an update, seems there's a workaround for Odin called heimdall, which is cross platform. . Haven't tried it, but looks like it should work.

Related

[Q] HOw to revert back from MK2 (ATT SGS4 i337) to MDB or MDL

HI there,
DOes anyone have a solution for us stuck on MK2?
I have the following problems:
I bought this i337 second hand, and it came with UCUAMK2 firmware.
I rooted it with SAFEROOT (saferoot.zip). That worked fine.
But I cant install LOKI, to get the ClockWorkMod, so I can't install Custom ROMs.
Because when I type in the commands in Android Terminal, to flash loki's CWM recovery, it says :
[+] loki_flash v1.1
[-] Loki aboot version does not match device.
SO i figure, I have to revert back to MDB or MDL firmware.
BUT when I open ODIN, and try to flash the official firmware:
1. I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
it FAILS in ODIN, so I (try) to flash this:
2.I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5
but that FAILS also!!!!!!!
SO should I install SAFESTRAP?
Some ppl complain, that screws things up, and end up in bootloop, and can't remove this SAFESTRAP...so i dunno if
i should install it.
Does flashing via/using ODIN FAIL==> because my bootloader is LOCKED?
Can you tell me how to Unlock my bootloader????
I need to go back to MDB or MDL, because otherwise I can't unlock the carrier restriction, since I'm on Vodafone,
and not on AT&T!
Plus, I was always installing custom Roms on my S2, S3, and all my other android devices since 2009....sorry to see
that the S4 is
such a headache....
Can you help me out please, seeing how good aof a DEV you are....?
Please and thank you
djmisi
You SOL buddy. Sell the phone and get something else. You will never be able to downgrade
MOTO X SLAPPED
djmisi99 said:
HI there,
DOes anyone have a solution for us stuck on MK2?
I have the following problems:
I bought this i337 second hand, and it came with UCUAMK2 firmware.
I rooted it with SAFEROOT (saferoot.zip). That worked fine.
But I cant install LOKI, to get the ClockWorkMod, so I can't install Custom ROMs.
Because when I type in the commands in Android Terminal, to flash loki's CWM recovery, it says :
[+] loki_flash v1.1
[-] Loki aboot version does not match device.
SO i figure, I have to revert back to MDB or MDL firmware.
BUT when I open ODIN, and try to flash the official firmware:
1. I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
it FAILS in ODIN, so I (try) to flash this:
2.I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5
but that FAILS also!!!!!!!
SO should I install SAFESTRAP?
Some ppl complain, that screws things up, and end up in bootloop, and can't remove this SAFESTRAP...so i dunno if
i should install it.
Does flashing via/using ODIN FAIL==> because my bootloader is LOCKED?
Can you tell me how to Unlock my bootloader????
I need to go back to MDB or MDL, because otherwise I can't unlock the carrier restriction, since I'm on Vodafone,
and not on AT&T!
Plus, I was always installing custom Roms on my S2, S3, and all my other android devices since 2009....sorry to see
that the S4 is
such a headache....
Can you help me out please, seeing how good aof a DEV you are....?
Please and thank you
djmisi
Click to expand...
Click to collapse
You will need to use safestrap.
Loki does not work with MK2 because they patched it in the MK2 update.
At this point in time the bootloader cannot be unlocked.
el o el
The s4 is nothing like previous samsung devices...at least on att, the bootloader is locked, safestrap is your only option.
Also keep in mind, att stated about a year ago they will no longer be supporting phones with unlocked bootloaders...so the problem you are experiencing now can be expected on every new att branded phone
Sent from my SAMSUNG-SGH-I337 using Tapatalk
djmisi99 said:
HI there,
DOes anyone have a solution for us stuck on MK2?
I have the following problems:
I bought this i337 second hand, and it came with UCUAMK2 firmware.
I rooted it with SAFEROOT (saferoot.zip). That worked fine.
But I cant install LOKI, to get the ClockWorkMod, so I can't install Custom ROMs.
Because when I type in the commands in Android Terminal, to flash loki's CWM recovery, it says :
[+] loki_flash v1.1
[-] Loki aboot version does not match device.
SO i figure, I have to revert back to MDB or MDL firmware.
BUT when I open ODIN, and try to flash the official firmware:
1. I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
it FAILS in ODIN, so I (try) to flash this:
2.I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5
but that FAILS also!!!!!!!
SO should I install SAFESTRAP?
Some ppl complain, that screws things up, and end up in bootloop, and can't remove this SAFESTRAP...so i dunno if
i should install it.
Does flashing via/using ODIN FAIL==> because my bootloader is LOCKED?
Can you tell me how to Unlock my bootloader????
I need to go back to MDB or MDL, because otherwise I can't unlock the carrier restriction, since I'm on Vodafone,
and not on AT&T!
Plus, I was always installing custom Roms on my S2, S3, and all my other android devices since 2009....sorry to see
that the S4 is
such a headache....
Can you help me out please, seeing how good aof a DEV you are....?
Please and thank you
djmisi
Click to expand...
Click to collapse
There is NO WAY back from mk2. You can flash custom roms ONLY with Safestrap. No CWM no TWRP. Read this guide, it has everything you need to know for the S4. There is nearly 30 custom roms tested & affirmed working. Good luck & happy reading.
http://forum.xda-developers.com/showthread.php?t=2616221
SGS4 AT&T i337 on Stock MK2...jeboo kernel/recovery needed to install SHOstock v3.0 ?
I am very familiar with custom roms and your kernels, from always using them on my SGS2 i777 (AT&T), but i just bought an SGS4 i337 AT&T, on MK2 baseband, and everybody suggested I should install the SHOstock v3.0 for the i337 (http://forum.xda-developers.com/show....php?t=2305752).
Problem is, I am sooooo confused now, because there is jeboo kernels: (Jeboo_Kernel_i337_v3_0a-i.zip, Jeboo_Kernel_i337_v3_0a.zip, Jeboo_Kernel_i337_v3_0.zip, Jeboo_Kernel_i337_v2_2.zip)
...than there's your RECOVERY: Jeboo_Recovery_v2_1.zip
so Im very confused now how I should go about installing our most awesome DEV shoman94's SHOstock v3.0) ROM...==> THAT I DUNNO WHAT SHOULD I DO ANYMORE.....
1. Because, on the thread there (http://forum.xda-developers.com/show....php?t=2305752), in POST#1 it says , in the Instructions, that :We must be running a custom recovery using Jeboo's Recovery from Post#4 which is your Jeboo_Recovery_v2_1.zip
2. But how should I run the Jeboo_Recovery_v2_1.zip RECOVERY, if Im on SafeStrap 3.71 (which is a recovery also)???
3. If i flash Jeboo_Recovery_v2_1.zip, wont that brick (or softbrick) the S4?
4. Or if I flash Jeboo_Recovery_v2_1.zip, will I end up having 2 recoveries? Or will I only end up with having only the Jeboo_Recovery_v2_1 ???
5. In POST#3, it says that:
IF YOUR PHONE HAS MF3/MK2 BOOTLOADERS, YOU MUST RUN THE MF3/MK2 STOCK KERNEL. DO NOT TRY INSTALLING ANYTHING BELOW UNLESS YOU HAVE MDB/MDL BOOTLOADERS THAT SUPPORT LOKI!!
So, should I NOT flash your Jeboo_Kernel_i337_v2_2.zip , since I am on MK2 stock kernel/baseband/bootloader....?
Check it out: http://i.imgur.com/cNWijKF.png
7. I mean, what is BELOW MF3/MK2 and ABOVE MDB/MDL? Because it also says, that: All binaries posted here will be loki'd (as signified by the .lok extension).
SO, keeping in mind that Im on Stock MK2 , but also Im ROOTED via SAFEROOT.zip (as you can see in the pic above: (http://i.imgur.com/cNWijKF.png) , can someone please tell me if I should flash this SHOstock v3.0, and more speciafically, WHICH, IF ANY of you jeboo kernels and Jeboo Recovery should I use?
Can I bug any of you to tell me the exact steps on how to get this SHOstock 3.0 on my i337, if I'm on MK2, rooted, and safestrap-ed?
ANy help would be much appreciated
djmisi99 said:
I am very familiar with custom roms and your kernels, from always using them on my SGS2 i777 (AT&T), but i just bought an SGS4 i337 AT&T, on MK2 baseband, and everybody suggested I should install the SHOstock v3.0 for the i337 (http://forum.xda-developers.com/show....php?t=2305752).
Problem is, I am sooooo confused now, because there is jeboo kernels: (Jeboo_Kernel_i337_v3_0a-i.zip, Jeboo_Kernel_i337_v3_0a.zip, Jeboo_Kernel_i337_v3_0.zip, Jeboo_Kernel_i337_v2_2.zip)
...than there's your RECOVERY: Jeboo_Recovery_v2_1.zip
so Im very confused now how I should go about installing our most awesome DEV shoman94's SHOstock v3.0) ROM...==> THAT I DUNNO WHAT SHOULD I DO ANYMORE.....
1. Because, on the thread there (http://forum.xda-developers.com/show....php?t=2305752), in POST#1 it says , in the Instructions, that :We must be running a custom recovery using Jeboo's Recovery from Post#4 which is your Jeboo_Recovery_v2_1.zip
2. But how should I run the Jeboo_Recovery_v2_1.zip RECOVERY, if Im on SafeStrap 3.71 (which is a recovery also)???
3. If i flash Jeboo_Recovery_v2_1.zip, wont that brick (or softbrick) the S4?
4. Or if I flash Jeboo_Recovery_v2_1.zip, will I end up having 2 recoveries? Or will I only end up with having only the Jeboo_Recovery_v2_1 ???
5. In POST#3, it says that:
IF YOUR PHONE HAS MF3/MK2 BOOTLOADERS, YOU MUST RUN THE MF3/MK2 STOCK KERNEL. DO NOT TRY INSTALLING ANYTHING BELOW UNLESS YOU HAVE MDB/MDL BOOTLOADERS THAT SUPPORT LOKI!!
So, should I NOT flash your Jeboo_Kernel_i337_v2_2.zip , since I am on MK2 stock kernel/baseband/bootloader....?
Check it out: http://i.imgur.com/cNWijKF.png
7. I mean, what is BELOW MF3/MK2 and ABOVE MDB/MDL? Because it also says, that: All binaries posted here will be loki'd (as signified by the .lok extension).
SO, keeping in mind that Im on Stock MK2 , but also Im ROOTED via SAFEROOT.zip (as you can see in the pic above: (http://i.imgur.com/cNWijKF.png) , can someone please tell me if I should flash this SHOstock v3.0, and more speciafically, WHICH, IF ANY of you jeboo kernels and Jeboo Recovery should I use?
Can I bug any of you to tell me the exact steps on how to get this SHOstock 3.0 on my i337, if I'm on MK2, rooted, and safestrap-ed?
ANy help would be much appreciated
Click to expand...
Click to collapse
You are making it too hard. You need to be on 3.71 Safestrap to flash Sho's 3.0. You must use default (stock) kernel. You can not flash any other kernels period. And no other recoveries. And no 4.4 or aosp roms. I am not on SafeStrap as I have a MDL phone. So, you need to go the SafeStrap thread and read up on flashing a rom on SafeStrap. There are a couple threads on the subject. Read all you can first and make any backup your phone/recovery allows before flashing. Also, do a clean wipe before installing rom. That may be different then a clean wipe on MDL/Custom Recovery, not sure--:good:
[email protected] said:
You SOL buddy. Sell the phone and get something else. You will never be able to downgrade
MOTO X SLAPPED
Click to expand...
Click to collapse
Problem is it came from AT&T Store with MDL ...but the MK2 update came through OTA...and that must of lock the bootloader....dayummmmmmm...
AM I right?
Yes
Maribou said:
You will need to use safestrap.
Loki does not work with MK2 because they patched it in the MK2 update.
At this point in time the bootloader cannot be unlocked.
Click to expand...
Click to collapse
Phone came from the Store with MDL, ( I see it on the Original box: SoftWare Ver: UCUAMDL....
The guy I bought it from rooted it, and loki-ed it... how did that OTA come through, I wonder? Once rooted and LOKI-ed...the OTAs shouldn't come through, right?
Sounds like the seller messed up and flashed back to stock. He was probably selling it to cut his losses.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Maribou said:
You will need to use safestrap.
Loki does not work with MK2 because they patched it in the MK2 update.
At this point in time the bootloader cannot be unlocked.
Click to expand...
Click to collapse
*************************************************************************
THX,
I just saw that the phone originally came with MDL baseband, its on the Original Box...
I wonder, was it with an unlocked bootloader at THAT time?
ANd the MK2 OTA update locked it?
djmisi99 said:
*************************************************************************
THX,
I just saw that the phone originally came with MDL baseband, its on the Original Box...
I wonder, was it with an unlocked bootloader at THAT time?
ANd the MK2 OTA update locked it?
Click to expand...
Click to collapse
Answer, yes & yes. There is plenty of custom roms for mk2 in the All things mk2 guide. You can also upgrade to 4.4.2 Kit Kat now as well. Forget about MDL cause there's no way to go back to it.
Maribou said:
You will need to use safestrap.
Loki does not work with MK2 because they patched it in the MK2 update.
At this point in time the bootloader cannot be unlocked.
Click to expand...
Click to collapse
Red_81 said:
Sounds like the seller messed up and flashed back to stock. He was probably selling it to cut his losses.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
******************************************
But if he had it LOKI-ed, that means he was just fine on MDL, no need for SafeSTrap, unlocked BL prolly ... he was free to install CM, GPE, AOSP, PACman and all these ROMs....so why flash it back to stock MK2? I mean, cutting his losses....that's funny...I mean, unless the MK2 OTA from AT&T came forced.... WHo knows...
He probably didn't know what he was doing, got stuck, and tried to Odin back to stock. Only he used the mk2 package and not the MDL one.
Stuff like that never surprises me anymore. People don't want to learn/read. Just give me the file so I can flash it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
joeybear23 said:
el o el
Click to expand...
Click to collapse
LOL my butt, buddy...we still have SafeStrap ....ab. 30+ ROMz for it...so not exactly eL Oh eL....but oh well....such is life, ya know?
Red_81 said:
He probably didn't know what he was doing, got stuck, and tried to Odin back to stock. Only he used the mk2 package and not the MDL one.
Stuff like that never surprises me anymore. People don't want to learn/read. Just give me the file so I can flash it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know EXACTLY what you mean, bud...just gimme the file so I can flash it -type ... who cares what's that gonna actually do to my phone...Oh well, there are people...and there's people.... U never know who you get to deal with....
Just ask for a little help, ...why is that so hard, right?
I've been reading up on all I could, and now that I "kinda" get a better understanding of how things lay with the i337 MK2...I can make a decision to flash, and stay stock...
Problem is, I have been flashing since 2009, so I can't imagine owning a droid, AND NOT FLASH IT!!! IT KINDA DEFEATS THE PURPOSE OF OWNING AN ANDROID, right? hehehe
I know that feeling. At least Safestrap is a decent option. I rushed out to grab my MDL 32gb one before they updated their stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
KK 4.4 NB1 baseband
John The Rhino said:
Answer, yes & yes. There is plenty of custom roms for mk2 in the All things mk2 guide. You can also upgrade to 4.4.2 Kit Kat now as well. Forget about MDL cause there's no way to go back to it.
Click to expand...
Click to collapse
***************************************
Yes, prolly could upgrade to 4.4 , but would be needing to flash the NB1 modem, baseband first right?
ANd ppl are saying there is not much SafeStrap versions for KK 4.4(.2) yet, or am I wrong?
DO you know any ROMz like that?
Would it be possible to come back to JB 4.3, once on KK, that you know of?
Lemme know, bud...THX
ANy links.....?

[Q] What is best way to get back to complete stock?

Hello,
What is the best way to get back to complete stock (including locked bootloader). I'm done with playing with custom ROMs (running CM11 right now). I want stock and guaranteed stability then nightmare dealing with nightlies etc.
artisticcheese said:
Hello,
What is the best way to get back to complete stock (including locked bootloader). I'm done with playing with custom ROMs (running CM11 right now). I want stock and guaranteed stability then nightmare dealing with nightlies etc.
Click to expand...
Click to collapse
I'm guessing you're on an I337 since you mentioned locked bootloader. If I were you I'd just flash a 4.4.2 stock ROM so that you can keep the possibility to use AOSP ROMs like the Google Edition ROMs and others. You can flash the ROM from HERE, use the version that doesn't say wBL at the end. Then just flash one of the 4.4.2 modems in RockRatt's I337 modem thread and it should work just fine. You could even reflash the MDL firmware before all of this to make it clean, or even just freeze the updater and stay on MDL.
If you really want to get rid of all possibility of running more than themed and modded TouchWiz ROMs, you can simply go to the General section, find the NB1 ODIN files, and flash them. If you want root after that, take the OTA to NC1 or sideload it and then use towelroot.
DeadlySin9 said:
I'm guessing you're on an I337 since you mentioned locked bootloader. If I were you I'd just flash a 4.4.2 stock ROM so that you can keep the possibility to use AOSP ROMs like the Google Edition ROMs and others. You can flash the ROM from HERE, use the version that doesn't say wBL at the end. Then just flash one of the 4.4.2 modems in RockRatt's I337 modem thread and it should work just fine. You could even reflash the MDL firmware before all of this to make it clean, or even just freeze the updater and stay on MDL.
If you really want to get rid of all possibility of running more than themed and modded TouchWiz ROMs, you can simply go to the General section, find the NB1 ODIN files, and flash them. If you want root after that, take the OTA to NC1 or sideload it and then use towelroot.
Click to expand...
Click to collapse
So if I flash one of NB1 ODIN files my phone will looks like something I get from ATT store if I walk in there today, right? That's what I want to achieve, completely something unadultered.
artisticcheese said:
So if I flash one of NB1 ODIN files my phone will looks like something I get from ATT store if I walk in there today, right? That's what I want to achieve, completely something unadultered.
Click to expand...
Click to collapse
Yes, it will be just like the others in every way, knox bootloader and settings and all, no custom flags or anything.

Help sought: Screwed up my S4 and seeking a fix

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

5.0.1 OC4 to OctOS 6.0.1 ?

i have rooted OC4 installed on my phone and have i've been reading up on OCTos and their 6.0.1 custom firmware (found a good link too: http://www.teamandroid.com/2016/01/20/update-att-galaxy-s4-i337-android-601-octos-marshmallow-custom-rom/ ) . and now am more confused.
it should be simple from what i am reading.
1) backup everything
2) revert to 4.3 (mk2), root, and install ClockworkMod 10.2+
3) install custom rom 6.0.1 OCTos
however, i'm reading on this page (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) but it states >> Once you flash NB1, you CANNOT go back to MK2. <<
So now I'm trying to figure out exactly how i can get the OCTos onto my phone. what guide should i follow !?!?!?!
:silly:
They meant the MK2 boot loader based devices, same with MDL. Aside from a few exploited boot loaders.. it's been the general consensus that they're all locked up, therefore.. only stock roms. The lowest boot loader you can possibly be on is NB1. Download "Terminal Emulator" for the Play Store and then when you open it up, type the following:
getprop ro.bootloader
^ exactly like that, then see what it says. The last three characters (MDK, MDL, MK2, NB1, NC1, OC3, OC4)--that's how you can figure out which boot loader you are using. I am on NB1's bootloader but I can still downgrade to MK2, i.e. Android 4.3, and still have it work.. only because of how the roms in these threads are rooted and the fact that they're stock, aside from a few other small details. When they say OC3 or MK2, or NB1... whichever.. then typically they mean the boot loader when saying you cannot revert. Definitely cannot revert to MK2 bootloader after taking an OTA update.
pr3dicament said:
getprop ro.bootloader
Click to expand...
Click to collapse
i337ucugoc4
egiblock said:
i have rooted OC4 installed on my phone and have i've been reading up on OCTos and their 6.0.1 custom firmware (found a good link too: http://www.teamandroid.com/2016/01/20/update-att-galaxy-s4-i337-android-601-octos-marshmallow-custom-rom/ ) . and now am more confused.
it should be simple from what i am reading.
1) backup everything
2) revert to 4.3 (mk2), root, and install ClockworkMod 10.2+
3) install custom rom 6.0.1 OCTos
however, i'm reading on this page (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) but it states >> Once you flash NB1, you CANNOT go back to MK2. <<
So now I'm trying to figure out exactly how i can get the OCTos onto my phone. what guide should i follow !?!?!?!
:silly:
Click to expand...
Click to collapse
Even though it was not mentioned, the article appears to be written for the SGH-i337 with old bootloaders (MDB, MDL). These are the only two bootloaders that can be exploited and installed the custom recovery like CWM or TWRP.
Since your bootloader is OC4 you can not install the CWM or TWRP. You could try flashing with safestrap though. If that custom rom is not written with Aroma then you could also try to flash with flashfire. These are the only two options for you.
egiblock said:
i337ucugoc4
Click to expand...
Click to collapse
Okay, yeah.. you're not on MDK or MDL, not even NB1.. you're simply on OC4. You aren't going to be able to do any flashing of any Custom Roms that are not Safestrap compatible (touchwiz)
Good luck.. you can't go anywhere backwards, not even OC3. That really sucks. I'm sorry. It looks like you took the OTA's.
I can still ODIN to NB1 and that was because I never took the OTA update. I got lucky.. I can still choose between kitkat and lollipop. You can't. You might be able to with someone's help.. but your bootloader is OC4.. that's a problem. You more than likely will have trouble doing anything unless it's not MDK/MDL or even NB1 based.
---------- Post added at 08:23 PM ---------- Previous post was at 08:21 PM ----------
sway8966 said:
Even though it was not mentioned, the article appears to be written for the SGH-i337 with old bootloaders (MDB, MDL). These are the only two bootloaders that can be exploited and installed the custom recovery like CWM or TWRP.
Since your bootloader is OC4 you can not install the CWM or TWRP. You could try flashing with safestrap though. If that custom rom is not written with Aroma then you could also try to flash with flashfire. These are the only two options for you.
Click to expand...
Click to collapse
Yeah.. You might have a shot with FlashFire. I might test that via the NB1 bootloader that I'm on but I don't think it matters that much aside from being able to Odin back to 4.3 software.
sway8966 said:
Even though it was not mentioned, the article appears to be written for the SGH-i337 with old bootloaders (MDB, MDL). These are the only two bootloaders that can be exploited and installed the custom recovery like CWM or TWRP.
Since your bootloader is OC4 you can not install the CWM or TWRP. You could try flashing with safestrap though. If that custom rom is not written with Aroma then you could also try to flash with flashfire. These are the only two options for you.
Click to expand...
Click to collapse
FlashFire came out with another release (0.32) that seems to have an AROMA emulation option.. my guess is that it's still in testing, but it's worth a shot even without it. The way I have OC3 with the NB1 boot loader is because of FlashFire.. Safestrap.. it's been awhile since I've used it. I've tried recently for other ROMS but you can't do a custom kernel.. that's the reason most custom roms aren't able to work, i.e. CM v13 runs a totally different kernel. It's not just TouchWiz now.. now it's just stock kernels.. at least via SafeStrap. So far I've gotten none to work with SafeStrap aside from Stock rooted roms. OC3, OC4, and if I felt like it, OK2.. but why even bother with OK2, I'm not gonna see any difference given all of the patches you can use with Xposed.. including any memory leak bull****, that's all good now in 5.0.x -- 5.1+ has that patched up.. and OK2 certainly isn't 5.1. I don't see any difference between OC3 and OC4.. and if my opinion counts for anything.. the one thing that I noticed (bloatware script ran and other apps not needed were frozen for both) is a very high amount of battery usage with OC4.. same userdata, same everything.. and when you flash the kernel, the modules, and move up to OC4.. it's still the same looking.. feels the same.. more ram used.. OC3 is superior in this instance. I'd love to try and give an AOSP rom a shot.. but.. via SafeStrap (someone made a guide for those not on the MDK or MDL boot loaders) .. eh.. no luck. That was all via SafeStrap. I'm just putting in my two cents. I think development for this phone is finished.. no one has come out with anything new aside from the SafeStrap kernel workarounds.. not many FlashFire users.. and the one that used to find every single exploit is now EMPLOYED by Samsung so his development.. gone. That was a huge kick in the ass to this entire community. Plenty of people around, just.. they don't give a **** about the S4 with boot loader all locked up. NB1 was an accident for me.. I was on MDL for a long, long time.. I really ****ed that up or I'd be running MarshMallow already It seems to run best with KitKat, but a lot of AOSP roms have shown huge differences in MarshMallow.. oh well. Can't try it at the moment.
Unfortunately I can't remember what I did in the past to this phone, but I have never had luck with OTA updates. I'll have to see if I can find my note to see what I originally did on this stupid thing.
egiblock said:
Unfortunately I can't remember what I did in the past to this phone, but I have never had luck with OTA updates. I'll have to see if I can find my note to see what I originally did on this stupid thing.
Click to expand...
Click to collapse
Since you are on OC4, the lowest you can go is NB1 (kit-kat).

Sprint Galaxy S4 Rooting

I've spent hours searching and I know this is an old phone. Is ther anyway to root the Lollipop and download Jelly Bean (custom or stock) to it? I'm not worried about Warranties. I'm not exactly a newb and I don't like Lollipop at all. I don't mind KitKat, but what I hate is the front facing camera can't be flipped. Dumbest thing ever.
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Click to expand...
Click to collapse
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
BikerSk8rKid said:
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
Click to expand...
Click to collapse
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
GDReaper said:
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Click to expand...
Click to collapse
I was half asleep and stressed out when I posted this. It's been a couple weeks or longer since I messed with the phone. Damn forums weren't resetting my password. When I mean I'm not a newb I mean I'm not like brand new to this and I know how to research. I guess you could say I'm not THAT stupid. haha
I'mma have to try this again and figure out what path's I kept trying. I'm so spaced out I can't remember hard any of it. Just that I tried to flash a stock and rooted rom with old odin and new odin. Spent 2 days straight messing with it and trying to get around it. But I kept getting blocked. I didn't come across CF-Autoroot. So I'll try that.
Strephon Alkhalikoi said:
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
Click to expand...
Click to collapse
Of all the researching I've done (I couldn't login) that one never showed up in my searchs. haha I'll have to give that one a try. It's been a couple weeks or longer. SPH-L720. I had a few Tri-Bands, but it seemed those were limited compared to the standard model.
Update: I went the CF-AutoRoot route and then tried to use Odin to flash stock mk2 rom. Now that I remember it kept failing everytime and then it would corrupt the current rom. I also tried using TWRP and couldn't get it to work properly.
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
GDReaper said:
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
Click to expand...
Click to collapse
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
BikerSk8rKid said:
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
Click to expand...
Click to collapse
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
GDReaper said:
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
Click to expand...
Click to collapse
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
BikerSk8rKid said:
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
Click to expand...
Click to collapse
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
GDReaper said:
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
Click to expand...
Click to collapse
I'll look into that and give it a shot. Thank you! I knew it wasn't THAT easy. LOL

Categories

Resources