Database Users

[Q] Soft Bricked my S4

Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.

tr10 said:
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
Click to expand...
Click to collapse
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.

xBeerdroiDx said:
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
Click to expand...
Click to collapse
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.

tr10 said:
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
Click to expand...
Click to collapse
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice, I have done that countless times. I'm hoping that it changes one of these times though.
I took your advice regarding re-flashing the image and ticking the bootloader update option, odin stated it was successful and auto-rebooted. I pulled the battery and tried to enter recovery, no cigar.

Perhaps try the Heimdall route: http://forum.xda-developers.com/showthread.php?t=2374441

When attempting to flash TWRP recovery, my phone says in the top right hand corner:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enabled
START [224, 1440]
SECURE CHECK FAIL: recovery
Don't know what that means.
I haven't tried the heimdall method yet, not sure if I wanna give it a shot because it seems a lot more complex only to accomplish the same thing odin would. I can imagine something is stopping odin from putting a bootloader, or kernel. That same thing would stop heimdall. But, I have no idea what I'm talking about. Waiting to hear more advice before I make the hole I dug deeper.
Thank you for your time guys.

Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?

Febby said:
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
xBeerdroiDx said:
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Click to expand...
Click to collapse
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.

tr10 said:
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
Click to expand...
Click to collapse
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.

Febby said:
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Aou said:
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Click to expand...
Click to collapse
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.

Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.

Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.

