Help! I did something stupid. - AT&T Samsung Galaxy S 5

I was using safestrap to try and install a custom rom, I wiped my stock rom but my phone ended up dying (I didn't see that the charger wasn't plugged in) now I can't do anything at all. IT just gets stuck on the samsung galaxy s5 logo. I cannot flash any AP I just get an auth failed error. I tried using the G900AUCU3BOC4_OneClick but I get an error on that as well. Please help me. I figured that I don't have an OS to boot into now. And I cant downgrade from 5.0 am I screwed?

So you can't put your phone into download mode and ODIN your old firmware back on to the phone?
Please post everything ODIN shows when you attempt so we can try and help you further. Might want to try flashing with the BL and PIT file as well.
P.S. I don't know what G900AUCU3BOC4_OneClick is, but google took me to
http://www.theandroidsoul.com/att-galaxy-s5-lollipop-update-odin-firmware-80652/
And that doesn't look legit. Make sure you get all of your firmwares from here or sammobile.com. The "Odin" on that page doesn't even look like odin.

at&t s5 active sm-g870a
I was trying to root my phone following instructions on this site.
I installed the NE4 that was about 10+mb.
then I got stuck on the screen with red font that says "android system recovery <3E>"
I can still flash in download mode.
I attempted to install the full NE4 available from this site which is about 2.3 gig and it says FAIL! (Auth)
So then i attempted to load NG3 available from this site and it was sucessful but I'm still stuck on the "android system recovery boot.
Would anyone happen to know where I might get the "G870AUCU280F3 ROM"?
Also does anyone know what NAND erase all does when the box is checked in Odin 3.09?
Im thinking about checking that box and trying again.
for now I'm thrilled that I can still get to download mode and I don't want to mess that up.

In general section.
Sent from my SAMSUNG-SM-G870A using Tapatalk

XRange said:
In general section.
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
thank you so much sir, but i do not understand your post.
I do very little with computers and internets and forums.
I've been scouring this site for the info i need and I'm either not smart enough to know what i'm looking for or this site is so vast that it may take more than a few days to learn how to navigate it.
I will say that I find it unsettling that the forum doesn't seem to recognize that our phones (sm-g870a) even exist, as evidenced by typing s5 active in the equipment box.
but meanwhile i will search for a general section.

Sean89us said:
So you can't put your phone into download mode and ODIN your old firmware back on to the phone?
Please post everything ODIN shows when you attempt so we can try and help you further. Might want to try flashing with the BL and PIT file as well.
P.S. I don't know what G900AUCU3BOC4_OneClick is, but google took me to
http://www.theandroidsoul.com/att-galaxy-s5-lollipop-update-odin-firmware-80652/
And that doesn't look legit. Make sure you get all of your firmwares from here or sammobile.com. The "Odin" on that page doesn't even look like odin.
Click to expand...
Click to collapse
I can get into download mode just fine. However, when I try to flash it. I get the fused binary error. Regardless of the firmware.

squirt r6 said:
thank you so much sir, but i do not understand your post.
I do very little with computers and internets and forums.
I've been scouring this site for the info i need and I'm either not smart enough to know what i'm looking for or this site is so vast that it may take more than a few days to learn how to navigate it.
I will say that I find it unsettling that the forum doesn't seem to recognize that our phones (sm-g870a) even exist, as evidenced by typing s5 active in the equipment box.
but meanwhile i will search for a general section.
Click to expand...
Click to collapse
Squirt,
if you have a question, please submit your own question in this thread instead of hijacking somebody else's question with an off-topic one. I suggest you take XRange's advice and check the "General" section of the "AT&T Samsung Galaxy S 5" thread.
http://forum.xda-developers.com/att-galaxy-s5/general
Had you checked the general section, you would see that the 4th post down is exactly what you are looking for.
http://forum.xda-developers.com/att-galaxy-s5/general/how-to-update-to-g870aof2-5-0-keeproot-t3161733
Also, S5 actives do not need a separate thread, they are identical hardware-wise to the S5.
---------- Post added at 08:33 AM ---------- Previous post was at 08:25 AM ----------
rbxrootx said:
I can get into download mode just fine. However, when I try to flash it. I get the fused binary error. Regardless of the firmware.
Click to expand...
Click to collapse
At this point I recommend you try and use Samsung's Kies software to restore your phone to factory, then you can start over with rooting or flashing roms.
Guide here:
http://forum.xda-developers.com/showthread.php?t=1984717
Please note that the link on that page to download kies is broken, so you can find kies here (you will want to download kies3):
http://www.samsung.com/in/support/usefulsoftware/KIES/
Good luck, and let us know how it goes.

