Can someone get us a stock odin image w/o root? I'm really apprehensive of rooting my phone on that off chance that I have a warranty issue.
...I'm scared
So, there is no Stock ROM? I've gotten myself stuck without recovery and need an Odin recovery file...I can't believe that doesn't exist yet. What does it take to get an Odin recoverable .md5/tar?
I'm scared.
I don't know that there has been a Samsung Android phone released where the stock ROM hasn't come out....eventually.
It will probably come out sooner rather than later, but it hasn't leaked out yet.
In any case....I think it's probably prudent to hold off on rooting (and therefore voiding your warranty) until the stock ROM leaks.
We need a leaked from for that.
Sent from my cm_tenderloin using Tapatalk 2
asked about this in another thread, heres a site that was mentioned by Reviewers http://www.sammobile.com/firmware/?page=-1. assuming when its available, it will be so there
Related
Not a Dev, but not a Noob, either. Formerly had a SGH-i897 Galaxy S for 3 years and flashed like crazy on it, while transitioning from Eclair to Froyo to Gingerbread to ICS to Jellybean, mostly using the fine offerings from the AOCP Collective folks. While familiar with Odin, CWM was my usual go-to utility.
Upgraded recently to a SGH-i337 Galaxy S4. Must have owned it for two, maybe three hours, before I rooted it with MotoChopper. This allowed me to re-install Titanium Backup. I left it as merely rooted, while I read up on CWM and some new-fangled thing called TWRP, which I wanted to get installed before casting about for a new ROM. (At the time, AOCP did not have an offering here, or it would have been a no-brainer for me.)
One morning, I turned on the phone and noticed it was doing an OTA update. . . . . . . . .
Mildly curious, I logged onto XDA to read what the community thought about the update, only to discover that I had missed all the dire warnings by a day and my (now) version I337UCUAMF3 ROM had it's boot-loaders locked from a blown Q-Fuse, courtesy of Samsung and AT&T.
Took me a week before I found the rooting solution from jortex, but thankfully, I'm now rooted again.
This background now leads to my questions:
I have ROM Manager Premium (from previous purchase) but have not installed it.
I was aware on my previous SGH-i897 that mixing the Gingerbread and Jellybean boot loaders was like, a Bad Thing when flashing ROMs and would promptly brick the phone.
Does CWM require the ability to load from a boot loader?
I know it creates an update.zip file to restore the original ROM, and usually does so by using whatever ROM is installed at the time.
So wouldn't it just create an update based on the I337UCUAMF3 ROM?
Even if I can't flash new ROMs (unless or until somebody comes up with a Q-Fuse Fix) couldn't I at least have all the recovery and .zip flashing of apps and cache clearing menu choices available to me from CWM?
Or would the act of just installing CWM on a I337UCUAMF3 ROM immediately brick my phone?
In Other Words, how close can I dance to the water's edge?
Been to the ROM Manager web site and they claim I can do any thing at any time.
(Easy for them to say: It ain't THEIR phones!)
Been searching these threads and can't come up with anything explicitly stating yea or nay.
So far, I have been happy enough with the TW stock ROM, but I always felt better being able to boot to recovery to fix things, on those few occasions I got just a leeeeeetle too close to the Bleeding Edge!
What is the consensus out there?
Will CWM 6.0.3.6 bork a I337UCUAMF3? Yes or no?
Would appreciate any thoughts that might enlighten me! :fingers-crossed:
It sure could brick the phone, the only thing you can do at the moment is root. I have seen a couple people try running a recovery on it, and it required a jtag service to restore the device.
Be careful.
TheAxman said:
It sure could brick the phone, the only thing you can do at the moment is root. I have seen a couple people try running a recovery on it, and it required a jtag service to restore the device.
Be careful.
Click to expand...
Click to collapse
Appreciate the response!
This phone is far different from the Captivate. There is no flashing anything on MF3. Basically you are waiting for a work around if that is even possible.
Sent from my SGH-I337 using xda premium
Hi, I am new to the GS4, came from the EVO 4G LTE, couldn't wait until it was time to upgrade and here I am finally! I did a search and specifically looking for information on rooting. Looking for pros and cons and possibly of returning to stock when necessary. Any help would be appreciated! I am currently running latest and greatest firware. Phone was purchased this weekend and I have upgraded to the latrst. Hopefully not a bad thing as I know with the EVO you would be screwed with the wrong hboot etc.
Thanks for your time and glad I went with Samsung, I'm loving this phone!
Sent from my SPH-L720 using xda app-developers app
waterbound said:
Hi, I am new to the GS4, came from the EVO 4G LTE, couldn't wait until it was time to upgrade and here I am finally! I did a search and specifically looking for information on rooting. Looking for pros and cons and possibly of returning to stock when necessary. Any help would be appreciated! I am currently running latest and greatest firware. Phone was purchased this weekend and I have upgraded to the latrst. Hopefully not a bad thing as I know with the EVO you would be screwed with the wrong hboot etc.
Thanks for your time and glad I went with Samsung, I'm loving this phone!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
If you've upgraded to the 'latest greatest' you actually are kind of screwed.
That means that you took the OTA to MK2 with the Knox bootloader. AND that means that you cannot modify your device without tripping the 'knox counter flag'. That may not be a big deal - you can still flash loads of ROMs.
AND you can root using CF-Autoroot - search it's here in the dev section. then add a custom recovery like Philz or TWRP (some ROMs require flashing with one or the other; I keep zips of both on my SD to let me flash between them for installing different ROMs.
And you can now return to stock MK2 via Odin thanks to a .tar you can download from Sammobile.com (link is here too). BUT you cannot 'reset' the knox counter - as of yet.
Take some more time and you'll surely find this device to be as fantastic as most of us do.
Good luck!
Thanks for the details! I figured I might have screwed myself a bit by taking the updates. I assume the counter flag isn't a big deal unless I want to return to stock? I'll read up on Knox to understand my limits. Thanks again!
Sent from my SPH-L720 using Tapatalk
The Knox warranty flag will only affect you if you need to send the phone to Samsung for warranty repair or replacement. If you never need to send it to Samsung then it won't matter. Sprint has really changed their rooting policies lately and don't seem to complain as much if you rooted your phone. TEP, Best Buy Ins, Square Trade, and other insurances will still replace or fix your phone, Samsung is the only one that will have a problem that the warranty flag is tripped.
I have a question. I have a Verizon Galaxy Note 3. I was wondering if it was possible to flash a custom ROM on my phone If I don't care about tripping Knox after being ignorant and updating to the Official KitKat firmware from Verizon. I've been searching for an answer for this for about a week and I'm not sure if I'm just wording it wrong. The only thing I got close to an answer to this question was someone said that you couldn't do it without tripping knox. I'm guessing that isn't correct being how motivated these phone companies seem to keep their crap installed on my phone. I really don't care about tripping knox and my warranty. I just want to get rid of flipboard and samsung push service off my phone. Can someone please point me in the right direction.
Your problem is you took the official OTA and no one has made a root method that works for it. Plus your bootloader incremented with the update. Which means if you try to flash a lower level one you'll soft brick at a minimum.
Before you took the update you could have rooted and flashed away. Tripping Knox counter only matters if you care to warranty your phone through Verizon or Samsung. If they see the counter at 1x0 or higher they know you've flashed illegal software at least once. They'll deny service. If you don't care. And don't ever intend to warranty or sell the phone. Then you're fine.
However. Like I said. Once you took the update. Unless you were able to keep root using super user survival mode or whatever. You're pretty screwed til someone finds a new exploit.
Sent from my GlaDos Baked Potato
Legato Bluesummers said:
Your problem is you took the official OTA and no one has made a root method that works for it. Plus your bootloader incremented with the update. Which means if you try to flash a lower level one you'll soft brick at a minimum.
Before you took the update you could have rooted and flashed away. Tripping Knox counter only matters if you care to warranty your phone through Verizon or Samsung. If they see the counter at 1x0 or higher they know you've flashed illegal software at least once. They'll deny service. If you don't care. And don't ever intend to warranty or sell the phone. Then you're fine.
However. Like I said. Once you took the update. Unless you were able to keep root using super user survival mode or whatever. You're pretty screwed til someone finds a new exploit.
Sent from my GlaDos Baked Potato
Click to expand...
Click to collapse
Thank you for for the reply. That pretty much confirmed what I was suspecting about flashing a different ROM after foolishly updating to KitKat. I had my phone rooted before, but I unrooted it when I was done cleaning up the bloat. You are right about soft bricking the phone. When I tried reverting back to jellybean, it would soft brick my phone and I would have to have to install a back up of the PIT file using ODIN. I'm going to do some more research to see how the authentication process works for these ROM files. There has to be away to modify the contents of the ROM unless there is a predetermined data size and the phone stops the write process. Again thank you for your time and good luck.
Search again, by the way, you can do it now... Just wanted to let you know in case you stopped reading here
Sent from my SM-N900V using Tapatalk
I just had to replace my S4 because I broke the screen on my old one. Unfortunately, the new one was shipped to me with NAE firmware and boot loader already installed. This means I'm already on KNOX from the first second of turning it on.
I have seen plenty of guides on how to update to NAE, and get root, etc. by not allowing KNOX to installed. However, I haven't really seen anything about what can be done if it's already installed. There's things scattered all over the net that suggest there might be ways around this, but nothing on the forums here that I have been able to find yet.
I'm not looking to flash any crazy roms or anything right now, I really just want root, but it seems like even that might be impossible now. Could I use something like "DrKetan Multitool" to "DeKNOX" my device and then root it? Does this tool even work on the S4, he claims it does but I've not seen it mentioned on the actual S4 forums. Any advice would be greatly appreciated. Note, I am looking for a method that doesn't trip the flash counter; or at least allows a reset afterwards. I'd rather not void the warranty on a brand new device if possible.
http://forum.xda-developers.com/showthread.php?p=53166571
Try this...it is a custom ROM but really close to stock
Sent from my SPH-L720 using XDA Premium 4 mobile app
I was already planning on installing UnknownForce Stock Rooted NAE Rom, if it's possible. However, you didn't really answer my question. Is there a method to bypass/kill the KNOX boot loader at this point or not? If not, then I might as well just stop now. I'm not prepared to void the warranty at this point.
tcatut said:
I was already planning on installing UnknownForce Stock Rooted NAE Rom, if it's possible. However, you didn't really answer my question. Is there a method to bypass/kill the KNOX boot loader at this point or not? If not, then I might as well just stop now. I'm not prepared to void the warranty at this point.
Click to expand...
Click to collapse
No. Once you have Knox, you have it.
Sent from my SPH-L720 using Tapatalk
After reading up a bunch it appears that even though I've successfully rooted my AT&T Galaxy S4 running NI1, I will not be able to unlock the bootloader and need to use safestrap and simply be limited to TW based ROMs. LAME!
Honestly, I don't care about voiding the warranty by tripping the knox sensor. What I would like to find out is if anyone has successfully flashed a previous build that has an unlocked bootloader so that I can put a custom recovery on and flash AOSP roms. Again, I know it will void the warranty. Don't care. If anyone could point me to a thread or explaining the process that would be cool. I've been searching for hours and have come across people asking the question but they just get met with "you'll void your warranty" bs.
If it can be done without bricking the phone I'll do it.
It can't be done. Qfuses are blown. It won't brick your device trying, Odin will just fail. But it's not worth the time trying because it won't work.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It can't be done. Qfuses are blown. It won't brick your device trying, Odin will just fail. But it's not worth the time trying because it won't work.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, can you clarify? You said "it won't brick your device trying", but it sounds like from the other parts of your post that you are saying it WILL brick the device.
What I hear you saying is that because of a "Qfuse" if I flash a pre-MGG stock release of the AT&T S4 firmware using ODIN on a rooted NI1 firmware then the device will brick. Is that accurate? I assume you know this because someone tried or is it theoretical? I don't ask because I'm skeptical but simply because sometimes people repeat things based on what someone else said rather than actual tested results.
Part of the reason I'm asking is because all the posts that I'm looking at people are saying flashing a pre-MGG rom will result in the knox register being changed to 0x1. I don't really care about that. What I want to know if warranty void or no, will it work. The QFuse posts don't seem real clear either.
objecttothis said:
Part of the reason I'm asking is because all the posts that I'm looking at people are saying flashing a pre-MGG rom will result in the knox register being changed to 0x1. I don't really care about that. What I want to know if warranty void or no, will it work. The QFuse posts don't seem real clear either.
Click to expand...
Click to collapse
A brick is when you're device becomes completely inoperable and unrecoverable. That will not occur if you try to flash the mdl firmware. But, the mdl firmware will not flash onto your device. Doesn't matter if you don't care about voiding warranty or not. It simply won't work, ever.
And by the way, there are no AT&T i337 bootloaders that were unlocked. There were just two that could be exploited with Loki to flash custom recoveries and kernels.
Sent from my Nexus 9 using XDA Free mobile app
Once Kit Kat is on phone you can Not go back to Jelly Bean, mdl firmware !!!!