[Q] [Urgent] Can't unroot i337 MDL version via Odin - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I have the AT&T Samsung Galaxy S4 i337 with MDL firmware and I needed to flash back to the stock ROM to bring to AT&T to fix an unlocking issue. I googled and found two top guides and a video where they all did the same thing so I thought it was safe to follow it--the guides did not specify that I needed to use a specfic firmware even if it's an AT&T variant (I assumed all AT&T variants had the same firmware and so did the guides apparently) so I think I used the wrong PDA on Odin 1.85 and now I get the issue "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I can no longer boot the device even to my custom ROM.
How do I fix this and then be able to flash back to stock so I can return it to AT&T? Some guides required a PIT file along with the PDA, some required both PIT and bootloader along with the PDA, and some just required PDA. Which ones am I required for my purpose and where do I get them? (I went to several sources after googling and they offered different ones).
Here's my Odin 3.07 output:
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
I will be checking back on this thread every chance I can get--this problem needs to be fixed by Monday because I desperately need it for work. Thank you!

I'm going to try to help you out. Bear in mind that I do not currently have this phone, and have very little actual experience with it.
I don't know you experience level. Did you perform a wipe data/factory reset from within recovery before the first time you flashed the stock firmware? If not, can you now enter recovery? If so, perform a wipe data/factory reset and see if the phone will then boot into system. If you can boot into recovery, but the wipe data/factory reset does not resolve the issue, please make note of the details of the recovery. It will tell you which version and we need to know that.
The MDL firmware is the second stock firmware distribution on the SGH-I337 (MDB was first) and was able to be cracked with Loki, by-passing the bootloader to allow installation of custom kernels. All subsequent stock firmware distributions, MF3, MK2, MLD, NB1, NC1, NI1, NJ4, or OC3 are locked, allowing only the stock kernel. So the first important question is what exactly did you flash onto the phone on the first try?
If you flashed the stock MDL firmware, it would be something like I337UCUAMDL, then your boot loader is still by-passable. However, if you flashed any of the subsequent stock distributions, then you will have a locked boot loader. So it's very important to know exactly what was done so far so that the recovery attempt can be done correctly.
I'll need this information, and anything else you can think to tell me, to give you further advice.

Related