Sean89us said:
Squirt,
if you have a question, please submit your own question in this thread instead of hijacking somebody else's question with an off-topic one. I suggest you take XRange's advice and check the "General" section of the "AT&T Samsung Galaxy S 5" thread.
http://forum.xda-developers.com/att-galaxy-s5/general
Had you checked the general section, you would see that the 4th post down is exactly what you are looking for.
http://forum.xda-developers.com/att-galaxy-s5/general/how-to-update-to-g870aof2-5-0-keeproot-t3161733
Also, S5 actives do not need a separate thread, they are identical hardware-wise to the S5.
---------- Post added at 08:33 AM ---------- Previous post was at 08:25 AM ----------
At this point I recommend you try and use Samsung's Kies software to restore your phone to factory, then you can start over with rooting or flashing roms.
Guide here:
http://forum.xda-developers.com/showthread.php?t=1984717
Please note that the link on that page to download kies is broken, so you can find kies here (you will want to download kies3):
http://www.samsung.com/in/support/usefulsoftware/KIES/
Good luck, and let us know how it goes.
Click to expand...
Click to collapse
Thank You sean89us, and sorry I didn't mean to hijack your thread RobotX, i just figured that if were in the same predicament whatever fixes yours may fix mine.
My bad

kies says it is not compatible with the phone so I had to install a new program which acted like it was going to do the trick. After 3 hours, It quit and told me that it was unable to complete the task.

Related

issues with flashing custom recovery

I used ODIN and all the correct files/methods to work with the Mini for my friend. The whole reason behind flashing CWM to it was so I could make a backup of it before flashing CM7.. It says completed and that I can remove the cable but just sits at the "ANDROID" logo when trying to enter recovery; WTD?! Anyhelp?
Has no-one developed a better way of flashing custom recovery, hell the wildfire was "S-on" and they figured a hardware-less way of removing it which was FREE.
Any help is appreciated!
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
abdovar said:
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
Click to expand...
Click to collapse
Or for a better version, go to http://forum.xda-developers.com/showthread.php?t=1529863 and download 5.0.2.8, a touch version that works great on the Mini.
The Odin and Tass in the link you provided are still fine though.
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
JackJack762 said:
I used ODIN and all the correct files/methods to work with the Mini for my friend. The whole reason behind flashing CWM to it was so I could make a backup of it before flashing CM7.. It says completed and that I can remove the cable but just sits at the "ANDROID" logo when trying to enter recovery; WTD?! Anyhelp?
Has no-one developed a better way of flashing custom recovery, hell the wildfire was "S-on" and they figured a hardware-less way of removing it which was FREE.
Any help is appreciated!
Click to expand...
Click to collapse
A few things, first of all, you cannot backup stock roms with CWM, you can back up data and apps with other backup programs.
You could have used your stock recovery to flash a CWM.zip file instead but that wouldn't have helped you either if you have the wrong version of CWM.
Regarding your last comment... You're not making any sense at all.
Basically, you did something wrong with your friends mini and now you want to blame anything but yourself for your own mistakes, that's not going to fix the mini.
abdovar said:
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
Click to expand...
Click to collapse
Yeah it said PASS sorry, I hadnt had the phone for one or two days so I just put Complete as a stand-in for the word PASS. I'll give it a try and hope for the best
Jinxxed said:
Or for a better version, go to http://forum.xda-developers.com/showthread.php?t=1529863 and download 5.0.2.8, a touch version that works great on the Mini.
The Odin and Tass in the link you provided are still fine though.
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
A few things, first of all, you cannot backup stock roms with CWM, you can back up data and apps with other backup programs.
You could have used your stock recovery to flash a CWM.zip file instead but that wouldn't have helped you either if you have the wrong version of CWM.
Regarding your last comment... You're not making any sense at all.
Basically, you did something wrong with your friends mini and now you want to blame anything but yourself for your own mistakes, that's not going to fix the mini.
Click to expand...
Click to collapse
I'll give that a try too, I wasn't blaming anything but my self.. I was just saying that this way is an over complicated system; There are better programs and ways that have been developed for most other Android devices like my R800i or my girlfriends ACE. Ok I didn't know about the back-up issue but I've done that via Supermanager anyway.
JackJack762 said:
Yeah it said PASS sorry, I hadnt had the phone for one or two days so I just put Complete as a stand-in for the word PASS. I'll give it a try and hope for the best
I'll give that a try too, I wasn't blaming anything but my self.. I was just saying that this way is an over complicated system; There are better programs and ways that have been developed for most other Android devices like my R800i or my girlfriends ACE. Ok I didn't know about the back-up issue but I've done that via Supermanager anyway.
Click to expand...
Click to collapse
Yeah, considering the ACE has the exact same tools, i think you are just full of sheit.
You can do it all via Rom Manager/Rom Toolbox/someotherprogram if you'd like, it's just that experience tells us that it works best if you do it in the simplest way possible because that is the most likely to work.
So either you want what works or you can search market, why didn't you do that in the first place if rebooting was too hard for you?
Just so you know, none of those apps will save your arse when your phone won't boot, right about then your knowledge about how to fix it from the recovery will save your arse in front of your girlfriend.
So say pretty please thank you and go away.
---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------
JackJack762 said:
Yeah it said PASS sorry, I hadnt had the phone for one or two days so I just put Complete as a stand-in for the word PASS. I'll give it a try and hope for the best
I'll give that a try too, I wasn't blaming anything but my self.. I was just saying that this way is an over complicated system; There are better programs and ways that have been developed for most other Android devices like my R800i or my girlfriends ACE. Ok I didn't know about the back-up issue but I've done that via Supermanager anyway.
Click to expand...
Click to collapse
Wait, you used the galaxy mini versions on your R800i and a Galaxy Ace?
Didn't work? WELL OF COURSE NOT!
Err no. I think you have read what I said wrong.
I have flashed the ACE and the R800i via other methods which work alot better, no need to be an asshole. I never used "ODIN" with the ACE so you can stop being such an ass when you need to read the post prior to posting.
I used flashable CWM on the ace then flashed new roms from that. Not ODIN, I used "x10 Flash tool" for the R800i.
So no I will not say "Thanks" and go away. You see, Unlike you I don't sit inside ALL of my life I have the ability and the hardware to flash any EEPROM or pretty much anything that needs to be accessed as thats my JOB. in the BRITISH ARMY.
Grow up and find something better to do than troll people.
thx
abdovar said:
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
Click to expand...
Click to collapse
Thx for the link