Febby said:
I actually considered switching to a ONE today.
Click to expand...
Click to collapse
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.

Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.

Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
Either way. Also, if one fails, try the other of course.

Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
I converted the .img to a .tar and I sadly had the same results =( Thank you for the idea though, definitely helped.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
Thank you, I attempted to reflash the stock kernel included in the MDL package. No avail. Same problem. Good advice though!
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
I just reflashed the stock kernel, no cigar =( It is very strange to me that I can't get the phone to respond to anything other than download mode. Especially considering that I odin'd to stock. I'm starting to think I made it worse by going back to stock after flashing slimbean's weekly update.
Thank you for your time guys, keep the ideas coming, I'm definitely trying to come up with my own ideas.
I have so far done the following:
Odin'd MDL, MDB, Stock Kernel, Stock Recovery (All through download mode, as I don't have access to recovery.)
I've also tried to odin TWRP but I fail in Odin since download mode blocks the illegal recovery.
Thank you again for your time.

tr10 said:
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Click to expand...
Click to collapse
Im not so sure how everyone just over looked this but the rom in that link is for the att S3. So you flashed an S3 rom to your S4.
D2att is the s3 for att.
Jflteatt is the att variant.
http://www.slimroms.net/index.php/downloads/all/viewcategory/620-jflteatt
Thats the correct link to weekly roms for slim rom for our device. your partitions might just be corrupted in case maybe having a jtag or using the pit file for MDL would fix? :/ im not an expert haha just observations.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------
xBeerdroiDx said:
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Click to expand...
Click to collapse
You sure? On the att one majority of devs dont post on the att htc one section but eather "HtC one" section since all roms work vice versa on that phone international roms > works on all models of the one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[Q] Odin Keeps Failing

Hello. I have been searching for hours like a mad man on Google for a solution to my problem, but i'm having no luck. Excuse the nooby nature of this post please. So I rooted my Galaxy S4 and I am trying to get it back to stock by flashing the AT&T md5 onto my phone (Galaxy S4 SGH-I337) through ODIN and it fails every single time. Initially, with ODIN 3.07, it would return something like fail (auth). Then I tried with ODIN 1.85, but that version returns "Complete(Write) operation failed." In addition, I attempted Kies but it too failed (no specific error code), and now the phone wont boot. It says that the firmware upgrade encountered an issue. I am not able to access stock recovery or TWRP because it will automatically go to Download Mode with "Could not do normal boot" in the top left corner if I in any way attempt to access it. I am using the stock cable with USB Debugging enabled. I also tried two different computers, two different cables (one being stock of course), and tried every single usb port on both computers. What went wrong? I will give you my upmost respect if you can solve this. I also am absolutely willing to supply any information you may need. Just ask. (Please don't be bricked. Please don't be bricked)
-With kind regards, Branden.

Let me guess you had the att mf3 firmware and tried retoring by flashing the MDL firmware via odin? You said md5 so I assume mdl? You might at this point still be able to fix it visiting a best buy near you if it has a samsung center. Also att store can reflash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Click Here throw this thread in the MF3 pile... guys we got another noob here, take a trip to your closest best buy and hope the samsung experience will flash the mf3 update for u

You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.

jd1639 said:
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
Click to expand...
Click to collapse
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.

If you never got twrp to work then I'm almost positive you have mf3 firmware. You're best bet is best buy and have them re-flash the firmware.

Astrophysicist789 said:
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
Click to expand...
Click to collapse
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.

gandes said:
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
Click to expand...
Click to collapse
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.

Astrophysicist789 said:
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Click to expand...
Click to collapse
Your welcome

And just so everyone knows...md5 is part of the package name I believe... (.tar.md5) or could be referring to md5 checksum...anyways as was mentioned and you acknowledged, best buy is your best bet
Sent from my SGH-I337 using Tapatalk 4

Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

ralphie1267 said:
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah it is the dreaded one! Root your device and flash a custom ROM or use titanium backup to freeze the update apps.
Sent from my SGH-I337 using Tapatalk 2

[Q] Note 3 N900W8 soft bricked, backup not working.. can't find a compatible firmware

I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?

Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?

Yorgo1982 said:
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Click to expand...
Click to collapse
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.

Apra24 said:
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Click to expand...
Click to collapse
wait sammobile if u r with rogers bell telus fido vmc koodo, and if with other carrier contact them with ur phone model and serial num so they will upload it ..

Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
Did you restore from CWM/TWRP?

Pikezer1337 said:
Did you restore from CWM/TWRP?
Click to expand...
Click to collapse
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..

Apra24 said:
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Click to expand...
Click to collapse
If you restored through TWRP there is a good chance that you are softbricked. There are restoring issues that mess with the system partition.

Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition

Apra24 said:
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Click to expand...
Click to collapse
can u give the file name?
plz

Yorgo1982 said:
can u give the file name?
plz
Click to expand...
Click to collapse
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.

Apra24 said:
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Click to expand...
Click to collapse
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol

Yorgo1982 said:
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Click to expand...
Click to collapse
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.

Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317

Dumbo53 said:
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I'm wondering if the official Bell/Rogers firmware will be available any time soon? Does it typically get released soon after the phone launch, or are they withholding it for some reason?

Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.

eklipse1 said:
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
Click to expand...
Click to collapse
I was trying the Peru one for a while, but it kept hanging up during the bootup. The message was in a foreign language, but I'm assuming it was "initializing". It would initialize for about 3 minutes then an error message would pop up saying something is not responding.

Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app

eklipse1 said:
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I have been trying to. When I flash the firmware in odin, it reinstalls the stock recovery mod. Right after flashing firmware, it won't go into recovery mode on the first boot (first does some android robot install thing, then boots up). I attempted to install the TWRP recovery directly after the firmware, and then booting directly into recovery to factory reset, but I'm still getting a boot loop.

Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol

Yorgo1982 said:
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Click to expand...
Click to collapse
do they know it's rooted/void? Or did you somehow not trigger the knox/warranty void switch? I may just have to do the same thing...

[Q] Hard-Bicked S4? Options?

Gentlemen/Ladies,
I was putting custom roms on my phone last night, trying a few different out. Obviously I misread (or didn't read) some instruction somewhere and ended up with this lovely message when turning my phone on:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So, what are my options? Can I use Odin or ADB or something to at least get the phone back to stock or am I completely effed and have to walk into a Verizon store? I'm open to suggestions and will probably try all of them.
Please advise,
phoyce

Flash a stock ROM via odin

DSA said:
Flash a stock ROM via odin
Click to expand...
Click to collapse
I did (tried) as you suggested. Obviously I'm doing something wrong.
I downloaded the stock Verizon Galaxy S4 SCH-i545 VRUAMDK md5 from [galaxys4root.com/galaxy-s4-stock-firmware]. I boot the phone into download mode, open up Odin (3.09) and flashed using the file above. Odin still fails on the first block.
Is this because what I downloaded was for Android 4.2.2 and my phone was/is 4.4? Or am I downloading the wrong file or simply going about this the wrong way?
Thanks a lot for the help, as you can see I'm still learning.
- phoyce

phoyce said:
I did (tried) as you suggested. Obviously I'm doing something wrong.
I downloaded the stock Verizon Galaxy S4 SCH-i545 VRUAMDK md5 from [galaxys4root.com/galaxy-s4-stock-firmware]. I boot the phone into download mode, open up Odin (3.09) and flashed using the file above. Odin still fails on the first block.
Is this because what I downloaded was for Android 4.2.2 and my phone was/is 4.4? Or am I downloading the wrong file or simply going about this the wrong way?
Thanks a lot for the help, as you can see I'm still learning.
- phoyce
Click to expand...
Click to collapse
you need to post in your relevant forum, this is for the international s4's
http://forum.xda-developers.com/galaxy-s4-verizon
but no, once you have got kitkat on your phone, you cant downgrade just like that
flash a kitkat stock rom via odin

Verizon Galaxy S5 stuck on verizon boot screen

My Verizon S5 (but being used on T-mobile) was charging in my car when it decided to turn off and reboot and it's been stuck on the Verizon boot screen ever since. I've tried countless times to clear the partition cache as well as factory resetting, with no change, still never goes past the Verizon screen. And more recently I've used odin to reflash the BOG5 .tar, which it was running at the time that the problem occurred, and which odin says was successful, but the phone still never boots past the Verizon screen. I've also tried flashing just the .pit file alone and the .pit file with the .tar file, but the problem remains. This phone was just running the standard ROM at the time of the problem.
I am about ready to throw in the towel, but would be grateful if anyone had some pointers.
Josh

jdfowl said:
My Verizon S5 (but being used on T-mobile) was charging in my car when it decided to turn off and reboot and it's been stuck on the Verizon boot screen ever since. I've tried countless times to clear the partition cache as well as factory resetting, with no change, still never goes past the Verizon screen. And more recently I've used odin to reflash the BOG5 .tar, which it was running at the time that the problem occurred, and which odin says was successful, but the phone still never boots past the Verizon screen. I've also tried flashing just the .pit file alone and the .pit file with the .tar file, but the problem remains. This phone was just running the standard ROM at the time of the problem.
I am about ready to throw in the towel, but would be grateful if anyone had some pointers.
Josh
Click to expand...
Click to collapse
try flashing Full Wipe G900V_Downgrade_to_NCG.tar which can be found here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 with odin hope that helps
this might help aswell
http://forum.xda-developers.com/showthread.php?t=2784880

Veid71 said:
try flashing Full Wipe G900V_Downgrade_to_NCG.tar which can be found here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 with odin hope that helps
this might help aswell
http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
He can't flash and downgrade to NCG. He wrote his phone was on BOG5 and he tried flashing that tar file also. If he was on stock BOG5 he cannot downgrade from there.

landshark68 said:
He can't flash and downgrade to NCG. He wrote his phone was on BOG5 and he tried flashing that tar file also. If he was on stock BOG5 he cannot downgrade from there.
Click to expand...
Click to collapse
idk its worth a shot he said its not on any rom atm lol it just bootloops and i think he meant it was on og5 while he had the rom installed (a rooted OG5 firmware/kernel im assuming) it cant hurt to try it its already bootlooped lol

jdfowl said:
My Verizon S5 (but being used on T-mobile) was charging in my car when it decided to turn off and reboot and it's been stuck on the Verizon boot screen ever since. I've tried countless times to clear the partition cache as well as factory resetting, with no change, still never goes past the Verizon screen. And more recently I've used odin to reflash the BOG5 .tar, which it was running at the time that the problem occurred, and which odin says was successful, but the phone still never boots past the Verizon screen. I've also tried flashing just the .pit file alone and the .pit file with the .tar file, but the problem remains. This phone was just running the standard ROM at the time of the problem.
I am about ready to throw in the towel, but would be grateful if anyone had some pointers.
Josh
Click to expand...
Click to collapse
In order to help you, can you tell us where you download the OG5.tar?? I just wondering if you actually flashed the stock OG5 tar or the modded OG5 tar. There will be different options depended on which one you used.

It was just the stock tar, the same as before the booting problem. I downloaded one from samsung-updates (can't post links) and another one linked from these forums with the same result. Both files were named G900VVRU2BOG5_G900VVZW2BOG5_G900VVRU2BOG5_HOME.tar.md5. I also tried to install one with an older version bootloader, but it failed, as to be expected I believe since I'm already at bog5. Thanks for the help so far.
buhohitr said:
In order to help you, can you tell us where you download the OG5.tar?? I just wondering if you actually flashed the stock OG5 tar or the modded OG5 tar. There will be different options depended on which one you used.
Click to expand...
Click to collapse

jdfowl said:
It was just the stock tar, the same as before the booting problem. I downloaded one from samsung-updates (can't post links) and another one linked from these forums with the same result. Both files were named G900VVRU2BOG5_G900VVZW2BOG5_G900VVRU2BOG5_HOME.tar.md5. I also tried to install one with an older version bootloader, but it failed, as to be expected I believe since I'm already at bog5. Thanks for the help so far.
Click to expand...
Click to collapse
Did you try Kies?

I did, but maybe I'll try again. Kies never recognized the phone, I figured because the phone never fully boots up. Should I try to put the phone in download mode? It also looked like Kies only reverts back to a state saved in Kies, but I've never previously done a back up in Kies. Is Kies still useful for me?
buhohitr said:
Did you try Kies?
Click to expand...
Click to collapse

buhohitr said:
Did you try Kies?
Click to expand...
Click to collapse
I tried Kies again, but could not get very far without a s/n, which I can't find anywhere on the phone, and Kies would not accept the imei.