Has anyone had this happen to them? Axura beta 4 was running quirky so i flashed my phone with odin 3 and then did a factory format *2767*3855#
to clear everything that odin did not. Everything nice and new all bloated and what not, thought I would give the samsung update a try "so i could use kies again" then the phone prompted to restart and did so but without the starting back up thing. I tried everything from puling the battery, download mode, recovery mode and cussing furiously at it and it did nothing. What went wrong? Is samsung gonna be able to see if i rooted the phone and all even after I did all the formatting? Before I did the update I checked to see what all was on the phone and it was like out of the box.........
Sickmutt
Happened to me when JH7 just came out. Phone was a paperweight. No power would go to the phone at all.
I exchanged it at the AT&T store...
As for them checking the root - doubt it and you reverted to stock regardless.
dang att sent me to samsung to get my phone fixed instead of helping me. that sucks that my phone gets bricked by a factory update
thanks for the fast response
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
theklxn said:
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
Click to expand...
Click to collapse
Which Odin did you use? When already on JB, you should be using Odin KK4 without bootloaders to avoid hard bricks.
If your Odin was flashing bootloaders when it got interrupted, chances are that it's hard bricked and only JTAG service will bring it back. You can contact Josh at mobiletechvideos.com for it (of course there's a fee for the service).
You can try a jig before going through JTAG service (build or buy one), maybe you'll get lucky and be able to force download mode but know that if it got interrupted while flashing the BLs, only JTAG can bring it back.
i was afriad you might say that didnt think i would have to go that far to bring it back but thank you for the swifty reponse ill get back to you when my problem has updated
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.
I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.
thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.
I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button
I am trying to unroot/flash stock rom back on my SM-G935A At&t s7 edge. I have tried both the at&t firmware and at&t unlocked. I have tried 3.12 regular odin and the modified odin from PrinceComsy. I have tried different computers and cables and all. Nothing seems to work. It is currently soft bricked but smart switch says the device is unsupported and wont allow me to run the recovery tool. When i try to flash in odin it will usually give an error on the phone "sw rev check fail : [aboot]Fused 4> Binary 2" and it will fail the flash. Any suggestions? It is not voided (0x0) and I can still get into the bootloader by doing a battery reset (hold all the buttons down) and then hold all but the up volume when it shuts off to get it into bootloader. Thankyou very much!
sxynrd34 said:
I am trying to unroot/flash stock rom back on my SM-G935A At&t s7 edge. I have tried both the at&t firmware and at&t unlocked. I have tried 3.12 regular odin and the modified odin from PrinceComsy. I have tried different computers and cables and all. Nothing seems to work. It is currently soft bricked but smart switch says the device is unsupported and wont allow me to run the recovery tool. When i try to flash in odin it will usually give an error on the phone "sw rev check fail : [aboot]Fused 4> Binary 2" and it will fail the flash. Any suggestions? It is not voided (0x0) and I can still get into the bootloader by doing a battery reset (hold all the buttons down) and then hold all but the up volume when it shuts off to get it into bootloader. Thankyou very much!
Click to expand...
Click to collapse
I'm having this exact issue, I get the same errors and everything. I've read as much forums as I could possibly manage and tried many different firmwares and versions of Odin. I hope we can get some help, because I'm not really sure what to do.
Oh its not that hard to solve all you have to do is have the correct files and place them in the correct place when using odin i would suggest looking through xda forums until you find the forum that has to do with flashing stock it works great with mine everything i mess something up in root i just restore. Ive done this a few times
Sent from my SAMSUNG-SM-G935A using Tapatalk
Savage_Realm,
As a user/contributor in XDA it is your duty to answer a question rather than just make a general suggestion. If you don't have a direct answer or solution to a question then do not post a response. Keep the meaningless chatter off this forum!
(Solved) and thank you everyone!
I have a Galaxy Note 5 for tmobile. I have been running Note 7 express rom. Also I had a backup or Hell Rom.
The problem is is I went to change the DPI settings and although I made a backup I forgot to take off the fingerprint lock or possibly delete a Google account and when the phone shut down and came back on it showed a custom boot animation. The boot animation was Biohazard.
At this time I have tried to download the last 4 firmwares DOK and PDH and the phone will go as far as to accept the boot but once it gets to where it should pass it will not. The phone will let me go into download mode however it won't let me do anything from that point and tells me that the custom binary has been blocked by FRP.
And hoping someone can help me as I can't afford a new phone at this time the phone is pristine and I'd hate to see it become a paperweight I took it in to Samsung and obviously pretended like I wasn't the one who did the damage and they said that they wasn't sure what it was or what it was doing but it wasn't working so I quickly realized that I had no help there and I thought I'd ask my brothers and sisters here.
If anyone can direct me to the right software or a proper flashing tool that might be able to get past the FRP lock please let me know as I am dying here in Ohio without my phone.
Thank you in advance all
DAD12345 said:
I have a Galaxy Note 5 for tmobile. I have been running Note 7 express rom. Also I had a backup or Hell Rom.
The problem is is I went to change the DPI settings and although I made a backup I forgot to take off the fingerprint lock or possibly delete a Google account and when the phone shut down and came back on it showed a custom boot animation. The boot animation was Biohazard.
At this time I have tried to download the last 4 firmwares DOK and PDH and the phone will go as far as to accept the boot but once it gets to where it should pass it will not. The phone will let me go into download mode however it won't let me do anything from that point and tells me that the custom binary has been blocked by FRP.
And hoping someone can help me as I can't afford a new phone at this time the phone is pristine and I'd hate to see it become a paperweight I took it in to Samsung and obviously pretended like I wasn't the one who did the damage and they said that they wasn't sure what it was or what it was doing but it wasn't working so I quickly realized that I had no help there and I thought I'd ask my brothers and sisters here.
If anyone can direct me to the right software or a proper flashing tool that might be able to get past the FRP lock please let me know as I am dying here in Ohio without my phone.
Thank you in advance all
Click to expand...
Click to collapse
Are you saying you tried stock firmware flash to phone? Download the stock firmware from samsung official website and flash through ODIN. If it fails try a different cable, try a different USB port (sometimes 2.0 and 3.0 fail for unknown reasons), try using windows 7 instead of 8, 8.1, and 10 or vice versa. Use a different version of ODIN. These are all common ODIN issues that cause flash to fail. Should accept a flash of completely stock firmware.
Let me know what you come up with.
obliviousmnd said:
Are you saying you tried stock firmware flash to phone? Download the stock firmware from samsung official website and flash through ODIN. If it fails try a different cable, try a different USB port (sometimes 2.0 and 3.0 fail for unknown reasons), try using windows 7 instead of 8, 8.1, and 10 or vice versa. Use a different version of ODIN. These are all common ODIN issues that cause flash to fail. Should accept a flash of completely stock firmware.
Let me know what you come up with.
Click to expand...
Click to collapse
Thank you, I will try those
obliviousmnd said:
Are you saying you tried stock firmware flash to phone? Download the stock firmware from samsung official website and flash through ODIN. If it fails try a different cable, try a different USB port (sometimes 2.0 and 3.0 fail for unknown reasons), try using windows 7 instead of 8, 8.1, and 10 or vice versa. Use a different version of ODIN. These are all common ODIN issues that cause flash to fail. Should accept a flash of completely stock firmware.
Let me know what you come up with.
Click to expand...
Click to collapse
Great news ! I found a photo of my settings on accident and was able to factory reset with Smart Switch. Tha k you for your time helping me.
Awesome i glad everything worked out for you. May want to edit title to [solved] or something