[Q] 807p tab s wifi and lte

I came here looking for root help with this device. I see the autoroot by chainfire is not listed for this. Can i get some direction on how to go about it?
Sm-t805 version should work
Kahun said:
Sm-t805 version should work
Click to expand...
Click to collapse
Ok i understand that you think it should work even though it is not the same nomenclature. Why should i believe that it should work when the nomenclature is different? What are my available options of in fact ir doesnt work and my device is bricked? I saw on other post in this forum on th 807p and it appears the person in that thread now has a bricked device that can not be recovered. So you see my reluctance to trust something that isnt clearly marked as for use with the nomenc.ature of my device. Thanks for your help with this.
liz.beth said:
Ok i understand that you think it should work even though it is not the same nomenclature. Why should i believe that it should work when the nomenclature is different? What are my available options of in fact ir doesnt work and my device is bricked? I saw on other post in this forum on th 807p and it appears the person in that thread now has a bricked device that can not be recovered. So you see my reluctance to trust something that isnt clearly marked as for use with the nomenc.ature of my device. Thanks for your help with this.
Click to expand...
Click to collapse
Could possibly brick try at your own risk if your desperate. Like you said I would just wait for it to get released.
In case it wasn't clear, I acknowledged that the device isn't listed in that thread, as such I am seeking other options for rooting my device. Are there other options available for rooting it?
This is the thread for you to ask:
http://forum.xda-developers.com/showthread.php?t=1980683
He'll need a copy of the recovery file that's inside the rom file. So you'll need access to the full file which I'm not sure it's even been released (try and get it so you have a copy for the future).
Sent from my SM-G900P using Tapatalk
Itchiee said:
This is the thread for you to ask:
http://forum.xda-developers.com/showthread.php?t=1980683
He'll need a copy of the recovery file that's inside the rom file. So you'll need access to the full file which I'm not sure it's even been released (try and get it so you have a copy for the future).
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Thanks for the clue. I still have less than 10 posts so i cant ask a question there yet. Maybe if we post back and forth enough here ill get b my 10 post requirement met?
I tried to find a copy of the ROM your using (T807PVPU1ANH1) but its not available at the regular locations....
http://samsung-updates.com/
http://www.sammobile.com/
No downloads on the Sprint and Samsung sites...
Samsung tablets are fairly hard to destroy as long as you can access recovery (and use Odin to flash a stock ROM) or get this Kies program to work.
i considered trying to extract the recovery.img but after installing android studio and the Java jdk, there seems to be some issue with android studio not recognizing the jdk path so I quit. . If you have some ideas, I'd be glad to take in any assistance you have.

