[Q] Canadian i9505 no sound, wifi, calls - Galaxy S 4 Q&A, Help & Troubleshooting

Let me start off with I'm an idiot. Now that that's over with let me explain what I did to end up here and what I've tried to do to fix it, to no avail of course.
I was running Android 4.3 rooted with cf-autoroot. My software was messing up and with the news that kitkat was available I wanted to unroot and upgrade.
Using a guide I found online I flashed a version of 4.2.2 android. the file name was I337MVLUAMDJ_I337MOYAAMDJ_RWC.zip
Of course when it finished I had the no sound, no wifi problem because i reverted back to the wrong android system.
I then using twrp flashed VANIR and got wifi but still no sound/calls.
As per other threads I tried flashing I9505XXUDMH8_I9505OXXDMHA_BTU with ODIN but every time i would get the error:
<ID:0/005> Complete(Write) operation failed.
The only somewhat success I had was i was able to flash RWC-I337MVLUEMK6-20131125124040 using ODIN 1.85 which is a 4.3 version but still no wifi/sound/calls.
Other files i have tried to flash are GSM_Modem_XXUFNA5_and_LTE_Modem_XXUFNA5(under phone), I9505XXUDMH8-PRE-ROOTED-KNOX_FREE-ODEX-FULL and even tried a pit file: CSB_signed_Fusion3_EUR_0325_V2.pit
Everytime i get Complete(Write) operation failed.
I've put CWM on but still no luck. I need suggestions or a fix please and thank you.

1. Be sure ur phone is SGH-i337 or SGH-i337M. Take the battery off and take a look the label pls for avoid problems :highfive:
2. Wipe all and flash the latest FIRMWARE android 4.4.2 for ur phone (if is SGH-i337M) through ODIN.
3. When u finish, tell me how it worked. Hi5

Downloading now. It is SGH-i337M. Is it normal to be getting (<ID:0/005> Complete(Write) operation failed.) errors when flashing with ODIN?

drock21d said:
Downloading now. It is SGH-i337M. Is it normal to be getting (<ID:0/005> Complete(Write) operation failed.) errors when flashing with ODIN?
Click to expand...
Click to collapse
Yes if u are trying to downgrade android 4.3 to android 4.2.2 :highfive:

Wow thank you. I did a flash with ODIN 3.09 and that file you sent and it seems to be working great. going to try to put CWM and VANIR on now. seeing as how my warranty is voided by knox anyways. Thanks Joku!

drock21d said:
Wow thank you. I did a flash with ODIN 3.09 and that file you sent and it seems to be working great. going to try to put CWM and VANIR on now. seeing as how my warranty is voided by knox anyways. Thanks Joku!
Click to expand...
Click to collapse
In the OP u wrote: "I was running Android 4.3 rooted with cf-autoroot". Your voided ur warranty that time :highfive:

Related

really need help. think I really did it

