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] 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...

(Soft) Bricked Samsung Galaxy S5 Verizon

"Root my phone" she says, "It will be great" she says...That is what my girlfriend asked me but now I have her phone bricked and can't get it running again. Have rooted multiple android devices before but this one has stumped me. Tried to get old 4.4.4 OS on it using Odin and now I cannot get any OS on it. Even the original stock OS I cannot get loaded on, which I would happily take.
Things you should know:
-Samsung Galaxy S5 Verizon edition
-Using Odin v 3.10.06
-Using md5 and .tar SM-G900V
-Phone can go into Recovery/Download Mode
-Odin sees phone and recognizes it, but when trying to load on OS it gives error failed.
Ask me for any other info, I would be happy to get it rooted, not rooted, custom ROM, just anything to get it running again.
Thank you very much.

TUTRider said:
"Root my phone" she says, "It will be great" she says...That is what my girlfriend asked me but now I have her phone bricked and can't get it running again. Have rooted multiple android devices before but this one has stumped me. Tried to get old 4.4.4 OS on it using Odin and now I cannot get any OS on it. Even the original stock OS I cannot get loaded on, which I would happily take.
Things you should know:
-Samsung Galaxy S5 Verizon edition
-Using Odin v 3.10.06
-Using md5 and .tar SM-G900V
-Phone can go into Recovery/Download Mode
-Odin sees phone and recognizes it, but when trying to load on OS it gives error failed.
Ask me for any other info, I would be happy to get it rooted, not rooted, custom ROM, just anything to get it running again.
Thank you very much.
Click to expand...
Click to collapse
Which build was the phone running? OG5 and the one before it can't be rooted/downgraded to my knowledge...
I also only stick w odin 3.09...been using it for years with no problems..

roadblock217 said:
Which build was the phone running? OG5 and the one before it can't be rooted/downgraded to my knowledge...
I also only stick w odin 3.09...been using it for years with no problems..
Click to expand...
Click to collapse
it was on 5.0 I believe, and now am using 3.09. Thanks for the info.
Anything else you would recommend?

TUTRider said:
it was on 5.0 I believe, and now am using 3.09. Thanks for the info.
Anything else you would recommend?
Click to expand...
Click to collapse
Need to know exactly which build the phone was on...its in settings

roadblock217 said:
Need to know exactly which build the phone was on...its in settings
Click to expand...
Click to collapse
I do not know, I know that is super unhelpful. But all it can do at this point is go into download mode and recovery mode.

TUTRider said:
I do not know, I know that is super unhelpful. But all it can do at this point is go into download mode and recovery mode.
Click to expand...
Click to collapse
lol no worries. To me, it seems like the phone was on OG5 (latest) or the one before that, which disables going BACK to an older build to be able to root...Are you using ODIN properly (sorry, I have to ask)
ALL files I've flashed go in the AP slot...so try downloading the top file of the two (seeing as it prob. isnt rootable anyway) http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
download, unzip if needed, and try flashing that in the AP slot when in ODIN...see what that does..

roadblock217 said:
lol no worries. To me, it seems like the phone was on OG5 (latest) or the one before that, which disables going BACK to an older build to be able to root...Are you using ODIN properly (sorry, I have to ask)
ALL files I've flashed go in the AP slot...so try downloading the top file of the two (seeing as it prob. isnt rootable anyway) http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
download, unzip if needed, and try flashing that in the AP slot when in ODIN...see what that does..
Click to expand...
Click to collapse
I will try it and keep you posted. I believe I am using it correctly, phone is connecting and it will start things but then the fail message comes up.

TUTRider said:
I will try it and keep you posted. I believe I am using it correctly, phone is connecting and it will start things but then the fail message comes up.
Click to expand...
Click to collapse
I know, just figured I'd make sure. I've messed up with it alot myself, trial and error.
Yeah if the error message pops up I'm pretty sure it's one of the 2 new updates...it kills root and backwards flashing

roadblock217 said:
I know, just figured I'd make sure. I've messed up with it alot myself, trial and error.
Yeah if the error message pops up I'm pretty sure it's one of the 2 new updates...it kills root and backwards flashing
Click to expand...
Click to collapse
It worked. Thanks you so so so much! Now I know I just got myself out of a hole but...any chance I can get this thing rooted? or am I better off just leaving it as is?