i'm stumped. s5 will not boot past samsung logo

after a FULL wipe bad flash to cm12 on my part, i restored with odin 3.09 with g900auc1ance firmware. it shows success on odin, but upon reboot, i still get the samsung "custom" with open padlock. then it attempts to boot and the samsung logo does it's thing and only completes about 80% of the logo, then goes dead/blank with blue led lightly pulsing. i took it to bestbuy to the samsung kiosk hoping the tech could help. he scolded me and showed me his at&t s5 running cm12. i'm stumped. any help would be appreciated.
i've rooted and rommed every android i've had and have always been able to fix it., all thanks to XDA.
Could it have been a bad download of ANCE. I've seen that happen before. Either a bad download or a bad transfer from comp/phone to sd card. I'd try re downloading
will do
will try that now. hoping it works.
nope. tried and same results.
Perhaps try Odin 3.10? Could it be that simple.
Also did you try a different source for the file you were trying to flash?
magnumglock said:
after a FULL wipe bad flash to cm12 on my part, i restored with odin 3.09 with g900auc1ance firmware. it shows success on odin, but upon reboot, i still get the samsung "custom" with open padlock. then it attempts to boot and the samsung logo does it's thing and only completes about 80% of the logo, then goes dead/blank with blue led lightly pulsing. i took it to bestbuy to the samsung kiosk hoping the tech could help. he scolded me and showed me his at&t s5 running cm12. i'm stumped. any help would be appreciated.
i've rooted and rommed every android i've had and have always been able to fix it., all thanks to XDA.
Click to expand...
Click to collapse
Number one you CANNOT run CM 12 or ANY AOSP or custom kernel on the G900A due to the locked bootloader whoever told you that flat lied to you
I'm assuming you've taken the 444 update correct??
Go to this thread http://forum.xda-developers.com/showthread.php?t=3021120read OP scroll down to the troubleshooting section and download the downgrade to NCE rar. Extract the downgrade to NCE tar md5 place phone in download plug it in and using Odin 3.09 place the tar in the ap slot then flash let it complete wait til phone boots then you'll be back to bone stock NCE phone.
I did the 4.4.4 and I'll give this a shot this evening. Again, thank you for the help.
*edit*
I have not tried Odin 3.10. I downloaded the files from the restore threads link to a google drive storage.
Odin 3.10 works fine. Don't forget to wipe cache and Davi. Sometimes that's all you need. And I agree, do some research first before you try flashing anything. Our locked bootloader makes us different.
Will do. I'll update what I find this evening.
magnumglock said:
I did the 4.4.4 and I'll give this a shot this evening. Again, thank you for the help.
*edit*
I have not tried Odin 3.10. I downloaded the files from the restore threads link to a google drive storage.
Click to expand...
Click to collapse
OK I figured you took the 4.4. 4 update go to the link I provided and if you read OP it states that if one has trouble with the first downgrade rar to go to the troubleshooting section.
Download the Downgrade to NCE rar in the troubleshooting section and extract the Downgrade to NCE md5 tar.
Using Odin 3.09 put phone into download mode plug it in you'll see added in the box.
Place the Downgrade to NCE tar md5 file into ap slot and press start it will work. I've done it several times myself and helped quite a few people in your place as well
Let phone completely boot up and you'll have a bone stock device ready to start over.
OPOfreak said:
OK I figured you took the 4.4. 4 update go to the link I provided and if you read OP it states that if one has trouble with the first downgrade rar to go to the troubleshooting section.
Download the Downgrade to NCE rar in the troubleshooting section and extract the Downgrade to NCE md5 tar.
Using Odin 3.09 put phone into download mode plug it in you'll see added in the box.
Place the Downgrade to NCE tar md5 file into ap slot and press start it will work. I've done it several times myself and helped quite a few people in your place as well
Let phone completely boot up and you'll have a bone stock device ready to start over.
Click to expand...
Click to collapse
this solved my problem. i cannot express how appreciative i am for your help.
magnumglock said:
this solved my problem. i cannot express how appreciative i am for your help.
Click to expand...
Click to collapse
A simple thank you is sufficient I'm glad you're squared away now.
The good thing is now if you soft brick your device you know how to get back to stock.
Happy flashing :thumbup::thumbup:
The same exact thing has happened to me.
OK, I am panicking now. My ATT GS5 is doint the exact same thing.
I will try the NCE rar too and let ya'll know how it went.
---------- Post added at 11:27 PM ---------- Previous post was at 10:59 PM ----------
Dodged that bullet. Got rid of Custom status too. Very cool
I am having the same issue but with a "there is no PIT partiton" error
I have tried everything that I could to get my phone working again. I even downloaded a so called pit file that apparently didn't work because the error keeps coming up. Is there a legit PIT file that I can download and if so could someone please point me in that direction? Also if someone could please help me to get my phone working again I would also appreciate that. I just bought this phone off of ebay and I am trying to get it working as my regular phone. when I start the phone up there are two lines at the top of the screen 1 is a white line that says MMC read fail error or something to that effect, and there's another line in red that says movinand confirmation error. After about 3 to 4 minutes of waiting the phone will go into download mode by itself and give me a whole bunch of lines one of which will say: Knox 0x0.
is there a way I can either repair or repartition the phone? I spent 6 hours trying to figure this out. I am tired.
Thanks in advance for any helpful response.