So I tried alot of ways to root my samsung galaxy s4 I337. After multiple attempts I got it to root. With the program called: kingo android root
I wanted to put cm10 on here but I needed a custom recovery i tried odin to put twrp on and It kept on failing giving me errors over and over.
so I found a program called: casual that did a root and custom recovery.
well after that it said reboot. So It did and then It got to odin downloading saying error cant normal boot.
I cant restore my phone, get into recovery, the only way I can get on my phone is if I press power down and the home button. Then it boots up.i want it to be fixed without going through all this haggle.
is there anyway besides kies cuz that aint working to fix my phone.
I check root checker basic and I am no longer rooted.
like I said odin is not working for my phone for whatever reason.
maybe if I wait for 4.3 on the 13th and do the ota update will that help.
im so lost please help me someone.
Need to know what firmware you're on. Mf3? Most likely
This might work, but it will delete everything on your phone and reset it. I hope this works :fingers-crossed:
Follow these steps (On your own risk):
1) get on your phone
2) Make sure you have unknown sources enabled (Settings--More--Security--Unknown Sources)
3) install Safestrap 3.62 (download given below)
4) Open app and click "Install Recovery"
5) then press "Reboot to Recovery"
6) It should boot into Safestrap, if not then turn off your phone and the boot it up as you would to use it and then click the menu button on the phone.
7) Then click Wipe
8) Swipe to Factory Reset
9) Reboot
10) Enjoy!
mrwilson1991 said:
So I tried alot of ways to root my samsung galaxy s4 I337. After multiple attempts I got it to root. With the program called: kingo android root
I wanted to put cm10 on here but I needed a custom recovery i tried odin to put twrp on and It kept on failing giving me errors over and over.
so I found a program called: casual that did a root and custom recovery.
well after that it said reboot. So It did and then It got to odin downloading saying error cant normal boot.
I cant restore my phone, get into recovery, the only way I can get on my phone is if I press power down and the home button. Then it boots up.i want it to be fixed without going through all this haggle.
is there anyway besides kies cuz that aint working to fix my phone.
I check root checker basic and I am no longer rooted.
like I said odin is not working for my phone for whatever reason.
maybe if I wait for 4.3 on the 13th and do the ota update will that help.
im so lost please help me someone.
Click to expand...
Click to collapse
You are most probably on MF3, therefore you cannot install TWRP or CWM recoveries. You can only use Safestrap as of right now.
jd1639 said:
Need to know what firmware you're on. Mf3? Most likely
Click to expand...
Click to collapse
firmware 4.2.2. originally. but after doing whatever I did and connecting to kies it says: Current Firmware version: PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
I am going to try safestrap and let you guys know if it worked.
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can't install Cyanogenmod. Read through the Safestrap thread and the Q/A thread to see what works.
Sent from my SGH-I337 running Foxhound 2.0
mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can't. On MF3 you cannot run AOSP/AOKP/CM/MIUI based roms. Only custom TW.
Sent from my SGH-I337 using XDA Premium 4 mobile app
mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can only use the roms listed in this thread
Thanks guys,
This means a lot with the help. Now if I can get the WiFi to work on the hyperdrive rom. I'll be good as gold tell y'all what from. Going from a jailbreak iOS themer to android rooting user. It's very different and a lot of looking into and reading.
Now back into looking to get this WiFi to work. Just wanted to say thanks
Did you flash the ATT compatibility package zip that you should have downloaded along side of the Hyperdrive rom ,after those two zips did you flash the MF3 kernel module zip.
I use the Hyperdrive rom now and don't have any issues
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Did you flash the ATT compatibility package zip that you should have downloaded along side of the Hyperdrive rom ,after those two zips did you flash the MF3 kernel module zip.
I use the Hyperdrive rom now and don't have any issues
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
no i only installed the hyperdrive rom. I am not sure what to do for the rest.
mrwilson1991 said:
no i only installed the hyperdrive rom. I am not sure what to do for the rest.
Click to expand...
Click to collapse
When you downloaded the rom it is in the same page. You need the compatibility package and the MF3 kernel module on Safestrap for it to work right.go back to the Hyperdrive thread and search for it
Sent from my ATT S4 MF3 using Tapatalk
Use Odin and the files here
Just went through this myself and I'm back and running
http://forum.xda-developers.com/showthread.php?t=2502003
You can root with kingo fine, I rooted again right after recovering but do not install any recovery like twrp or clockwork
Sucks but it's how it is
Sent from my Nexus 7 using xda app-developers app
tevil said:
Use Odin and the files here
Just went through this myself and I'm back and running
http://forum.xda-developers.com/showthread.php?t=2502003
You can root with kingo fine, I rooted again right after recovering but do not install any recovery like twrp or clockwork
Sucks but it's how it is
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
here is my issue now.
I rooted with kinggo android root. Then for custom recover I have Safestrap. I rooted to see what all i could do but after trying different Roms I have noticed I don't care. Much for it.
I unrooted via the kinggo app. And verified with root checker.
But i want to go back to full stock. I noticed Safestrap is still there running in background. But the custom logo is gone.
I just want to go back to stock and have nothing to do with root.
I used the code to remove safestrap. and used kingo to unroot. but when I get the offical files for odin and try to push them into my phone. yes I am in download mode when I enter download mode i get:
odin mode
product name: SGH - 1337
current binary: Samsung official
system status: official
CSB-CONFIG-LSB: 0X30
write protection enabled
when I enter odin put thi the tar file for 4.2.2 I get a pass then a fail. the message log says: <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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and then there is this in red on my phone:
start [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I know I changed the topic. but after thinking there is really nothing that bennifets me with being rooted. and personally I would rather be stock.
can you guys please help.

[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

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

return to kitkat problem

did anyone try to comeback (910C)lolipop (new poland stock rom COJ5) to kitkat (4.4.4) via odin
in Turkish forum some guy tried to comeback ,but he did not success it.I told him what I know about this.
he also used 4 parts rom and pit files ,one part rom and pit files,firstly try to kitkat bootloader via odin etc.etc but he said no,no,no
some guys are saying,now samsung has prevent to return kitkat from COJ5 ,is that true or not
we need alternatives way
hi,still no any idea
guys,I thing samsung putted a bootloader lock to return to kitkat even 5.0.1.
I tried to both of them ,but result no succesed it. that is way ,whom want to return to comeback to kitkat and 5.0.1 bootloader ,they will meet this lock. maybe you want to use miui rom like me .what will I do
I bought a new Note 4 N910G Indian version with LP 5.01. Loaded a custom Rom, Dr.Ketan ROM 5.0.1 after rooting. Got Xposed working but still didnt like it. I then downgraded to Stock Kitkat 4.4.4 from Sammobile site with ODIN. Rooted after loading TWRP again. (Root got disabled on downgrading so had to reroot SuperSu). Loaded Xposed. Everything working smoothly. Only one issue is Lockscreen Widgets which even Xposed is not able to bypass when the phone has PIN or Pattern lock but very happy now. Quite similar to my JB Note 3 N9005 which is what I wanted.
pelase help, any idea, suggestion,etc.
what should I do ,what can I do
i tried 5.0.1 but then came back to ANK3 4.4.4 Kitkat via ODIn with no problem. Nothing still beat the Xposed on Kitkat. One thing I am looking forward to is more options of 4.4.4 kernel. I can only see 1 kernel for kitkat which is KT kernel. Hopefully some more kernel for Note 4 Kitkat OS will be available.
theleftykid said:
i tried 5.0.1 but then came back to ANK3 4.4.4 Kitkat via ODIn with no problem. Nothing still beat the Xposed on Kitkat. One thing I am looking forward to is more options of 4.4.4 kernel. I can only see 1 kernel for kitkat which is KT kernel. Hopefully some more kernel for Note 4 Kitkat OS will be available.
Click to expand...
Click to collapse
do you mean try to change the kernel(kitkat)to return kitkat
mudur1998 said:
pelase help, any idea, suggestion,etc.
what should I do ,what can I do
Click to expand...
Click to collapse
Did you do all the steps properly?
I started off by doing a complete Reset and Format in TWRP. Wiped everything including External SD card.
So maybe you should do that first. But backup any important data on some external storage not connected to the phone. Most important : Make sure you are using the correct stock Kitkat ROM version for your model from Sammobile site.
Follow the instructions on Sammobile's firmware download page, and you should be back to stock Kitkat 4.4.4 soon.
niceguy1430 said:
Did you do all the steps properly?
I started off by doing a complete Reset and Format in TWRP. Wiped everything including External SD card.
So maybe you should do that first. But backup any important data on some external storage not connected to the phone. Most important : Make sure you are using the correct stock Kitkat ROM version for your model from Sammobile site.
Follow the instructions on Sammobile's firmware download page, and you should be back to stock Kitkat 4.4.4 soon.
Click to expand...
Click to collapse
that is good idea I will try it,firstly format evrything in twrp and after that try to flash rom with odin .I know my rom is correct rom.
I will report it
sorry ,no result,one part rom,four part roms,with pit and without pit .
before start I wiped everything in twrp
now, I believe that samsung putted a lock to prevent return also 5.1.1 my own rom
mudur1998 said:
now, I believe that samsung putted a lock to prevent return also 5.1.1 my own rom
Click to expand...
Click to collapse
any logs on odin?
kerbiii said:
any logs on odin?
Click to expand...
Click to collapse
knox warranty void 1
ap survey 2
sw rev.check fail device 2 binary 1
ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> _(N910CXXU1COI4_4files_5.1.1_TUR_Factory_Firmware)(like that I do not rememeber but it is my own firmware) HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried kitkat but have no more odin logs
Dont know why you are fiddling with PIT. Not required to touch it at all. As far as I know 5.1.1 to KK is quite possible, just as mine I successfully downgraded from 5.0.1 to KK.
Once you wipe everything and format SD card as well, and start with a clean slate, it should work through ODIN. Try with another version of ODIN maybe? Dont touch PIT section at all.
niceguy1430 said:
Dont know why you are fiddling with PIT. Not required to touch it at all. As far as I know 5.1.1 to KK is quite possible, just as mine I successfully downgraded from 5.0.1 to KK.
Once you wipe everything and format SD card as well, and start with a clean slate, it should work through ODIN. Try with another version of ODIN maybe? Dont touch PIT section at all.
Click to expand...
Click to collapse
I mean 5.1.1 but COJ5 (poland new firmware),I also tried with pit and without pit,I could not to downgrade 4.4.4 or 5.0.1 and also my own rom 5.1.1 COI4
Same problem
I am having the same problem, please advise the solution
please text on Whatsapp +966553270134
mudur1998 said:
I mean 5.1.1 but COJ5 (poland new firmware),I also tried with pit and without pit,I could not to downgrade 4.4.4 or 5.0.1 and also my own rom 5.1.1 COI4
Click to expand...
Click to collapse
have you tried flashing CWM recovery and wiping everything and using clean install? that way it will remove your 5.1.1 FW
kerbiii said:
have you tried flashing CWM recovery and wiping everything and using clean install? that way it will remove your 5.1.1 FW
Click to expand...
Click to collapse
yes you can flash twrp,no problem. I tried also I wiped everything and clean install with odin.no,no,no
never comeback to even COI4
mudur1998 said:
yes you can flash twrp,no problem. I tried also I wiped everything and clean install with odin.no,no,no
never comeback to even COI4
Click to expand...
Click to collapse
try to search for custom ROM with the same bootloader that you are using right now, your official bootloader will not let you flash any older bootloader thats why you cant flash anything under 5.1.1.,
i suggest try flashing the latest wanam
http://forum.xda-developers.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266
if you successfully flash the wanam then try to flash the stock kitkat again
kerbiii said:
try to search for custom ROM with the same bootloader that you are using right now, your official bootloader will not let you flash any older bootloader thats why you cant flash anything under 5.1.1.,
i suggest try flashing the latest wanam
http://forum.xda-developers.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266
if you successfully flash the wanam then try to flash the stock kitkat again
Click to expand...
Click to collapse
yes, without miui I am using these types of custom roms DN5,sixperience,e robot,rulinglite,sweet rom,etc.but I like only miui rom ,that is way I want to try come back bootloader 4.4.4 or 5.0.1.
It is (wanam lite rom)based COJ5,what would be change.but I have tried it. I have already installed wanamlite rom, and wanam kernel etc.no ,no, no
mudur1998 said:
yes, without miui I am using these types of custom roms DN5,sixperience,e robot,rulinglite,sweet rom,etc.but I like only miui rom ,that is way I want to try come back bootloader 4.4.4 or 5.0.1.
It is (wanam lite rom)based COJ5,what would be change.but I have tried it. I have already installed wanamlite rom, and wanam kernel etc.no ,no, no
Click to expand...
Click to collapse
what im trying to say is, try to flash 5.1.1. custom rom first and from there downgrade to kitkat. have you done trying that?

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