Related
The whole purpose of this ROM flash is to easily revert back to RFS from the ext4 file system without having to resort to odin. The Froyo DK28 Modem is a prerequisite. Please use a 3 finger salute to enter clockworkmod rather than quickboot recovery before flashing this.
***NOTICE*** THIS TOPIC IS NO LONGER SUPPORTED.
A new, more reliable ReRFS Format Stock ROM EC05 is available here:
http://forum.xda-developers.com/showthread.php?t=1027904
This is a stock Froyo DK28 odexed ROM, prerooted with some mods. Nothing fancy, but will get you to a trusted Froyo environment without any hassles. This can be flashed from either ClockworkMod versions 2 or 3, and will replace cwm3 with cwm2. It also flashes the stock DK28 kernel. This flash can prove incredibly useful for those experiencing problems during the ext4 conversion process, and those with Macs who don't have access to odin.
Warning: For some people, this hs failed. Symptoms included not being about to mount, umount, or format the stl blocks. The phone wouldn't boot past the samsungmobile.com logo. If this happens, an odin flash will fix it.
Edit: I did perform at least a dozen tests with both Quantom Rom 2.7 and Bonzai4All 1.1.4, using all clockworks. Also coming from both ext4 journaled and nojournaled. I couldn't get it to fail. So if this fails for you, please tell me as much as possible about the situation: was it nonbootable previously? What ROM were you coming from? What file system? Can you adb while the phone is in clockwork and type "mount | grep stl" (without quotes)? What is the output?
Note: This will erase all data, so perform a backup first before flashing. I intend to make another release as soon as I can find a way to reliably secure both a nandroid backup and restore from the script.
Hopefully this will soon be deprecated by a version of ClockworkMod 3 that can format and handle both the ext4 and RFS file systems.
Credits go to:
Noobnl for the original modded stock rom, supercurio for his voodoo lagfix sources that clarified the use of fat.format, and Dameon87 for parts of the Edify script. Noobnl once again for guidance and patience.
Great!
Would've helped me the first time I tried to flash (ViperRom..) and booted straight to CWM every time.
Sh0t from my Bonsai'd SPH-D700 using the XDA Android app.
No more windows, your a life saver. Thanks for this!
Sent from my SPH-D700 using XDA App
I used this and my screen would not get past the samsung screen on boot up.
redram38 said:
I used this and my screen would not get past the samsung screen on boot up.
Click to expand...
Click to collapse
what rom were you using before the flash? and what filesystem?
thanks needed this!
DRockstar said:
what rom were you using before the flash? and what filesystem?
Click to expand...
Click to collapse
Bonsai4All EXT4 1.14 was on RFS used CWM3 to convert. I probl messed up something somewhere. Ended up bricking the phone trying to get back to stock.
Updated original post with my latest test results... I couldn't get the flash to fail. Please continue to post your results here.
One interesting thing: I was able to use the ReRFS.Format.ROM to get back from a failed bonsai4all 1.1.4 install from cwm2.
Sent from my SPH-D700 using Tapatalk
I was running DK28 and CWM 2.5.1.0, I updated to CWM 3.0.0.5, and after the 3-finger salute, and the back-up creation, the phone began freezing at the Samsung screen. In my naivety, I removed my SD card from the back of my phone and proceeded to replace all the files on the SD card with the ones I had backed-up (since the install caused an SD card format)
And from there, my phone wouldn't do ANYTHING outside of the CWM 3 menu. I can't update, format, mount/unmount, backup, or restore. I have an original DK28 update.zip that I tried to use, it wouldn't work. I tried installing the Quantum Rom, since it's supposed to be compatible with the CWM3 file-type, no avail. Also tried to use the ROM you provided, everything runs, and it claims it's successful, but it won't boot past the CWM3 menu. And since the phone won't load past the menu, I can't get it into download-mode for an Odin flash. Odin recognizes the phone, but this is what I get:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.
and it just sits, nothing happens. So, I'm out of options. I've really no clue what I'm doing with this whole Android development thing and I was taking a gamble by even attempting to update it, so I guess it's what I get for meddling where I shouldn't be meddling.
Okay, was able to finally get the phone into download mode, but only for a slit second. And, this was my Odin experience:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Complete(Write) operation failed.
now, the phone won't turn on at all.
zdavidi said:
Okay, was able to finally get the phone into download mode, but only for a slit second. And, this was my Odin experience:
Added!!
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
param.lfs
Complete(Write) operation failed.
now, the phone won't turn on at all.
Click to expand...
Click to collapse
Take out your battery, and while holding down both the 1 key and the power buttons with one hand, replace the battery with the other hand. This should get you back into download mode.
Sent from my SPH-D700 using Tapatalk
DRockstar said:
...
Warning: For some people, this hs failed. Symptoms included not being about to mount, umount, or format the stl blocks. The phone wouldn't boot past the samsungmobile.com logo. If this happens, an odin flash will fix it.
...
Click to expand...
Click to collapse
Can you elaborate on the part where said "an odin flash will fix it"?
The only thing I knew how to do with Odin was flash the DK28 modem, which I did, but it did not change my situation - still stuck at the SAMSUNG splash...
I found SPH-D700-DK28-8G-REL.tar.md5 and flashed that and now I'm back in business - **phew**
I tried to flash it through clockwork but got the frozen samsung screen after.
I tried odin but odin needs to have a tar file i believe and this is zip.
I had that exact same problem when I did that..i was going around asking for help all I was getting im doing something wrong...just don't trust ext4 and cwm3 never did ... I ended up replacing my phone....
Sent from my SPH-D700 using XDA App
As wonderful as this sounds on paper and concept...its not working, will keep a eye out for any updates.
Sent from my SPH-D700 using XDA App
Cobaltikus said:
Can you elaborate on the part where said "an odin flash will fix it"?
The only thing I knew how to do with Odin was flash the DK28 modem, which I did, but it did not change my situation - still stuck at the SAMSUNG splash...
Click to expand...
Click to collapse
You gotta download the DK28 Md5 .tar file, then use that in Odin. Put it in the PDA section of Odin. You don't need the modem and pit file when your using the Md5.tar file, as it already has those 2 in it...
Sent from my SPH-D700 using XDA App
same happened to me, just sitting on boot screen.
I rooted my phone the other day using this thread: http://forum.xda-developers.com/showthread.php?t=2046439. Then I tried to install MOAR rom and it didn't work, weird I thought. So I flashed my phone back to the recovery image I made before installing MOAR. However, my phone would start to randomly turn off. Well the screen would turn off and nothing would help to turn the phone back on unless I remove the battery and reboot. One of those time, it got stuck on the galaxy s3 screen and wouldn't go anywhere.
I tried reflashing a rom and it said that it couldn't mount my /system. So then I looked into this guide: http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/. Right now I'm trying to install the VRALEC bootloader and it gets stuck on the sbl2.mbn file. It's probably been like that for half an hour now. I've tried turning off odin and rebooting into download mode and trying different cables, but to no avail. Is there anything else that anyone can suggest me doing?
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
This is the Odin log. I'm using Odin 3.07
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. Then use Ez-Unlock 1.2 to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. Then use Ez-Unlock 1.2 to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice. I tried it and for whatever reason it gets to NAND WRITE START after sbl2.mbn and then doesn't do anything else. Any chance I've actually hard bricked my device? Or is that term only used for phones that cannot boot into download mode? And what is sbl2.mbn?
Check md5 it may be a bad download.
Sent from my SCH-I535 using Tapatalk
Okay I checked the md5, it checked out. I tried a different file from that thread and it still halts when it gets to sbl2.mbn. This is really frustrating..
Another question. If I installed the Sprint MOAR rom instead of the Verizon MOAR rom, is there any chance I would still be able to boot into download mode? Because I might have done that. I think I googled galaxy s3 moar rom and got to the sprint page, but I'm not completely sure. I deleted the files I used because I was running out of space on my hard drive so I can't check them.
nike t said:
Another question. If I installed the Sprint MOAR rom instead of the Verizon MOAR rom, is there any chance I would still be able to boot into download mode? Because I might have done that. I think I googled galaxy s3 moar rom and got to the sprint page, but I'm not completely sure. I deleted the files I used because I was running out of space on my hard drive so I can't check them.
Click to expand...
Click to collapse
You could check your browser history. Btw, it sounds like you may need to reflash a pit file to get around all your issues. Idk if that will definitively resolve your issues though.
Sent from my SCH-I535 using Tapatalk 4
Awesome, I think that would be good to try. Is this the pit file I need? http://forum.xda-developers.com/showthread.php?p=30547929 and then would I just use one of the ROM's from the thread that Sandman posted? Or would I be using the stock ROM from samsung-updates?
nike t said:
Awesome, I think that would be good to try. Is this the pit file I need? http://forum.xda-developers.com/showthread.php?p=30547929 and then would I just use one of the ROM's from the thread that Sandman posted? Or would I be using the stock ROM from samsung-updates?
Click to expand...
Click to collapse
Try using one from samsung-updates, it will wipe /sdcard though which is the internal storage. To clarify, our phone is SCH-i535 (or d2vzw) so do not flash anything in Odin unless it's meant for our device.
Okay so I got the vzw-i535vbrmf1-20130627174111.zip file and the sch-i535-16gb.pit file. I just put the zip file in the pda spot and then the pit file in the pit section and then check repartition and hit start right? I'm just trying not to screw this part up because I know I'll hard brick it if I do.
edit: I'm guessing I need to unzip it to get the tar out first
Update: I tried the pit and vbrmf file and it wouldn't go past nand write!!!!... Could this be a motherboard issue?
nike t said:
Okay so I got the vzw-i535vbrmf1-20130627174111.zip file and the sch-i535-16gb.pit file. I just put the zip file in the pda spot and then the pit file in the pit section and then check repartition and hit start right? I'm just trying not to screw this part up because I know I'll hard brick it if I do.
edit: I'm guessing I need to unzip it to get the tar out first
Update: I tried the pit and vbrmf file and it wouldn't go past nand write!!!!... Could this be a motherboard issue?
Click to expand...
Click to collapse
Hmm, why is it getting stuck at that same point? Are you using the Samsung OEM cable? Able to try a different port or try this on another computer? And to clarify, you are pressing "Start" correct?
I wish I could tell you why it always stops at the same spot :/.I am using the OEM cable and tried different ports on the ccomputer and multiple versions of Odin. I haven't tried another computer though. I'll try that soon. And yes I am pressing start. I don't know what's happening
nike t said:
I wish I could tell you why it always stops at the same spot :/.I am using the OEM cable and tried different ports on the ccomputer and multiple versions of Odin. I haven't tried another computer though. I'll try that soon. And yes I am pressing start. I don't know what's happening
Click to expand...
Click to collapse
Maybe uninstall the Samsung drivers, reboot the computer, then put your S3 into download mode and plug it into your computer to force install new drivers. Once it installs new drivers, boot the phone back into download mode and try again with Odin. If its a laptop, keep it plugged into the wall outlet.
So I tried what you just suggested (uninstalling the samsung drivers and then rebooting the computer) and then also tried writing the stock image from a different computer. I'm getting the same problem. It will not get past the "NAND Write Start!!" part..
Would trying the debrick image on an SD card work for me? Or is that mostly just to be able to get the phone into boot mode and then from there flash the regular image? I'm so extremely confused why this is happening to my phone
EDIT: http://forum.xda-developers.com/showthread.php?t=2345831. I'm now reading this thread. It says that if flashing a pit file fails my phone is dead, and the motherboard is screwed. True story? I also know this is for Samsung Galaxy S2, but I thought that the same would apply to the S3
EDIT2: http://forum.xda-developers.com/showthread.php?t=1457458. Now I'm reading this thread. Could I have a NAND corruption? Again I know this says Galaxy S2, I'm just trying to get as much information as I can
Sorry for the double post, but I found this thread and I'm beginning to think that "nand erase all" might help. I have the official rom from samsung-updates for the vbrmf1 firmware. If I flash that while having the nand erase all checkbox checked does anything think that this would help me solve my problem? I read this thread: http://forum.xda-developers.com/showthread.php?t=1976695. There's also this thread that suggest the nand erase all: http://forums.androidcentral.com/sa...ot-flash-really-really-stuck-please-help.html.
If I do use nand erase, it'll be like the guide for soft bricking, but without flashing the bootchains. How necessary is it to flash those boot chains? Would I be able to try flashing them after I try flashing the stock rom? Or must the order of the soft brick thread by Hero an absolute?
Another question. What happens if I flash just a pit file without anything in the PDA section?
Okay, well I was able to get my recovery back after trying to flash my pit with the stock firmware checking nand erase all and repartition. In the end it failed because it said there was no pit partition.
However, now I'm unable to do a factory reset because it cannot mount system or cache. It also asks for a password when I first boot up the recovery. Anyone know what's going on?
nike t said:
Okay, well I was able to get my recovery back after trying to flash my pit with the stock firmware checking nand erase all and repartition. In the end it failed because it said there was no pit partition.
However, now I'm unable to do a factory reset because it cannot mount system or cache. It also asks for a password when I first boot up the recovery. Anyone know what's going on?
Click to expand...
Click to collapse
I just had all the issues you described on the latest TWRP when flashing a 4.4 ROM. Try the latest CWR. Format system and data using CWR 6.0.3.1
Sent from my SCH-I535 using Tapatalk
I tried CWR 6.0.1.2 and I was able to flash it, but I wasn't able to do a factory reset. It said that there was an error mounting /sdcard/.android_secure and it also says E format_volume: make_extf4fs failed on /dev/block/mmcblk0p17.
nike t said:
I tried CWR 6.0.1.2 and I was able to flash it, but I wasn't able to do a factory reset. It said that there was an error mounting /sdcard/.android_secure and it also says E format_volume: make_extf4fs failed on /dev/block/mmcblk0p17.
Click to expand...
Click to collapse
Use the latest version!
Sent from my SCH-I535 using Tapatalk
Alrighty, tried 6.0.4.3, no go. Thanks for all the help. I think the phone's done. It's gotta be some kind of nand problem. I'll probably send it in for JTAG or maybe try to transplant a motherboard from a different phone..
I've searched and searched for hours on this topic and still haven't had any luck, so maybe someone can tell me if my phone is recoverable. Here are the specifics.
At some point in the past (maybe ICS timeframe), I rooted my phone. I suspect that also unlocked my bootloader way back when because every time the phone booted, I'd see the unlock symbol and the word "custom".
Verizon just pushed out to me an OTA for 4.4.2. My phone was slow enough before, this didn't seem to improve it.
An acquaintance told me he had good luck with his Android phone performance by installing Cyanogenmod, so I figured I'd give that a try.
I started following the directions at the Cyanogenmod site (Install_CM_for_d2vzw).
After completing Step 5, the phone threw the "System software not authorized by Verizon" error.
I've tried all kinds of things, using Odin and trying to get back to something that will allow my phone to work.
Nothing has worked so far.
Running Windows 8.1 on my laptop. Drivers to talk to the phone seem good (must have worked enough to get me here).
Can anyone help at all? I'd be most grateful to get the phone to anything that will actually work.
mdesq said:
I've searched and searched for hours on this topic and still haven't had any luck, so maybe someone can tell me if my phone is recoverable. Here are the specifics.
At some point in the past (maybe ICS timeframe), I rooted my phone. I suspect that also unlocked my bootloader way back when because every time the phone booted, I'd see the unlock symbol and the word "custom".
Verizon just pushed out to me an OTA for 4.4.2. My phone was slow enough before, this didn't seem to improve it.
An acquaintance told me he had good luck with his Android phone performance by installing Cyanogenmod, so I figured I'd give that a try.
I started following the directions at the Cyanogenmod site (Install_CM_for_d2vzw).
After completing Step 5, the phone threw the "System software not authorized by Verizon" error.
I've tried all kinds of things, using Odin and trying to get back to something that will allow my phone to work.
Nothing has worked so far.
Running Windows 8.1 on my laptop. Drivers to talk to the phone seem good (must have worked enough to get me here).
Can anyone help at all? I'd be most grateful to get the phone to anything that will actually work.
Click to expand...
Click to collapse
Long story short, 4.3+ have permanently locked the bootloader beyond any current known XDA exploit. No AOSP once you have taken VRUCML1 4.3, VRUCNC1 4.3, and VRUDNE1 4.4.2 OTAs. Additionally, once officially on 4.4.2, you can not downgrade via Odin to 4.3. Being that this 4.4.2 OTA is new, there is not much in the way of resolving hard bricks for the 4.4.2. OTA.
My primary suggestion is to Odin flash this VRUDNE1 4.4.2 tar if you can boot into Download mode.
SlimSnoopOS said:
My primary suggestion is to Odin flash this VRUDNE1 4.4.2 tar if you can boot into Download mode.
Click to expand...
Click to collapse
Many, many, MANY thanks! That worked and I'm back in with a running phone.
mdesq said:
Many, many, MANY thanks! That worked and I'm back in with a running phone.
Click to expand...
Click to collapse
Glad that worked out for you!
Sent from my SCH-I535 using Tapatalk 4
I'm currently on the 4.4.2 ne1, but buggy and laggy. I tried factory reset. But still iffy, can I Odin the ne1 tar and it wipe the phone and start fresh?
theviper90210 said:
I'm currently on the 4.4.2 ne1, but buggy and laggy. I tried factory reset. But still iffy, can I Odin the ne1 tar and it wipe the phone and start fresh?
Click to expand...
Click to collapse
Yes, download VRUDNE1 tar from Sammobile.com or Samsung-updates.com and search for "sch-i535" and flash with Odin. The VRUDNE1 tar from these websites will wipe the phone clean.
(Edited wrong post)..Slimsnoopsos, thanks I'll do that!!!
SlimSnoopOS said:
Yes, download VRUDNE1 tar from Sammobile.com or Samsung-updates.com and search for "sch-i535" and flash with Odin. The VRUDNE1 tar from these websites will wipe the phone clean.
Click to expand...
Click to collapse
Slim, I downloaded the one from Sammobile.com and odin it and it completed sucessfull, phone booted back up not wiped!! it just re flashed 4.4.2 over my current 4.4.2, what did I do wrong to make it not wipe then flash? I want Wipe then reflash 4.4.2
SlimSnoopOS said:
Yes, download VRUDNE1 tar from Sammobile.com or Samsung-updates.com and search for "sch-i535" and flash with Odin. The VRUDNE1 tar from these websites will wipe the phone clean.
Click to expand...
Click to collapse
theviper90210 said:
Slim, I downloaded the one from Sammobile.com and odin it and it completed sucessfull, phone booted back up not wiped!! it just re flashed 4.4.2 over my current 4.4.2, what did I do wrong to make it not wipe then flash? I want Wipe then reflash 4.4.2
Click to expand...
Click to collapse
Ok also downloaded the one from samsung-updates.com and it also is a no wipe. So is there a ne1 tar, that will wipe before flashing?
theviper90210 said:
Ok also downloaded the one from samsung-updates.com and it also is a no wipe. So is there a ne1 tar, that will wipe before flashing?
Click to expand...
Click to collapse
Are you positive neither wiped your phone? How do you know they did not wipe your phone?
To answer your question, those websites are the two primary sources that supply stock tar files and their tar files have always wiped the phone on prior OTAs. No, I do not know of anywhere else to download them from. I guess you'll have to boot into recovery and do a factory reset from there. From a powered off state, hold: volume up, power, and home until it boots into recovery.
Positive, after both flashes phone booted right back into android with all my data still installed. No "setup wizard" just back to where I left off. And both times the flashes were successful. So weird
theviper90210 said:
Positive, after both flashes phone booted right back into android with all my data still installed. No "setup wizard" just back to where I left off. And both times the flashes were successful. So weird
Click to expand...
Click to collapse
And that's with:
-Odin 3.07
-auto reboot and f. reset are selected
-install the tar via the tab labeled "PDA"
-your S3 is fully booted into download mode (volume down, home, and power)
Correct?
It was Odin 3.09!?!
Tar via the ap tab (no PDA tab in 3.09)
These were the directions from the sites were the tar was. Could that really make a difference.
And yes in download mode. Odin will flash, reboot to the android with spinning stomach for a minute run a progress bar. Reboot into android and success. But no wipe?
---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------
Kinda like a dirty flash
theviper90210 said:
It was Odin 3.09!?!
Tar via the ap tab (no PDA tab in 3.09)
These were the directions from the sites were the tar was. Could that really make a difference.
And yes in download mode. Odin will flash, reboot to the android with spinning stomach for a minute run a progress bar. Reboot into android and success. But no wipe?
---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------
Kinda like a dirty flash
Click to expand...
Click to collapse
Download Odin 3.07 from here then let me know if this works. ONLY FLASH IN PDA. Do not flash in any other tab.
I'll have to try it when I get home from work. But I'll let u know thanks!!
theviper90210 said:
I'll have to try it when I get home from work. But I'll let u know thanks!!
Click to expand...
Click to collapse
That's cool, hope it helps out!
SlimSnoopOS said:
That's cool, hope it helps out!
Click to expand...
Click to collapse
Flash was success using 3.07 and PDA option, but still NO WIPE, phone booted normally with all data.
Here is the message data from odin. I dont notice any wipe command?
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl2.mbn
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> tz.mbn
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img.ext4
<ID:0/010> cache.img.ext4
<ID:0/010> NON-HLOS.bin
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The .tar files from Samsung are no wipe. They are exact copies of OTA including lock down.
prdog1 said:
The .tar files from Samsung are no wipe. They are exact copies of OTA including lock down.
Click to expand...
Click to collapse
That's a very surprising change from before
That's what I thought, so I just used kies and it will wipe and fresh install
Odin to Stock, Updating, Rooting, and Safestrap Guide
Post 1 - Odin and Guide Notes
Post 2 - Odin to Stock, Update, Rooting and Safestrap Guide
Post 3 - FAQs
Once you are rooted with Safestrap installed, the world is your oyster. Check out this thread...
[INDEX] All things AT&T [MK2 NB1 NC1 NI1 NJ4 NJ5 OC3 OC4 OK2 OK3] and ROM List
WARNING 1 -- ALL GUIDES BELOW WILL WIPE YOUR DEVICE. Make sure you have you data backed up before attempting.
WARNING 2 -- Follow these guide at your own risk. Everything worked for me, but... NOTHING IS 100% GUARANTEED.
Who is this guide for?
Anyone using an AT&T Galaxy S4 (SGH-I337) AND...
-- has the MF3, MK2, MLD, NB1, NC1, NI1, NJ4, NJ5, OC3, OC4, OK2, or OK3 bootloader
-- wants to return their phone back to stock.
-- was told to “Odin back to stock” in another thread.
-- thinks they bricked their phone
-- is bored and wants to start fresh before flashing another ROM.
Who SHOULD NOT use this guide?
-- SGH-I337 users with a MDB or MDL bootloader. (Don’t use this guide or you’ll be locked down for good.)
-- Anyone using another Galaxy S4 variant, such as T-Mobile, Verizon, i337m, etc...
-- Anyone using a Galaxy S4 Active. (You have your own forum here.)
-- Anyone who does not take the time to read the notes below and F.A.Q.'s in Post 2 before flashing.
ODIN NOTES
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. If you see 0:[COMn] (n = any number) then Odin can see your phone
2. Make sure Auto Reboot and F. Reset Time are the ONLY boxes checked
3. If the Odin tar is an "all in one", then it will go in the AP slot, otherwise, match them up with their appropriate locations
4. A successful restore will show the follow message... (file name in line 4 may be different)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
If you have any issues or Odin does not see your device...
1. Try a different USB cable
2. Try a different USB port on your PC
3. Uninstall Kies. (Kies sometimes interferes with Odin)
4. Download the latest drivers from the Samsung website here. (Uninstall the existing drivers from your PC, reboot, and then install the new drivers.)
5. Try a newer version of Odin. @sway8966 has posted Odin v3.10.6 in this post.
Linux Users
Please check out @userwaldo post for Using Heimdall on Linux to Flash NB1...
http://forum.xda-developers.com/gal...-stock-updating-rooting-t2926642/post65935022
Thank You
Thank you to all the members who have helped make this thread possible. From coming up with root and update methods to helping me with the install steps and files. Hopefully I got everyone. If I left you out, please PM me.
@muniz_ri
@Hashcode
@brownie9987
@Maribou
@Apoplectic1
@Homeboy76
@Kingxteam
@geohot
@k1mu
Odin to Stock, Updating, Rooting, and Safestrap Instructions
HOW TO GET TO ANY LOLLIPOP 5.0.1 (OC3, OC4, OK2, OK3) BASE
Can be performed from ANY base.
NOTES
1. Once you take the Lollipop update, you can go back to NB1.
2. If you want a STOCK or ROOTED lollipop base... Follow Steps 1 and 2
3. If you want ROOTED with RECOVERY lollipop (ie... ability to flash ROMs), follow Alternate method, instead.
STEP 1 - Odin to NB1 Stock
Files...
Odin -- Odin v3.09 -- XDA thread. Download from here.
Stock NB1 OTA -- I337UCUFNB1_4.4_Stock_Odin_tar -- from here.
Instructions
1. Power off phone
2. Boot into Download Mode
--- press and hold BOTH power and volume down buttons
--- when you see "Warning!" screen... release both buttons
--- press volume up to continue
3. Connect phone to PC via usb cable
on pc...
4. Extract .tar.md5 from Stock NB1 OTA file
5. Right click Odin and run "as administrator"
6. Click AP button and select extracted tar.md5 file
7. Click Start
8. Phone will reboot when complete
STEP 2 - Flash Updates in Stock Recovery
Files...
You will need the following update files from here...
NJ4_update_from_NB1.zip
OC3_update_from_NJ4.zip
OC4_update_from_OC3.zip (Optional)
OK2_update_from_OC4.zip (Optional)
OK3_update_from_OK2.zip (Optional)
Instructions...
1. Copy update zip(s) to your External SdCard
2. Unplug and power off phone
3. Boot into Stock Recovery
--- press and hold BOTH power and volume up buttons
--- when you see the blue "RECOVERY BOOTING..." message in the top left corner, release power button (phone may reboot)
--- when you see the android guy, release volume up button
4. Select "apply update from external storage"
5. Browse to location of NJ4_update_from_NB1.zip and select it
6. Phone will reboot when complete
7. Repeat steps using OC3_update_from_NJ4.zip file
8. For those wanting OC4 Base... repeat steps using OC4_update_from_OC3.zip file
9. For those wanting OK2 Base (after flashing OC4 base)... repeat steps using OK2_update_from_OC4.zip file
10. For those wanting OK3 Base (after flashing OK2 base)... repeat steps using OK3_update_from_OK2.zip file
You are now on the stock base of your choice. If you DO NOT want root, STOP here.
STEP 3 - Root
Kingroot -- XDA thread.
OC3 / OC4 --> Phone app version (V4.62_C133_B233)
OK2 / OK3 --> Desktop version
Instructions...
Install and run application. More information in Kingroot thread.
You are now rooted.
ALTERNATE - Rooted Lollipop and Safestrap Method
Update to I337_OC4 (or OC3) - 5.0.1 and KeepRoot
Starting with any rooted kitkat base, follow this method to flash a rooted OC3 or OC4 Stock ROM Base.
(Bootloader, Kernel, and Modem are also updated in the process)
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
For Safestrap Recovery and ROM Flashing, check out this great guide...
http://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
List of compatible ROMs can be found in Post #3 here...
http://forum.xda-developers.com/showthread.php?p=53758296
HOW TO GET TO ANY KITKAT 4.4.2 (NB1, NC1, NI1) OR 4.4.4 (NJ4, NJ5) BASE
NOTES
1. You can go back to NB1 from ANY BASE. (Yes... even if you took the OC4 update.)
2. After Odining the NC1 kernel to run Towelroot, WiFi won't work until you odin back the nj4 kernel. (Not an issue, as Towelroot still works with Mobile data.)
3. As long as you use Towelroot v3, you DO NOT need to mess with SELinux Mode Changer.
4. On some bases, after completing all the steps, the Safetrap app may force close if opened. Don’t worry, the Safestrap menu will continue to appear on reboot.
STEP 1 - Odin to NB1 Stock
Files...
Odin -- Odin v3.09 -- XDA thread. Download from here.
Stock NB1 OTA -- I337UCUFNB1_4.4_Stock_Odin_tar -- from here.
Instructions
1. Power off phone
2. Boot into Download Mode
--- press and hold BOTH power and volume down buttons
--- when you see "Warning!" screen... release both buttons
--- press volume up to continue
3. Connect phone to PC via usb cable
on pc...
4. Extract .tar.md5 from Stock NB1 OTA file
5. Right click Odin and run "as administrator"
6. Click AP button and select extracted tar.md5 file
7. Click Start
8. Phone will reboot when complete
You are now on STOCK NB1. If you DO NOT want any of the updates, STOP here.
STEP 2 - Flash Update(s) in Stock Recovery
Files...
Determine which base you want and download their respective file(s) from here...
NC1 --> NC1_update_from_NB1.zip
NI1 --> NI1_update_from_NB1.zip
NJ4 --> NJ4_update_from_NB1.zip
NJ5 --> NJ4_update_from_NB1.zip and then NJ5_update_from_NJ4.zip
Instructions...
1. Copy update zip(s) to your External SdCard
2. Unplug and power off phone
3. Boot into Stock Recovery
--- press and hold BOTH power and volume up buttons
--- when you see the blue "RECOVERY BOOTING..." message in the top left corner, release power button (phone may reboot)
--- when you see the android guy, release volume up button
4. Select "apply update from external storage"
5. Browse to location of update zip and select it
6. Phone will reboot when complete
7. NJ5 ONLY... repeat steps using NJ5_update_from_NJ4.zip
You are now on the stock base of your choice. If you DO NOT want root, STOP here.
STEP 3 - Root and Install Safestrap
Files...
Towelroot v3 -- tr.apk -- from here.
Safestrap v3.72 -- Safestrap-JFLTE-3.72-kk-B01.apk -- from here.
Your base kernel and NC1 kernel from here because Towelroot ONLY works with NC1...
NB1 --> NB1_kernel.tar.md5 and NC1_kernel.tar.md5
NC1 --> no kernels needed (skip steps 2 - 5 and 10 - 12 below)
NI1 --> NI1_kernel.tar.md5 and NC1_kernel.tar.md5
NJ4 --> NJ4_kernel.tar.md5 and NC1_kernel.tar.md5
NJ5 --> NJ5_kernel.tar.md5 and NC1_kernel.tar.md5
Instructions for Rooting...
1. Upload Towelroot and Safestrap zip onto External SDcard
2. Reboot into Download Mode
3. In Odin, flash NC1 Kernel file in the AP slot
4. Phone will reboot
5. Go into Settings > More > Security
--- check "Unknown sources"
--- uncheck "Verify apps"
6. Open My Files app, browse to Towelroot v3, click it, and install.
7. Open Towelroot and click make it ra1n
You are now rooted. If you DO NOT want to install safestrap, skip to #10.
Instructions for Installing Safestrap Recovery...
8. Open My Files app, browse to Safestrap v3.72, click it, and install.
9. Open Safestrap and click Install Recovery
10. Reboot into Download Mode
11. In Odin, and flash you base kernel file in the AP slot
12. Phone will reboot when complete
All Done. You are now ready to flash a KitKat ROM.
See Post 4 in the Index for list of compatible ROMs and installation instructions.
***When flashing ROMs, use the respective modules that match your base. (ie - NJ5 base users, use ATT_NJ5_modules)***
HOW TO GET TO JELLY BEAN 4.3 (MK2) BASE
NOTES
You can go to MK2 from MLD, MK2, and earlier. Once you flash NB1, you CANNOT go back to MK2.
STEP 1 - Odin to MK2 Stock
Files...
Odin -- Odin v3.09 -- XDA thread. Download from here.
MK2 OTA -- I337MK2_Combined_Odin_Tar -- from here.
Instructions...
1. power off phone
2. boot into Download Mode
--- press and hold BOTH power and volume down buttons
--- when you see "Warning!" screen, release both buttons
--- press volume up to continue
3. connect phone to PC via usb cable
on pc...
4. extract .tar.md5 from MK2 OTA .rar file
5. Right click Odin and run "as administrator"
6. click AP button and select extracted .tar.md5 file
7. click Start
8. Phone will reboot when complete
You are now on STOCK MK2. If you DO NOT want root, STOP here.
STEP 2 - Root and Install Safestrap
Files...
Saferoot -- saferoot.zip -- from here.
Safestrap v3.71 -- Safestrap-JFLTEATT-3.71.apk -- from here.
Instructions for Rooting...
on phone...
1. Go to Settings > More > About Phone... Tap Build Number repeatedly until developer mode is enabled.
2. Go to Settings > More > Developer Options... Enable USB debugging
3. Connect phone to PC
on pc...
4. On PC, unzip saferoot.zip, and browse to folder.
5. Run install.bat and follow prompts. (phone will reboot)
You are now rooted. If you DO NOT want to install safestrap, STOP here.
Instructions for Installing Safestrap Recovery...
1. Copy safestrap file to extSdCard
Open My Files app, browse to Safestrap-JFLTEATT-3.71.apk, click it, and install.
2. Open Safestrap and click Install Recovery
All Done. You are now ready to flash a Jelly Bean ROM. See Post 3 in the Index for list of compatible ROMs and installation instructions. Make sure to use the MK2 modules.
To run KitKat ROMs... Install Safestrap 3.72 instead of v3.71 and see Post 2 in the Index for KitKat ROM install instructions. After installing a KitKat ROM, remember flash the MLD modules. (To make KitKat ROMs possible, the Magic Tool flashes the MLD kernel.)
FAQs
What is ODIN?
Odin is a 3rd party program that can restore your phone to factory settings.
Do I need to take my SIM and SdCard out?
If you follow the directions and everything goes as it should, neither your SIM or SdCard will be affected. I, personally, leave both in and have never had an issue. Worst thing that can happen is you loose the data on your SdCard and/or you need to go to ATT for a new SIM card... Your call.
What is the difference between these instructions and the ones found in other threads?
Some are the same and the others might use different files. I'd like to think they are more detailed than some of the others out there. Besides, These are the steps I used and I know they work.
I have a different tar file. Can I use that one instead?
Sure. It's your phone, you can do whatever you want... But if you have problems, don't look at me for help. These instructions are specific to the files I have referenced. Different tar files may yield unexpected results.
I’m on MDB or MDL base, why no love for us?
You have an bootloader which can be loki'd to flash any kernel. If you follow any of the directions above, your bootloader will be permanently locked and you will be stuck with stock kernel.
I bought my phone on MF3 and have no experience with loki or your bootloader. I only post what I know from personal experience. I suggest you look in this thread for more info... http://forum.xda-developers.com/showthread.php?t=2314494
I took the NB1 OTA, can I Odin the MK2 files?
No. Once you take the NB1 update, you cannot go back to MK2.
I took one of the Lollipop Updates, can I Odin the NB1 files?
Yes. You can odin NB1 from ANY base. Yes... Even the Lollipop bases.
Which recoveries can we use?
If you are on MK2, NB1, NC1, NI1, NJ4, or NJ5 base, then you have a locked bootloader. SAFESTRAP is the ONLY recovery you can use.
Lollipop bases need a work around to use Safestrap. More info can be found in one of the install instruction links here...
http://forum.xda-developers.com/showpost.php?p=53758296&postcount=3
What about those of us on MF3 that want to odin back to MF3 stock?
Sorry, but there are not too many of you left. I may add your steps at a later date, but for now, these links may help you out...
-- Odin file -- http://forum.xda-developers.com/showthread.php?t=2504311
-- Root steps -- http://forum.xda-developers.com/showthread.php?t=2387577
-- Safestrap v3.65 -- http://forum.xda-developers.com/showthread.php?t=2448925
Will these instructions work on a Mac?
No. Odin is specific for Windows. There is a mac version called “Jodin”, but I have never had any luck flashing large files with it. More info can be found here... http://forum.xda-developers.com/showthread.php?t=2598203
I'm rooted with Safestrap recovery installed. Now what?
Start here... http://forum.xda-developers.com/showthread.php?t=2616221 or one of the other excellent threads in the ATT Galaxy S4 Forums on XDA
Thanks @guut13. A much needed guide here
Sent from my Nexus 5 using XDA Free mobile app
Thanks
This is a very helpful tutorial, been looking into all of my options since I picked up my s4,it's on 4.2.2 with the mf3 build. This will hopefully get my phone up to nc1 or ni1. Not sure what build I want yet, gotta check out which has the roms I want to check out... Also need to charge my phone a bit but will try this method out in a little while. I'll let you know how it goes in a later update.
Hey guys,
I believe I bricked my phone. I had an AT&T Samsung Galaxy S4 SGH-i337 NC1 build. I now have a brick.
Below is a conversation I've been having about getting my phone working again.
If NEbuddy can help I am desparate. My biggest need is to get the Nandroid backup working , that I made right before this bricking happened. As you can see I need to get the Nandroid backup working or I'd get it fixed back to stock by Best Buy.
If this is confusing please take the time to message me or write in this thread.
As you can see most of this is background. Right now I'm stuck at using Odin v3.09 to get back to stock NB1. Then I can follow the instructions above.
TIA and please read the information below.
************************************************************************************
Basically, the process is simple. First let's start off by getting some information...
Head over to Settings --> More --> About Device
What is your Baseband?
What is your Build Number
************************************************************************************
Hi N,
Baseband version i337UCUFNC1
Build number KOT49H.I337UCUFNC1
J
************************************************************************************
BTW I'm rooted with 3.45gb on sd card and 6.50 on external sd card free space. Also have d/l of Graviton ROM. Also have safestrap installed and super su, Busybox, se linux mode changer, Secure settings.
************************************************************************************
Since your rooted, have Safestrap installed, and such it's fairly straight forward...
1. Put the Graviton ROM's zip file onto the external SD
2. Put the NC1 Modules zip file onto the external SD
3. Put the SuperSU zip file onto the external SD
4. Reboot into Safestrap, go to Wipe and wipe everything but external SD.
5. DO NOT REBOOT OR EXIT SAFESTRAP
6. Hit the back arrow to go back to the SS main menu, hit install.
7. Select the Graviton ROM zip file (you made need to navigate to the SD card)
8. Flash it
9. Do not reboot yet.
10. Flash SuperSU, and the NC1 Modules.
11. Reboot, set APN's,etc.
If any of those steps fail your need to use Odin to restore your device back to stock. So I advise backing up BEFORE doing this.
***************************************************************************************
Hey there,
How do I make another Nandroid backup first. I have a Nandroid backup of the stock rom after I rooted. I forget how to make the backup. I think I used Safestrap to backup but I don't remember. That's what has been keeping me back from flashing a rom, as I worry that I something will go wrong and I have no current backup.
J
****************************************************************************************
Inside Safestrap go to Backup, follow the instruction on the screen and let it do it's thing. Afterwards plug the device into a PC and copy the TWRP folder off the external SD onto the PC itself.
******************************************************************************************
Hi N,
Sorry for the repeated posts, but I'm trying to solve what I can. I found the instructions on how to Odin back to stock. The first file I need is Odin v3.09. I can't find this file to download. I wonder if it may be my browser. I'm using Chrome on a Windows 8.1 machine. IDK how to get the file.
Thank you,
J
******************************************************************************************
https://www.dropbox.com/s/1mujevgk0b...Odin-v3-09.zip
Your need to install Samsung Kies to get the proper drivers.
http://downloadcenter.samsung.com/co.../KiesSetup.exe
Follow the instructions here...
http://forum.xda-developers.com/show...34&postcount=6
********************************************************************************************
Hi, N
I grabbed the Odin file and followed the thread here http://forum.xda-developers.com/gala...oting-t2926642. Also ran the Kies driver install. But Odin just hangs and displays "Not responding."
I'd like to throw a few buck your way so maybe we can finish this up someway and I can do that.
Thank you,
J
********************************************************************************************
There really isn't anything I can do to help you further. Do remember that the entire process of modifying your device is "at your own risk". I haven't encountered any of these problems with Odin, Safestrap, etc. - If your device is bricked now your best bet may be to take it to a Samsung agent at your local Best Buy and they should be able to restore it to stock condition. The only feasible way I see to help further would be a session on Skype (via chat or microphone) and use of a remote access to your PC (you'd retain full control). The only issue with this is being online at the same time. Other then that I'm afraid you've hit a brick wall, keep trying... and post in the forum and perhaps others can help you solve the issues with Odin.
*********************************************************************************************
I was wondering if there is anything I can do with my Nandroid backup I made? What do you think?
J
*********************************************************************************************
If and when you get your device successful modded you can hang onto it to restore if anything goes wrong. As I said in the last message keep researching around the forum and especially this thread. Thanks for the donation, it was really generous and definitely will help me out in these tight times. If you have any other questions feel free to ask and I'll try my best to answer them in a quick manner.
************************************************************************************************
What issues are you having with Odin? Have you downloaded the nb1 file and extracted it? You should have a .tar.md5 file, user that in Odin AP slot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What issues are you having with Odin? Have you downloaded the nb1 file and extracted it? You should have a .tar.md5 file, user that in Odin AP slot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
*********************************************************************************************************
I grabbed the Odin file and followed the thread here http://forum.xda-developers.com/gala...oting-t2926642. Also ran the Kies driver install. But Odin just hangs and displays "Not responding."
*********************************************************************************************************
Did I maybe screw up the Kies Install?
Revitupmx5 said:
*********************************************************************************************************
I grabbed the Odin file and followed the thread here http://forum.xda-developers.com/gala...oting-t2926642. Also ran the Kies driver install. But Odin just hangs and displays "Not responding."
*********************************************************************************************************
Did I maybe screw up the Kies Install?
Click to expand...
Click to collapse
Google Odin 1.85 xda. Try that
Edit, does your device show up in device manage when is connected?
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
jd1639 said:
Google Odin 1.85 xda. Try that
Edit, does your device show up in device manage when is connected?
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Click to expand...
Click to collapse
Under Control Panel, Device Manager there is an entry under Universal Serial Bus Controllers, entry is Samsung Mobile USB CDC Composite Device
That's what I see.
Also under Windows Explorer my phone doens't show up anymore since bricked.
Revitupmx5 said:
Under Control Panel, Device Manager there is an entry under Universal Serial Bus Controllers, entry is Samsung Mobile USB CDC Composite Device
That's what I see.
Also under Windows Explorer my phone doens't show up anymore since bricked.
Click to expand...
Click to collapse
Ok try Odin 1.85. As long as the device shows up in that you'll be ok
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
jd1639 said:
Ok try Odin 1.85. As long as the device shows up in that you'll be ok
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Click to expand...
Click to collapse
I grabbed Odin v1.85 but there are so many different settings from Odin v3.09 that I don't know where to start. Can you make up a short list of settings fo use for the AT&T Samsung Galaxy S4 SGH-i337 NC1. Actually I don't think the build matters anymore since I bricked it.
TIA
---------- Post added at 07:40 PM ---------- Previous post was at 07:07 PM ----------
jd1639 said:
What issues are you having with Odin? Have you downloaded the nb1 file and extracted it? You should have a .tar.md5 file, user that in Odin AP slot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This may sound lame but I can't extract the tar file from the rar. Can you suggest a good program to extract the tar file.
Revitupmx5 said:
I grabbed Odin v1.85 but there are so many different settings from Odin v3.09 that I don't know where to start. Can you make up a short list of settings fo use for the AT&T Samsung Galaxy S4 SGH-i337 NC1. Actually I don't think the build matters anymore since I bricked it.
TIA
---------- Post added at 07:40 PM ---------- Previous post was at 07:07 PM ----------
This may sound lame but I can't extract the tar file from the rar. Can you suggest a good program to extract the tar file.
Click to expand...
Click to collapse
Success getting Odin to run using Odin v3.09. Below is t the log from Odin. As you see the result is a FAIL.
Is there something I need to do now? I've followed all the instructions up to getting phone to reboot into NB1.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Revitupmx5 said:
Success getting Odin to run using Odin v3.09. Below is t the log from Odin. As you see the result is a FAIL.
Is there something I need to do now? I've followed all the instructions up to getting phone to reboot into NB1.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Odin is not seeing your phone. Is your phone in download mode?
If so, try using a different usb cable or port on your pc. If still not working, you may need to delete the samsung drivers from your pc and reinstall.
AT&T I337 Odin Keeps Failing Need Stock. HELP??
When the I try to flash my phone with odin, I end up getting:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what version of odin are the file I am flashing I get this error. And a little progress bar shows up on my phone.
My phone is not working at all. I put hyperdrive rom on my phone but it had some issues so I needed to go back to stock. But when I tried to use kies to get me to stock, it gave me an error and now I have a "Firmware upgrade encountered an issue." It is stuck at download mode. Can someone help with this.
Beydt said:
When the I try to flash my phone with odin, I end up getting:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what version of odin are the file I am flashing I get this error. And a little progress bar shows up on my phone.
My phone is not working at all. I put hyperdrive rom on my phone but it had some issues so I needed to go back to stock. But when I tried to use kies to get me to stock, it gave me an error and now I have a "Firmware upgrade encountered an issue." It is stuck at download mode. Can someone help with this.
Click to expand...
Click to collapse
What base were you on and which file are you trying to flash in Odin?
guut13 said:
What base were you on and which file are you trying to flash in Odin?
Click to expand...
Click to collapse
I believe I was on NC1 but don't quote me on that. I was told to flash the NB1. I been given the links to your posts, so the files that you provided.
Revitupmx5 said:
Success getting Odin to run using Odin v3.09. Below is t the log from Odin. As you see the result is a FAIL.
Is there something I need to do now? I've followed all the instructions up to getting phone to reboot into NB1.
Click to expand...
Click to collapse
Beydt said:
I believe I was on NC1 but don't quote me on that. I was told to flash the NB1. I been given the links to your posts, so the files that you provided.
Click to expand...
Click to collapse
I've updated the OP with a Odin notes and screenshot section. See if that helps.
guut13 said:
I've updated the OP with a Odin notes and screenshot section. See if that helps.
Click to expand...
Click to collapse
The download for odin 3.09 does not work. The thread also has no download link. Is their another link you trust or would this link work: http://odindownload.com/
I just want to be completely sure and safe. I just want to fix up my phone so I can use it as soon as possible.
Beydt said:
The download for odin 3.09 does not work. The thread also has no download link. Is their another link you trust or would this link work: http://odindownload.com/
I just want to be completely sure and safe. I just want to fix up my phone so I can use it as soon as possible.
Click to expand...
Click to collapse
Thanks for the heads up. Yeah, once the XDA page pulled their download link, I was hesitant to trust 3rd party sites. Pushed my copy up to AFH. Link is fix. Try again, please.
Hey guys,
I've been trying to figure this out for about the last 8 hours and have been hitting brick wall after brick wall.
I accidentally deleted all my system files on my phone when trying to install a new rom. I can no longer access TRWP recovery. Whenever I do I get the firmware upgrade encountered an issue error. I have plugged the phone into my computer but Kies can't connect to it. I have tried to reinstall 5.0 and I get sw rev check fail aboot fused 2 binary 1 error. I am currently downloading 4.4.2 to hope that this will work but I'm not sure on what to do now. Any help would be greatly appreciated.
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Ramer said:
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Click to expand...
Click to collapse
Downloading it right now. Will let you know what happens when I try to install it
kevorski said:
Downloading it right now. Will let you know what happens when I try to install it
Click to expand...
Click to collapse
I know I shouldn't have to ask this, but being as it's happened once before, I'm making an assumption that since you posted on a Sprint forum, you are on the Sprint network?
Ramer said:
I know I shouldn't have to ask this, but being as it's happened once before, I'm making an assumption that since you posted on a Sprint forum, you are on the Sprint network?
Click to expand...
Click to collapse
Yeah I'm on Sprint. Funny that you would have to ask that question
Ramer said:
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Click to expand...
Click to collapse
So I downloaded the image and tried to flash it.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is the error I get when trying to flash it. Any ideas?
kevorski said:
So I downloaded the image and tried to flash it.
This is the error I get when trying to flash it. Any ideas?
Click to expand...
Click to collapse
Which OS are you running on PC? Also, use an MD5 checker to confirm good download.
Ramer said:
Which OS are you running on PC? Also, use an MD5 checker to confirm good download.
Click to expand...
Click to collapse
Windows 7 64bit I ran a checksum and they match
kevorski said:
Windows 7 64bit I ran a checksum and they match
Click to expand...
Click to collapse
I suspect I left out an important step, you need to be on the OA6 firmware to to install a lollipop rom and you may have wiped yours out. Odin this file, it's the OA6 firmware and KT TWRP.
Before you do this, if you have an extSD, this is the link for MOAR, you can try any rom you want, but let's attempt to get you going on a rom I'm familiar with. You need to copy the rom to your extSD beforehand. Download link is about half way down to OP.
So, to recap:
1. Download and copy MOAR to extSD and put back in your phone.
2. Odin OA6 firmware with TWRP. (Turn off auto-reboot, as you don't have a system to boot into)
3. After it PASSES, unplug from PC and pull the battery. Wait a few seconds and put battery back in and go into recovery mode (Volume UP, Home and Power).
4. If all goes well, TWRP is loaded and you can now navigate to you extSD and flash MOAR. (Clean install etc and remember, first boot can take about 20 minutes.
Ramer said:
I suspect I left out an important step, you need to be on the OA6 firmware to to install a lollipop rom and you may have wiped yours out. Odin this file, it's the OA6 firmware and KT TWRP.
Before you do this, if you have an extSD, this is the link for MOAR, you can try any rom you want, but let's attempt to get you going on a rom I'm familiar with. You need to copy the rom to your extSD beforehand. Download link is about half way down to OP.
So, to recap:
1. Download and copy MOAR to extSD and put back in your phone.
2. Odin OA6 firmware with TWRP. (Turn off auto-reboot, as you don't have a system to boot into)
3. After it PASSES, unplug from PC and pull the battery. Wait a few seconds and put battery back in and go into recovery mode (Volume UP, Home and Power).
4. If all goes well, TWRP is loaded and you can now navigate to you extSD and flash MOAR. (Clean install etc and remember, first boot can take about 20 minutes.
Click to expand...
Click to collapse
I still get the same error as above.
kevorski said:
I still get the same error as above.
Click to expand...
Click to collapse
Shoot. Sorry I'm out of ideas Maybe someone else can help?
Some other thoughts, Try updating your Samsung drivers. Reboot your PC. (Actually, try that first) Try a different USB port and a different cable. Make sure you see the blue COM:ID button in Odin.
Ramer said:
Shoot. Sorry I'm out of ideas Maybe someone else can help?
Some other thoughts, Try updating your Samsung drivers. Reboot your PC. (Actually, try that first) Try a different USB port and a different cable. Make sure you see the blue COM:ID button in Odin.
Click to expand...
Click to collapse
Hey Ramer,
Just wanted to let you know that I took the device to someone that does this for a living and found out that I had fried my bootloader. Didn't know if you wanted to know about the status. I have it up and running now with it rooted and running lollipop. Thanks for all the help that you provided.
kevorski said:
Hey Ramer,
Just wanted to let you know that I took the device to someone that does this for a living and found out that I had fried my bootloader. Didn't know if you wanted to know about the status. I have it up and running now with it rooted and running lollipop. Thanks for all the help that you provided.
Click to expand...
Click to collapse
Good to hear, but slightly confused. The bootloader (firmware) can be odin'd and if you installed the full OD3 stock tar it would have been included. Regardless, glad you're up and running.
Well now after I did a backup of the stock rom the guy put on it is locked up...again.