HELP!!! bootloop/ bricked phone

when i press the power button i can see the "Samsung galaxy note 4" thing and then after a couple seconds it does it all over again.
https: //gyazo.com/ 7253cff1fd13dba02df89eae9df6d1a1 (sorry cant post links yet delete spaces)
i downloaded the stock firmware from Sammobile and it still will not work.
i went to tmobile and told them this is happening they said Samsung will send you a new phone but i didn't tell them my phone is rooted
does anyone think that they will not give a new phone if i say anything?
i tried putting TWRP and starting but the most it goes to is download mode. a least it turns on... :crying: :crying:
please someone help me this is the only phone i have
EDIT: is there a way to make the knox counter 0x0 from 0x1? if can do that i would send the phone to samsung
when i go into download mode it says "SYSTEM STATUS: CUSTOM" even though i restored everything to the official firmware
re: boot screen blinks
proman505 said:
when i press the power button i can see the "Samsung galaxy note 4" thing and then after a couple seconds it does it all over again.
https: //gyazo.com/ 7253cff1fd13dba02df89eae9df6d1a1 (sorry cant post links yet delete spaces)
i downloaded the stock firmware from Sammobile and it still will not work.
i went to tmobile and told them this is happening they said Samsung will send you a new phone but i didn't tell them my phone is rooted
does anyone think that they will not give a new phone if i say anything?
i tried putting TWRP and starting but the most it goes to is download mode. a least it turns on... :crying: :crying:
please someone help me this is the only phone i have
EDIT: is there a way to make the knox counter 0x0 from 0x1? if can do that i would send the phone to samsung
Click to expand...
Click to collapse
Don't worry, they will not ask you anything about knox or root.
Tmobile won't even look for root or knox in the first place unless you tell
them all those details.
Also you do not need to exchange your phone because it's a simple fix.
You must have installed or flashed something which is not compatible
with your N910T Tmobile phone which caused the issue you are having.
The only reason you have not had any luck in fixing it yourself is the fact
that you do not have enough experience yet to figure it out and you have
not read enough posts here in xda about your particular issue.
The problem you are having with your phone is not a new one, many people here
have had the exact same problem with their phones and have solved the problem.
The first thing you need to remember is to always follow the instructions to a "T" before
flashing firmwares, roms, kernels, recoveries, themes and any mods or addons.
If you do not fully understand the posted instructions here in xda then post a question
regarding your specific issue before you do anything.
Good luck,
Have a great day!
Sorry, but currently your warranty is void forever.
Are you following Odin instructions correctly? <-Most important step
Are you flashing the correct firmware for your phone? <-Also important
Have you tried different versions of Odin?
Are you getting a PASS when using Odin?
Misterjunky said:
Don't worry, they will not ask you anything about knox or root.
Tmobile won't even look for root or knox in the first place unless you tell
them all those details.
Also you did not need to exchange your phone because it's a simple fix.
The only reason you have not had any luck in fixing it yourself is the fact
that you do not have enough experience yet to figure it out and you have
not read enough posts here in xda about your particular issue.
The problem you are having with your phone is not a new one, many people here
have had the exact same problem with their phones and have solved the problem.
The first thing you need to remember is to always follow the instructions to a "T" before
flashing firmwares, roms, kernels, recoveries, themes and any mods or addons.
If you do not fully understand the posted instructions here in xda then post a question
regarding your specific issue before you do anything.
Good luck,
Have a great day!
Click to expand...
Click to collapse
i am 100% sure that i flashed the right stuff. the phone worked perfectly but then it just turned off and then got stuck in a bootloop for some reason. im gonna try to send it to samsung and not say anything about rooting it hopefully they will fix it
if you dont mind linking me what firmware i should use to restore it. i dont care about my data its already gone anyway.
Edit: how do i make the system status official because it says custom right now
xanmato said:
Sorry, but currently your warranty is void forever.
Are you following Odin instructions correctly? <-Most important step
Are you flashing the correct firmware for your phone? <-Also important
Have you tried different versions of Odin?
Are you getting a PASS when using Odin?
Click to expand...
Click to collapse
yes if you look at the link in the post odin seems to have no errors.
i followed the instruction right from sammobile and many youtube videos
www .sammobile .com /firmwares/download/46452/N910TUVU1COD6_N910TTMB1COD6_TMB/
thats what i used

