(Soft) Bricked Samsung Galaxy S5 Verizon - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

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

Related

[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] HELP!!!! Plz my note 3 is bricked

ODIN
Product name:sm-n900v
Current binary: Samsung official
system status: Custom
ive tried everything I can think of,its booting to Verizon stock logo but padlock screen still in custom mode any help will be great its driving me nutts!!!!
camphurt said:
ODIN
Product name:sm-n900v
Current binary: Samsung official
system status: Custom
ive tried everything I can think of,its booting to Verizon stock logo but padlock screen still in custom mode any help will be great its driving me nutts!!!!
Click to expand...
Click to collapse
remove battery, boot into odin mode, flash mje and you'll be okay.
I did that I flashed in to odin and tried to return to stock but the custom screen still remains almost like im hung up in root mode
After flashing back to stock, reboot to recovery and wipe data/factory reset
Sent from my SM-N900V using Tapatalk
Please Help
I don't know if this is the place to ask this and I apologize if it isn't. I am needing MAJOR help. My phone won't boot into recovery it will boot into odin and The Samsung Note 3 Screen that says Custom and has a lock. I don't know what to do and I am so stressed out. I shouldn't have messed with something i wasn't sure of
cljames0119 said:
I don't know if this is the place to ask this and I apologize if it isn't. I am needing MAJOR help. My phone won't boot into recovery it will boot into odin and The Samsung Note 3 Screen that says Custom and has a lock. I don't know what to do and I am so stressed out. I shouldn't have messed with something i wasn't sure of
Click to expand...
Click to collapse
If it will boot into Download (Odin) mode, then it will almost certainly be able to be flashed back to pure stock using Odin. Just make sure to use the Odin file which is equal to (or greater) the release that was on the phone. For instance, if you were on MJ7, then you could use either the MJ7 or MJE stock Odin file, but if you were on MJE, you must use the MJE Stock Odin tar.md5 file.
Note that this will completely wipe your phone.
If you flashed something non-stock to the recovery partition & your device is a retail SM-N900V, you will have blown the Knox Warranty flag and that will not be fixed by flashing back to stock. However, that means almost nothing in terms of lost functionality (but it will mean your warranty is void).
good luck
bftb0 said:
If it will boot into Download (Odin) mode, then it will almost certainly be able to be flashed back to pure stock using Odin. Just make sure to use the Odin file which is equal to (or greater) the release that was on the phone. For instance, if you were on MJ7, then you could use either the MJ7 or MJE stock Odin file, but if you were on MJE, you must use the MJE Stock Odin tar.md5 file.
Note that this will completely wipe your phone.
If you flashed something non-stock to the recovery partition & your device is a retail SM-N900V, you will have blown the Knox Warranty flag and that will not be fixed by flashing back to stock. However, that means almost nothing in terms of lost functionality (but it will mean your warranty is void).
good luck
Click to expand...
Click to collapse
Thank you for your reply, if this helps any when I rooted it a while back I used the Kingo Root, then today I decided it was being dumb I wanted to factory reset and that is when I found out recovery wasn't there. To be honest with you I don't know what was on there I do know it was Android 4.3 but that is all I know. I feel so stupid and at a lost. I have tried so many diff things and I fear I have messed it up worse. At this point I would just be happy with it booting up. Right now I have actually put my number back on my NOte 2 for now just so my kids can contact me if they need too etc. But, I have tried doing this in Odin N900vrubmj7 etc. and everytime i try to do it through odin it Fails. So would that mean I need to do the MJ5 that you mentioned. I greatly appreciate your help. Believe me i have learned a valuable lesson from this.
cljames0119 said:
Thank you for your reply, if this helps any when I rooted it a while back I used the Kingo Root, then today I decided it was being dumb I wanted to factory reset and that is when I found out recovery wasn't there. To be honest with you I don't know what was on there I do know it was Android 4.3 but that is all I know. I feel so stupid and at a lost. I have tried so many diff things and I fear I have messed it up worse. At this point I would just be happy with it booting up. Right now I have actually put my number back on my NOte 2 for now just so my kids can contact me if they need too etc. But, I have tried doing this in Odin N900vrubmj7 etc. and everytime i try to do it through odin it Fails. So would that mean I need to do the MJ5 that you mentioned. I greatly appreciate your help. Believe me i have learned a valuable lesson from this.
Click to expand...
Click to collapse
Hey, don't be so hard on yourself. You obviously aren't stupid, you asked for help. I had to reset my phone tonight from something I did in safestrap, no big deal it's all part of the root game. Shoot mine wouldn't get past the custom lock screen even after a battery pull. Anyways I would just flash up to MJE, root and be done with it. Look at it as a learning experience. Now you know what to do if the phone gets messed up again. Relax and enjoy the rest of the night.
Thank you
Misterxtc said:
Hey, don't be so hard on yourself. You obviously aren't stupid, you asked for help. I had to reset my phone tonight from something I did in safestrap, no big deal it's all part of the root game. Shoot mine wouldn't get past the custom lock screen even after a battery pull. Anyways I would just flash up to MJE, root and be done with it. Look at it as a learning experience. Now you know what to do if the phone gets messed up again. Relax and enjoy the rest of the night.
Click to expand...
Click to collapse
I appreciate that, so you are saying get MJE install that via odin? Then root and that should be it? My main thing is Odin keeps failing on the install maybe I am not using the right thing so I will look for MJE. I hate to ask this but could you give me step by step or direct me where? I appreciate this. And never touching my phone again after this nightmare!!!
cljames0119 said:
I appreciate that, so you are saying get MJE install that via odin? Then root and that should be it? My main thing is Odin keeps failing on the install maybe I am not using the right thing so I will look for MJE. I hate to ask this but could you give me step by step or direct me where? I appreciate this. And never touching my phone again after this nightmare!!!
Click to expand...
Click to collapse
No problem. Here are two excellent guides to get you through close to anything that may go wrong with the phone.
http://forum.xda-developers.com/showthread.php?t=2528707
http://forum.xda-developers.com/showthread.php?t=2543386
---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------
I forgot to answer your question, yes MJE via Oden then you will be up to date with the firmware.
Thank you
Misterxtc said:
No problem. Here are two excellent guides to get you through close to anything that may go wrong with the phone.
http://forum.xda-developers.com/showthread.php?t=2528707
http://forum.xda-developers.com/showthread.php?t=2543386
---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------
I forgot to answer your question, yes MJE via Oden then you will be up to date with the firmware.
Click to expand...
Click to collapse
Hoping for the best will let you know. Thank you
cljames0119 said:
Hoping for the best will let you know. Thank you
Click to expand...
Click to collapse
process system isn't responding that's the my problem I did everything that I could..i have a new now but still trying to get my old one working
So far so good
cljames0119 said:
Hoping for the best will let you know. Thank you
Click to expand...
Click to collapse
Well so far so good have gotten farther then I have all evening and it is on the Verizon screen as we speak drum roll please.....and it is still chugging along, Im hoping it just takes a bit to get past this and WE ARE BACK ON SERVICE!!!! THANK YOU THANK YOU
cljames0119 said:
Well so far so good have gotten farther then I have all evening and it is on the Verizon screen as we speak drum roll please.....and it is still chugging along, Im hoping it just takes a bit to get past this and WE ARE BACK ON SERVICE!!!! THANK YOU THANK YOU
Click to expand...
Click to collapse
You are very welcome, I'm glad you are up and running again.
Thanks for the help misterxtc but my problem still remains
Sent from my SM-N900V using Tapatalk
Have you confirmed the md5 to ensure you have a good download? It might be good to redownload Odin and the stock tar. Also make sure you are using the latest and greatest Odin. In you are using odin for s3 you may have issues.
Sent from my SM-N900V using Tapatalk
tpike said:
Have you confirmed the md5 to ensure you have a good download? It might be good to redownload Odin and the stock tar. Also make sure you are using the latest and greatest Odin. In you are using odin for s3 you may have issues.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yeah i did that sir but I think I damaged my EFS folder consider this is a lesson well learned and i have a retail sm n900v which I believe there isn't a fix for yet ill just keep reading up on things..no sweat i have another note 3 but just trying to fix the on i damage
Sent from my MZ617 using Tapatalk
camphurt said:
Yeah i did that sir but I think I damaged my EFS folder consider this is a lesson well learned and i have a retail sm n900v which I believe there isn't a fix for yet ill just keep reading up on things..no sweat i have another note 3 but just trying to fix the on i damage
Sent from my MZ617 using Tapatalk
Click to expand...
Click to collapse
I'll take another shot. Have you tried checking the Nand Erase All and Phone EFS Clear check boxes in Odin with the MD5 and PIT files? I have done these on my phone with no ill effects. Leave the other check boxes as they are and add those two. I got the info from here a while ago. http://forum.xda-developers.com/showthread.php?t=2610757
Misterxtc said:
I'll take another shot. Have you tried checking the Nand Erase All and Phone EFS Clear check boxes in Odin with the MD5 and PIT files? I have done these on my phone with no ill effects. Leave the other check boxes as they are and add those two. I got the info from here a while ago. http://forum.xda-developers.com/showthread.php?t=2610757
Click to expand...
Click to collapse
Ok lets give that a try.. like i said i have a back up note 3 and im not hold anyone responsible for what im ready to do.
Sent from my MZ617 using Tapatalk
I had trouble with Odin failing when trying to get my galaxy s4 back to stock. Found my computer seemed to be the problem. Maybe to old and couldn't handle it but once I moved to the newer computer in the living room it worked off the first try. Hope this helps.
Sent from my SM-N900V using xda app-developers app