TUTRider said:
It worked. Thanks you so so so much! Now I know I just got myself out of a hole but...any chance I can get this thing rooted? or am I better off just leaving it as is?
Click to expand...
Click to collapse
As he said in his first response to you, the OE1 and OG5 builds cannot be rooted, and likely will never be able to be rooted.

TUTRider said:
It worked. Thanks you so so so much! Now I know I just got myself out of a hole but...any chance I can get this thing rooted? or am I better off just leaving it as is?
Click to expand...
Click to collapse
Glad that worked at least...but yeah you won't be able to root or anything until (if) they find an exploit..only time will tell I guess at this point....BUT you have a phone that works at least...

landshark68 said:
As he said in his first response to you, the OE1 and OG5 builds cannot be rooted, and likely will never be able to be rooted.
Click to expand...
Click to collapse
OK. Thank you very much!

I happily did exactly what TUTRider did, from trying to root, to bricking, then using roadblock's 6.0.1 files to unbrick, but I'm still getting stuck on the Galaxy splash screen. Odin 3.09 gave the load a PASS, and I 100% had 6.0.1 on it before trying to root. Is there something I could be doing horribly wrong, I'm fairly new to Android rooting, though I have a lot of experience with iOS jailbreaking.

fabledlight said:
I happily did exactly what TUTRider did, from trying to root, to bricking, then using roadblock's 6.0.1 files to unbrick, but I'm still getting stuck on the Galaxy splash screen. Odin 3.09 gave the load a PASS, and I 100% had 6.0.1 on it before trying to root. Is there something I could be doing horribly wrong, I'm fairly new to Android rooting, though I have a lot of experience with iOS jailbreaking.
Click to expand...
Click to collapse
If you're trying to root, you have to be on Lollipop. Can't root MM, but it IS possible to get on a pre-rooted ROM.
Go back to Lollipop, and follow this: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Once you're on Lollipop and rooted, if you can get your bootloader unlocked, then you can upgrade to a pre-rooted 6.0.1 ROM.
Go here to see if you can unlock. (Some phones can, some can't. Cross your fingers!) Read the "Warnings" section carefully, and look to see if your cid # starts with 15.
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
If you can unlock, follow the instructions on that page carefully to do it, and then follow these instructions for going to 6.0.1 on unlocked bootloader:
http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784

TUTRider said:
it was on 5.0 I believe, and now am using 3.09. Thanks for the info.
Anything else you would recommend?
Click to expand...
Click to collapse
Yes. We would need to know which 5.0/LP you were on. Such as 0A8, OC4, OD5, etc...as the person posted before me. You cannotODIN back to KK(4 4.2/4.4.4) if you were on OE1 and above...if you know exactly what version you were on, I'd suggest you grab that tar and odin. Best of luck bud and let us know the Version you were on before you attemptedto root.

Flashed 930UUEU on a 930A

Just got this phone in yesterday as a replacement for a water damaged LG G3. Thought to myself that I was pretty good at rooting, flashing etc. so I decided that would be the first thing I would do. Long story short, I rooted the phone just fine and even flashed the non-bloatware-filled rom available with little problem. Then I tried to flash xposed with flashfire and, well, things didn't go so smoothly. Ended up getting stuck on the AT&T splash screen after every reboot. To attempt a fix for this I thought I would just use Odin to flash stock, what I thought was stock but was really 930UUEU, once again. I am now realizing that I flashed the wrong firmware and am currently trying to flash G930AAT once more but keep getting "FAIL! Model dismatch fail" in Odin.
Open to any suggestions at this point as I am at a loss. I've tried using a different version of Odin, 3.12.3, but to no avail have not been able to get it right. Let me know if you need any more information as to help me with this problem. Thanks in advance!

You're probably flashing an older firmware than what's on phone? Which verison are you trying to flash?

joe3681 said:
You're probably flashing an older firmware than what's on phone? Which version are you trying to flash?
Click to expand...
Click to collapse
Currently the phone boots straight into recovery. I get the update droid that fails and am sent to the options where it has me as running G930UUEU2APEH. I am pretty certain that this is the firmware I mistook as stock and half-flashed with odin. Still able to get into download mode so let's hope I can work this out!

Download the U firmware that I posted and flash that. Should flash fine. I've done it several times with the mode Odin from the root thread with zero issues

joe3681 said:
Download the U firmware that I posted and flash that. Should flash fine. I've done it several times with the mode Odin from the root thread with zero issues
Click to expand...
Click to collapse
Worked like a charm. Is there anything I should know about being on U firmware while having the 930A?

joe3681 said:
Download the U firmware that I posted and flash that. Should flash fine. I've done it several times with the mode Odin from the root thread with zero issues
Click to expand...
Click to collapse
Alright, looks like I may have run into another problem. I've rooted and flashed xposed properly this time. Kept getting a security warning so I thought it would be okay to uninstall SecurityLogAgent.apk and I am now unable to install apps. This may just be a coincidence and it may be that I have a different problem. May also be important to note that I have to reinput my WiFi password after every reset.

SubjectToReplay said:
Alright, looks like I may have run into another problem. I've rooted and flashed xposed properly this time. Kept getting a security warning so I thought it would be okay to uninstall SecurityLogAgent.apk and I am now unable to install apps. This may just be a coincidence and it may be that I have a different problem. May also be important to note that I have to reinput my WiFi password after every reset.
Click to expand...
Click to collapse
Reflash the U firmware and that will restore the security log agent app. If your rooted you'll get that notification, you'll need to freeze one of the security apps in titanium. As for the WiFi password there is a fix for it in this forum http://forum.xda-developers.com/ver...-root-install-xposed-unroot-t3411039/page230.
Also you should probably flash his V15 fixes it will fix multiple things when you root.

dirtydodge said:
Reflash the U firmware and that will restore the security log agent app. If your rooted you'll get that notification, you'll need to freeze one of the security apps in titanium. As for the WiFi password there is a fix for it in this forum http://forum.xda-developers.com/ver...-root-install-xposed-unroot-t3411039/page230.
Also you should probably flash his V15 fixes it will fix multiple things when you root.
Click to expand...
Click to collapse
Started this about 15 minutes ago. Thanks for the link to fix the WiFi issues.

dirtydodge said:
Reflash the U firmware and that will restore the security log agent app. If your rooted you'll get that notification, you'll need to freeze one of the security apps in titanium. As for the WiFi password there is a fix for it in this forum http://forum.xda-developers.com/ver...-root-install-xposed-unroot-t3411039/page230.
Also you should probably flash his V15 fixes it will fix multiple things when you root.
Click to expand...
Click to collapse
Okay, flashed everything again. Everything was working great and now I am getting that error -505 again when trying to install apps.

SubjectToReplay said:
Okay, flashed everything again. Everything was working great and now I am getting that error -505 again when trying to install apps.
Click to expand...
Click to collapse
Did you run the V 15 fix from the thread that i posted you. The fix corrects a lot of stuff

dirtydodge said:
Did you run the V 15 fix from the thread that i posted you. The fix corrects a lot of stuff
Click to expand...
Click to collapse
I did, it fixed my WiFi issues and being I flashed the debloat version it also got rid of Instagram etc. so I am certain it worked. Could it have something to do with me installing lucky patcher?

SubjectToReplay said:
I did, it fixed my WiFi issues and being I flashed the debloat version it also got rid of Instagram etc. so I am certain it worked. Could it have something to do with me installing lucky patcher?
Click to expand...
Click to collapse
Just an update. After some deduction I decided it must be lucky patcher. Uninstalled it, wiped dalvik cache and everything seems to be fine. I am still cautiously optimistic.

I'm no help on the root issues. Root isn't what it used to be so I don't really mess with it anymore.

Phone stuck in bootloop after device reset and installing stock rom

The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!

beerbat123 said:
The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!
Click to expand...
Click to collapse
Have you tried flashing the marshmallow boot loader in odin?

RomBetaTester said:
Have you tried flashing the marshmallow boot loader in odin?
Click to expand...
Click to collapse
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!

beerbat123 said:
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!
Click to expand...
Click to collapse
Google search for marshmallow bootloader and flash it through Odin. I am very good with android. I can fix your problem. Is there anyway you could direct message me?