Bricked

It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
So going by the lack of feedback I'm basically screwed?
Oh for ****s sake come on! I've had this up for 3 days on this site full of so called enthusiasts and "professionals" and not one response? I'm sorely disappointed.
So there is honestly no one that can help me with this?
Pathetic...
Come on there must be someone that can help me with this, otherwise I'll have to risk buying a broken one for parts.
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Grumpy Cat said:
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
Click to expand...
Click to collapse
TheMadTurnip said:
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Click to expand...
Click to collapse
Thanks for the feedback but as I have already stated I can't access any recovery only Odin, and desktop Odin won't allow me to re-partition only write. Still, whether it be stock or a custom ROM it is the same result: bootloop and recovery freezes on splash screen.
So any other takers? Yes? No?
Why even have a "help & troubleshooting" section if, well, I don't know, no one helps!!!
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
The problem you've described suggests that you're phone is 'fixable' however, it may take a few different methods to restore it. Ok, so you cannot access recovery mode, therefore you're unable to clear your phone like TheMadTurnip suggested, and you're also unable to access any backup you might have made. The downloader works so I can only recommend you try to investigate what's going wrong when you flash via Odin, does the flash show as pass or fail? Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin? Is Kies installed on your computer, if so then remove it. Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Kind Regards,
Pinda
Pinda007 said:
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
Click to expand...
Click to collapse
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
Pinda007 said:
does the flash show as pass or fail?
Click to expand...
Click to collapse
It shows a pass, won't allow me to re-partition though.
Pinda007 said:
Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin?
Click to expand...
Click to collapse
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
Pinda007 said:
Is Kies installed on your computer, if so then remove it.
Click to expand...
Click to collapse
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
Pinda007 said:
Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Click to expand...
Click to collapse
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Grumpy Cat said:
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
It shows a pass, won't allow me to re-partition though.
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Click to expand...
Click to collapse
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop, using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Pinda007 said:
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Click to expand...
Click to collapse
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Grumpy Cat said:
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Click to expand...
Click to collapse
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Pinda007 said:
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Click to expand...
Click to collapse
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Grumpy Cat said:
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Click to expand...
Click to collapse
I think that's the exact file that worked for me
I don't know what else to suggest at the moment, the fact that you cannot get into recovery makes it that much harder.
I'll come back to you if something comes to mind.
EDIT- Have you tried re flashing a custom recovery to overwrite your current one? If you can somehow get into recovery you could trying clearing your phone of cache and installing a ROM zip-folder. Also, have you got another battery you can try in your handset? I cannot help you with the Odin method no because you've pretty much exhausted all the possible solutions that I know of, perhaps screenshot the Odin log and post it on here for more info.
My s3 mini also got same problem.any solution found

Categories

Resources