[Q] unauthorized software

I stupidly tried to flash a custom recovery without unlocking the boot loader (2nd time rooting a phone) and of course now I get the message that there is software not authorized by Verizon, yada yada yada.....I can't use the phone. As I already said, I'm not very smart w/ this I guess. I rooted my phone with the new towelroot method and it worked flawlessly....but then I tried to go further and figured I'd just do everything necessary to run custom roms. Anyways, I've got the yellow triangle and I really really don't want to go to Verizon and try to talk my way into a replacement (I just got a replacement phone about 2 weeks ago) Is there any way to fix this? Before you reply, know I don't have a windows computer so I don't think I can use Odin, and my phone isn't showing up in Kies when I connect it after making sure my phone is in download mode. I'm at a loss.
Your only option is Odin, I would say find a friend with a windows computer... Then once you are back on track, read on this forum about safestrap before you flash anything else... Good luck!
Sent from my SM-N900V using Tapatalk
mattchenzo said:
Your only option is Odin, I would say find a friend with a windows computer... Then once you are back on track, read on this forum about safestrap before you flash anything else... Good luck!
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks. I know what I'm doing today now
Can anyone point me in the right direction to download the right pit file for use in Odin (Jodin3 to be specific). It's supposed to find the proper pit file automatically, but it can't for some reason. Oh, and I did do some digging....for some reason the only pit file I found (which was uploaded in Oct. of 2013) doesn't work. I can't find anything else other than that...if there is anything else.
I am trying to fix his phone for him but I am unable to find any full 4.4.2 Odin tars, are there even any available yet? The only ones I can find seem to be on websites I have never heard of haha.
Help Please
I also Rooted via Towel Method and flashed clockwork touch recovery not thinking, and i am also in the same boat. Can anyone point me in the direction of a stock TAR file to flash with ODIN, So i can get my note working again.. Any help would be great.. Thanks in advance
Shutton82 said:
I also Rooted via Towel Method and flashed clockwork touch recovery not thinking, and i am also in the same boat. Can anyone point me in the direction of a stock TAR file to flash with ODIN, So i can get my note working again.. Any help would be great.. Thanks in advance
Click to expand...
Click to collapse
Just found the link for it in this topic!
EDIT: Forgot to put in the link LOL http://forum.xda-developers.com/showthread.php?t=2783842
Worked like a CHARM!!!
draco259 said:
Just found the link for it in this topic!
EDIT: Forgot to put in the link LOL http://forum.xda-developers.com/showthread.php?t=2783842
Click to expand...
Click to collapse
Thank you, I just finished Flashing File with ODIN, Worked like a CHARM!!!! Many Many Thanks!!!!!:laugh::laugh::laugh::laugh:
Shutton82 said:
Thank you, I just finished Flashing File with ODIN, Worked like a CHARM!!!! Many Many Thanks!!!!!:laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Glad I could be of some help