[Q] hyperdrive rls12 install problems

Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
The kernel message was no problem for me.using safe strap?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
rugmankc said:
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
Click to expand...
Click to collapse
Thank you both for your replys, your help is very much appreciated.
So I wiped it with recovery not aroma.
Carrier is Fido (Rogers subsidiary)
Phone is Canadian S4 variant (SGH-I337m) I believe it is the same as i337 (The m being a canadian designation) but don't quote me on that.
I was under the assumption that Canadian s4 Didn't need lokidoki.
Can you elaborate on safestrap?
No matter what I try it goes boots to download mode. Even if I plug it in to charge not pressing any power button.
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
SelfElevated2 said:
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
Click to expand...
Click to collapse
I believe that my phone's bootloader is unlocked (as with most other jtflecan models), but again don't quote me. As a result I have never used safestrap. Should/could I still use it if my bootloader is unlocked?
SelfElevated2 said:
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
Click to expand...
Click to collapse
It seemed that way as that was the only error, and aroma proceeded through. First time I tried without the ATT compatibility pack, no go, then with and still no go. Then i tried with a few kernels and same thing.
SelfElevated2 said:
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
Click to expand...
Click to collapse
I transitioned from cwm to philz for ntfs capability as my external sdcard is ntfs. I remember reading somewhere that autoloki was not included and some have complained about it so im not sure if it was added in a later build. In any case I just tried flashing twrp and got a mushy brick.
Now Im curious if I should restore to original and use safestrap or what as my phone does nothing but odin mode.
As always thanks for your valued input.
Your boot loader is definitely not locked. If it was you wouldnt have a custom recovery. So you don't need safestrap. Just restore and reroot and get a recovery. What you put on your phone after that is up to you. I know hyperdrive wouldn't boot for me with most kernels it was just stuck on the splash screen. But it booted for kt kernel. I would honestly find another Rom if I was in the same position
MINI UPDATE:
Phone was bootlooping so I tried to restore to stock 4.2.2 but ODIN failed continuously. Tried 4.3 stock (mk6) and odin failed, tried older odin and succeeded but it bootlooped and went to the kies upgrade error. Tried multiple Computers (2PC 1OSX) multiple ports and cables and all failed.
Trying to figure this out but not much help out there with regards to canadian s4, att guides ok? any suggestions? trying kies restore now but kies hangs after it downloads firmware. urgh
ODIN Outuput:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
ODIN seems to fail at different points, sometimes in recovery, or modem or etc.
do i need to repartition?if so where do i find the pit file for my device?
im reading that im screwed and praying its not true.
Thanks for any help
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
SelfElevated2 said:
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
Click to expand...
Click to collapse
no i only get odin.
phone only turns on when plugged in to usb on pc, otherwise unresponsive to hardkeys.
Every instance of ODIN flashing fails. No matter which firmware or computer i used, either write failure or PIT failure. both of which im attributing to an incomplete flash, and its making me think that the partition tables are chewed.
im stumped and phonless
any idea what that app was called? google yields no results
thanks for your help
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
SelfElevated2 said:
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Click to expand...
Click to collapse
Thank you very much for that link. It summed up everything i have been reading for the past 24 hours, but alas i have yet to figure out which pit to use, whether I can use the att pit, wind (different provider, uses aws (2 different frequencies from gsm standard) as opposed to gsm although they may have changed that recently),find a rogers pit, since they and fido are essentially the same network or continue searching for a fido pit.
Knowing what the pit does, would it really be carrier specific (asides from the difference in radios between fido/rogers and wind)? Is it ROM version and android version specific?
Update:
-Have Tried all options for recovery in KIES on multiple Pcs and Multiple Macs
-Download/Odin Mode Reads:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224,1440]
BAR [240,1440​
Questions:
Before this whole fiasco ODIN didnt show KNOX. I assume thats from the 4.3 revert i tried?
Does Write Protection have anything to do with it? I do recall being able to odin flash with this before.
eMMC Burst is new to me, havent seen this before
BAR pops up before failing but not seconds before, maybe a minute before.
Still Stumped
Edit: Even if i were to find the pit file, i cant seem to find modem, csc, and bootloader to add to odin. (unless they are all combined in that md5 file) so i wouldnt be able to flash until having all the necessary items as pit rewrites the partitions and all data is lost.
i also remembered one odd thing, may or may not apply here, but just before flashing to hyperdrive, i was not able to properly format. it would take a few tries to format data or whichever for example, before files were actually gone.
tried reverting to MDJ got vibrate loop
trying again to MK6
The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
d9vabder said:
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
Click to expand...
Click to collapse
What variant do you have?
So I figured out my problem. In TWRP recovery, I went to mounts, and mounted my micro SD card. It was mounted to internal memory and I guess that was screwing up flashes. Hope this works for you too!
Sent from my SAMSUNG-SGH-I337 using xda premium

please help before I brick it

good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help
Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I
..
fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!
Try this
..
fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know
Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.
Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!
..

Soft Brick G900V using Odin Stuck in Recovery Mode

My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
j0mz said:
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
Click to expand...
Click to collapse
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
j0mz said:
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
Click to expand...
Click to collapse
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
simplepinoi177 said:
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
I tried it but Odin cant find it. Its a rar file?
Stuck in recovery mode loop. SM-G900V Verizon G900VVRU2BOG5
Im in the exact same situation... i have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU.
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
Veid71 said:
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
Click to expand...
Click to collapse
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
Click to expand...
Click to collapse
ah okay i see then his post was kinda confusing
I don't know how to do that ODIN stuff, is there a video guide out or something?
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
Click to expand...
Click to collapse
I have no idea what any of this means. Please, can you help me?!
m0bk3yn1nj4 said:
I don't know how to do that ODIN stuff, is there a video guide out or something?
Click to expand...
Click to collapse
m0bk3yn1nj4 said:
I have no idea what any of this means. Please, can you help me?!
Click to expand...
Click to collapse
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
landshark68 said:
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
Click to expand...
Click to collapse
Much obliged
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
rachelrgr said:
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
Click to expand...
Click to collapse
You can grab the stock firmware, either OG5. OK3, or PB1 (newest), and flash with odin in the AP slot, I also recommend grabbing the PIT file (goes in the PIT slot). If you want root, then just go ahead and grab the PB1 and follow the directions on this link.
Firmware Link: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370

Help: Galaxy S4 sgh-i337 AT&T . Trying to install a different ROM

Ok, making some progress after 10 hours digging it. kind fun to see how this makes me look dumb.
I want to install a new ROM on my sgh-i337 . I rooted the motha foka, tried to install a different ROM with Odin and somehow it crashed.
I was trying to install ( is this even the word?) the old OS back and it wasn't working. I switched the USB port ( comon, what da fuu!) and it finally restored the phone.
Great. Now that I know how to undo the sheet, I want to try something better ( yeah... again, next level stupidity.).
I can't install twrp (twrp-3.0.2-0-jfltexx.img.tar to be more specific) thru Odin , it fails
( <ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth) )
So I was thinking about installing I337UCUAMDB_I337ATTAMDB_ATT.zip, trying to install twrp again with Odin ( aparrently that's the problem right?) to finally follow this guide ( [www cyanogenmods .org/forums/topic/update-galaxy-s4-att-nougat-7-0-aosp-rom )
and get my phone to survive a few more years ( at this point is just easier to buy a new one).
I appreciate any help !!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
""
If the phone has a 4.3 or newer bootloader, you can't install TWRP because the bootloader is now locked. No TWRP mean no custom ROM that needs TWRP for installation.
audit13 said:
If the phone has a 4.3 or newer bootloader, you can't install TWRP because the bootloader is now locked. No TWRP mean no custom ROM that needs TWRP for installation.
Click to expand...
Click to collapse
Hi, i have a GS4 i337 att, with android 4.4.4, what options i have to flash a custom rom, or upgrade to 5 and root. Sorry im new with GS4. Thanks in advance
You cannot flash any roms from Sammobile.com using Odin now that that the phone has a locked bootloader.
I would run ota updates until the phone is running the latest ROM. After that, I would consider rooting, installing safestrap, and a custom ROM that can be installed from safestrap.
audit13 said:
You cannot flash any roms from Sammobile.com using Odin now that that the phone has a locked bootloader.
I would run ota updates until the phone is running the latest ROM. After that, I would consider rooting, installing safestrap, and a custom ROM that can be installed from safestrap.
Click to expand...
Click to collapse
rooting using what method? safestrap can be installed on the latest ota update(OK3 afik)? And will using safestrap, to install a new rom, leave your old rom in place so that both are taking up space on the phone?
@valavicius yeah, samsung/att really f*ed us all when they locked the bootloader, and then released a new firmware that locked it down even further. If you're lucky and you have a really early firmware that's never been updated or the i337m you're still good to go, though.
I don't think Samsung is to blame for locked bootloaders. I believe it is something requested by AT&T. AT&T, Verizon, and Sprint as they are are the only carriers that have phones with locked bootloaders. Furthermore, AT&T never locked the bootloader until 4.3 where as all other carriers have updated via OTA to 5.01 without ever locking the bootloader.
audit13 said:
You cannot flash any roms from Sammobile.com using Odin now that that the phone has a locked bootloader.
I would run ota updates until the phone is running the latest ROM. After that, I would consider rooting, installing safestrap, and a custom ROM that can be installed from safestrap.
Click to expand...
Click to collapse
Hello,
Sorry for my poor english. I have sgh-i337 at&t with android 5.0.1, with bootloader OC4 so I think is locked. As I understood I can flash my phone only ROMs which can be flash by safestrep. Is thay mean I don't need unlock bootloader? And what is ota? Do I need update it? And Can you recommend some ROM with polish (europe) language?
Regards
Jactra
You can only flash roms with safestrap and you do not need to unlock the bootloader. The bootloader cannot be unlocked and I don't recommend using any software to try and unlock it because it could brick the phone.
OTA means over-the-air.
I don't know which ROM will have Polish so you'll have to check the ROM forum for the ATT S4.
audit13 said:
I don't think Samsung is to blame for locked bootloaders. I believe it is something requested by AT&T. AT&T, Verizon, and Sprint as they are are the only carriers that have phones with locked bootloaders. Furthermore, AT&T never locked the bootloader until 4.3 where as all other carriers have updated via OTA to 5.01 without ever locking the bootloader.
Click to expand...
Click to collapse
You are correct..AT&T, and Verizon have locked bootloaders..
sent from my SGH-M19something or another..its really my SM-S975L running a T-Mobile custom ROM
audit13 said:
You can only flash roms with safestrap and you do not need to unlock the bootloader. The bootloader cannot be unlocked and I don't recommend using any software to try and unlock it because it could brick the phone.
OTA means over-the-air.
I don't know which ROM will have Polish so you'll have to check the ROM forum for the ATT S4.
Click to expand...
Click to collapse
Thank you for your reply. So do you think I can without any risk of brick my phone flash it for example by this guide (part for safestrap)?
https://forum.xda-developers.com/galaxy-s4-att/development/guide-to-install-custom-rom-i337-att-t3483736
And one question: If I have OC4 do I have to flash with files kernel, modules and firmware OC4 or I need only install chosen ROM (SuperWizCyan)?
I don't have the AT&T sgh-i337, I have the sgh-i337m which is the Canadian version of the s4 with an unlocked bootloader; therefore, I can't comment on the safestrap method as I have never needed to use it. Flashing custom ROMs on the Canadian s4 is done using TWRP, not safestrap.
There is always risk chance that something will go wrong during any flashing process. You just have to make sure you download all of the necessary files to unbrick the phone before flashing anything.
I am sure there are some YouTube videos on how to use safe strap.
Long safestrap thread here: https://forum.xda-developers.com/showthread.php?t=2428254

Samsung S4 SGH I337(Don't know the PDA it's running on) hangs on AT&T logo.

Dear All,
I have been reading many threads for a week before I decided to post a new thread here.
I am running in a big problem here with my S4 SGH-I337 which I have. I have never updated it with any version and it's hanging on it's ATT logo. I have tried all the factory and data reset options which I have come across on this forum, but the phone didn't come back to life.
Then I tried to flash it with Odin using I337UCUAMDB tar file(Since the phone is not working I couldn't find the PDA its running on), but it's failing saying FAIL! (Auth). Since I am doing it first time and I don't know much about flashing things, I am stuck out here. After doing some research I found that I should flash it with the PDA version matching to my phone but since my phone is not booting up I am not sure how can i find the PDA version for my phone. Even I have tried reaching to SAMSUNG's authorized center but they replied, as you are in INDIA and your phone was purchased when you were in USA, so we don't have that software to repair it. Please help me as I don't know what to do this phone now. Your help would be greatly appreciated.
Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.
StoneyJSG said:
Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.
Click to expand...
Click to collapse
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.
mahendra_bhawsar said:
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.
Click to expand...
Click to collapse
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.
StoneyJSG said:
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.
Click to expand...
Click to collapse
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.
Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?
mahendra_bhawsar said:
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.
Click to expand...
Click to collapse
I downloaded I337UCUAMDL firmware from http://stockroms.net/file/GalaxyS4/SGH-I337/I337UCUAMDL_I337ATTAMDL_ATT.zip but when I flesh it using ODIN it says FAIL(!Auth). Here is the ODIN Log: <ID:0/004> Added!!
<ID:0/004> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me what should I do in this case.
audit13 said:
Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?
Click to expand...
Click to collapse
Nope, It does not say anything about Knox in the download screen. I see model number(SGH-I337) on the hardware underneath the battery.
Thank You!
The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.
audit13 said:
The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.
Click to expand...
Click to collapse
I think I have purchased this cell phone back in Sept 2013, that time I believe AT&T had the following versions:
Build Date: 27.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDL Changelist: 453947 Android: 4.2.2
Build Date: 09.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDB Changelist: 440216 Android: 4.2.2
I tried both of them using both the ports of my laptop with different USB Cables(Original cable from Sony, Samsung and Moto G), but every time I got the same Odin Fail (!Auth) error. I am not sure whats the wrong here or what should I do to resolve this error and get the phone working.
Thank You!
What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?
audit13 said:
What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?
Click to expand...
Click to collapse
I think it was Android 4.2.2, this is what the download mode says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNAL LOCK: 0*0
KNOX WARRANTY VOID: 0*0
CSB-CONFIG-LSB: 0*30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thank You!
The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.
audit13 said:
The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.
Click to expand...
Click to collapse
Ohh I understand this now. But knox says 0*0 bit still it means it has a locked bootloader ? I think may be it was running on 4.3 before it crashed, may be I had got some update on 4.2.2 and that made it got updated on 4.3 which I didn't re-collect. What should I do now, which ROM you would suggest me to flash it with. Really appreciate your help.
Thank You!
If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221
audit13 said:
If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
It has lots of ROMS and instructions to follow, I am a novice user in this so got confused what to do and what not. Even I don't know my current baseband version so unable to choose firmware or method to flash it in order to get it working. Any help from your side on this front ?
Thank You!
You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
audit13 said:
You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
Click to expand...
Click to collapse
My phone is in hanging state on boot loop won't be able to perform the steps mentioned on that link like : 1. Place the ROM onto your device (use either internal or ext-sdcard). etc... Any other suggestion please ?
You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.
audit13 said:
You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.
Click to expand...
Click to collapse
Great! Thanks I am trying to download it, it will take time since my network is a bit slow, will let you know if that works, hopefully it should.

Categories

Resources