My phone stopped working after trying to unroot NEED HELP

Well i rooted my device and the bugs were to much to deal with so i decided to unroot by flashing the stockedgeboot and now every time i boot my device it goes straight to recovery mode Can someone please help?
nyamd20 said:
Well i rooted my device and the bugs were to much to deal with so i decided to unroot by flashing the stockedgeboot and now every time i boot my device it goes straight to recovery mode Can someone please help?
Click to expand...
Click to collapse
odin to PG1 firmware
guaneet said:
odin to PG1 firmware
Click to expand...
Click to collapse
how exactly would i do that?
nyamd20 said:
how exactly would i do that?
Click to expand...
Click to collapse
Have you tried just selecting reboot system now.
nyamd20 said:
how exactly would i do that?
Click to expand...
Click to collapse
If you have to ask this question. Then you should of never rooted you phone. These are Basic things you should be able to do. Before you root.
nyamd20 said:
how exactly would i do that?
Click to expand...
Click to collapse
You need to download Odin, then download one of the recent firmwares like PD8 etc. Put your phone in download mode, hook it to your computer, open Odin, click AP then pick the firmware file you downloaded and hit start.
You should have Odin from when you rooted and you can find the firmware file on the forum here. Just search for PD8 or PG1.
You soft bricked your device. no big deal Samsung makes it fairly easy to fix. Download Smart Switch to your computer and use the Emergency Software Recovery/ initialization process to recover your device. You will have to re initialize your device and you will lose everything on your internal storage but your phone will be fine.
Again the root method discovered uses an ENG boot and is not meant for every day use it is not true root and will always cause more issues than it is worth.

so i tried to root my samsung galaxy s7 edge sm-935u and it's stuck in reboot loop

So after I flashed the stock rom back on the phone is functioning good and everything seems to be in order. However when i try to root it it gives me this error in odin http://prntscr.com/g3sml0 . Does anyone know why this is happening to my SM-G935U ???
Thanks for the help in advance
I still get secure check fail in odin for no reason at all
intramorph said:
I still get secure check fail in odin for no reason at all
Click to expand...
Click to collapse
It sounds like a bad download. I think you need the .tar file and not the tar.md5 file...
check and try again.
intramorph said:
So after I flashed the stock rom back on the phone is functioning good and everything seems to be in order. However when i try to root it it gives me this error in odin http://prntscr.com/g3sml0 . Does anyone know why this is happening to my SM-G935U ???
Thanks for the help in advance
Click to expand...
Click to collapse
I've tried rooting SM-G935U multiple times. The ENG boot image flashes fine in Odin but once it boots into the OS it reboots every 45-60 seconds. I never get to flash the root.bat
I'm thinking something has definitely changed. Others aren't reporting quite the same struggle I'm experiencing (at least not to the extent I have.) I just got this phone 2 weeks back. It came with Nougat.
Though I don't get any errors in Odin. Are you using the modified version?
KLit75 said:
I've tried rooting SM-G935U multiple times. The ENG boot image flashes fine in Odin but once it boots into the OS it reboots every 45-60 seconds. I never get to flash the root.bat
I'm thinking something has definitely changed. Others aren't reporting quite the same struggle I'm experiencing (at least not to the extent I have.) I just got this phone 2 weeks back. It came with Nougat.
Though I don't get any errors in Odin. Are you using the modified version?
Click to expand...
Click to collapse
No i'm using the original one from sam's mobile. I'm also on nougat. I had the same issue the first time i tried to root,got stuck in a reboot loop so i had to flash original firmware. After that my phone is working as intended but i get this error in odin now. Is there another way to root this device or am i out of luck xD
By modified version do you mean if it's a t-mobile device "for example" with the U firmware flashed? in that case no it's the original SM-G935U device.
TheOne741 said:
It sounds like a bad download. I think you need the .tar file and not the tar.md5 file...
check and try again.
Click to expand...
Click to collapse
Hi and where can i find the .tar file please. Forgive me for being such noob
intramorph said:
Hi and where can i find the .tar file please. Forgive me for being such noob
Click to expand...
Click to collapse
G935U Bootloader is locked
take a look here
https://
forum.xda-developers.com/sprint-s7-edge
intramorph said:
No i'm using the original one from sam's mobile. I'm also on nougat. I had the same issue the first time i tried to root,got stuck in a reboot loop so i had to flash original firmware. After that my phone is working as intended but i get this error in odin now. Is there another way to root this device or am i out of luck xD
By modified version do you mean if it's a t-mobile device "for example" with the U firmware flashed? in that case no it's the original SM-G935U device.
Click to expand...
Click to collapse
By modified I just meant the version of Odin youre using.
When you say you had to flash back to the original firmware, do you happen to know which version?
KLit75 said:
By modified I just meant the version of Odin youre using.
When you say you had to flash back to the original firmware, do you happen to know which version?
Click to expand...
Click to collapse
I do i used this one https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/TMK/download/G935UUES4BQG1/181625/
also i tried the modified version of odin as well as the latest. By now i've just given up. it's just not worth it imo
intramorph said:
I do i used this one https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/TMK/download/G935UUES4BQG1/181625/
also i tried the modified version of odin as well as the latest. By now i've just given up. it's just not worth it imo
Click to expand...
Click to collapse
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
KLit75 said:
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
Click to expand...
Click to collapse
It wasnt successful. It send me into a boot loop. Much like you. I couldn't run the root.bat file either. After that I just flashed original rom and that's it
Sent from my SM-G935U using Tapatalk
KLit75 said:
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
Click to expand...
Click to collapse
Hey man i was wondering if you still want to root. here's what worked for me. https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 . This method works for the sm-g935u. Also xposed works as well
The only thing i could find that was wrong was that my device was a bit laggy after rooting it but i gave it some time and it's lag-free now. I'm glad i did this. The downside is there's no custom recovery but maybe we'll get one soon. Good luck
intramorph said:
Hey man i was wondering if you still want to root. here's what worked for me. https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 . This method works for the sm-g935u. Also xposed works as well
The only thing i could find that was wrong was that my device was a bit laggy after rooting it but i gave it some time and it's lag-free now. I'm glad i did this. The downside is there's no custom recovery but maybe we'll get one soon. Good luck
Click to expand...
Click to collapse
I just rooted it Sunday night but thanks for letting me know!:good:
If you could though, please tell me which version of xposed you flashed. Was it the purify os v87 sdk24 from 7/26?
KLit75 said:
I just rooted it Sunday night but thanks for letting me know!:good:
If you could though, please tell me which version of xposed you flashed. Was it the purify os v87 sdk24 from 7/26?
Click to expand...
Click to collapse
it was purifyos and you flash the zip in Flashfire mount system

Categories

Resources