I cant get my phone to boot past the ATT screen. I screwed up somewhere trying to change from the X-note rom and lost my data connection. Tried changing roms and that just went down hill so they i went to the MJ5 restore steps and now its really screwed up. I can get it to go into download mode and it finished a restore process but then it wont boot up do anyone have a file that i can use or something. Im totally lost now and without an actual MJ5 odin file seems like nothing works. Can anyone point me in the right direction.
redalertlb said:
I cant get my phone to boot past the ATT screen. I screwed up somewhere trying to change from the X-note rom and lost my data connection. Tried changing roms and that just went down hill so they i went to the MJ5 restore steps and now its really screwed up. I can get it to go into download mode and it finished a restore process but then it wont boot up do anyone have a file that i can use or something. Im totally lost now and without an actual MJ5 odin file seems like nothing works. Can anyone point me in the right direction.
Click to expand...
Click to collapse
Odin does not work on MJ5... That is why there are so many threads warning you not to mess with Changing from MJ5 to something else... Or anything based on MJ5... MJ5 has a locked bootsector and there is nothing to unlock it right now meaning it cannot be written over. Once you mess it up, it will stay that way till somebody cracks the boot loader and we can then use any rom... I would just try to hard brick it now and make a warranty claim. If it is hard bricked they cannot test it to see if you have tampered with it...
Solarenemy68 said:
Odin does not work on MJ5... That is why there are so many threads warning you not to mess with Changing from MJ5 to something else... Or anything based on MJ5... MJ5 has a locked bootsector and there is nothing to unlock it right now meaning it cannot be written over. Once you mess it up, it will stay that way till somebody cracks the boot loader and we can then use any rom... I would just try to hard brick it now and make a warranty claim. If it is hard bricked they cannot test it to see if you have tampered with it...
Click to expand...
Click to collapse
Spoke with Samsung and they told me to take my phone to best buy and have a samsung tech look at it because at the moment its stuck in emergency recovery. Does that make it detectable?
Once they get it to boot which they can, they will see the KNOX has tripped and you will be out of a warranty and charged for their work..
Solarenemy68 said:
Once they get it to boot which they can, they will see the KNOX has tripped and you will be out of a warranty and charged for their work..
Click to expand...
Click to collapse
Knox isnt tripped or at least when the emergency recovery screen is up knox still says 0x0
redalertlb said:
I cant get my phone to boot past the ATT screen. I screwed up somewhere trying to change from the X-note rom and lost my data connection. Tried changing roms and that just went down hill so they i went to the MJ5 restore steps and now its really screwed up. I can get it to go into download mode and it finished a restore process but then it wont boot up do anyone have a file that i can use or something. Im totally lost now and without an actual MJ5 odin file seems like nothing works. Can anyone point me in the right direction.
Click to expand...
Click to collapse
Just to be clear, your device is a samsung captivate? what about calling at&t, on another phone of course. you might also try searching the forums.
Paulita1 said:
Just to be clear, your device is a samsung captivate? what about calling at&t, on another phone of course. you might also try searching the forums.
Click to expand...
Click to collapse
No its a Samsung Galaxy Note 3 and im outside my ATT warranty but still under samsung warranty. This is what my screen says when i turn my phone on.
Odin Mode
Product Name: sm-n900a
Current Binary: Samsung Official
System Status: Official
Knox Kernal Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm secureboot: Enable (CSB)
AP SWREV: S2, T2, R2, A2, P2
Write Protection: Enable
Firmware upgrade encountered an issue. Please select recovery mode in kies & try again.
And it stays that way no matter what i do unless i try to manually put it into download mode. Other then that the phone doesnt do anything at all.
So have you tried getting Kies for your PC and using it instead of Odin?? Then use it as the phone is suggesting?
Solarenemy68 said:
So have you tried getting Kies for your PC and using it instead of Odin?? Then use it as the phone is suggesting?
Click to expand...
Click to collapse
Yes i have tried both ways and nothing works. Samsung is telling me that i need to mail them my phone and that they will try and fix it. Which basicly means that i will be without a phone until next year. So now im stuck between should i wait and hopefully a fix will be released or found or should i just send it back and feel naked for some weeks.
This is why you should always keep an old flip phone or older smart phone as a back up. I have an old Sony Ericsson flip as well as an HTC Pure in the event I need to send my Note back for service and not be without a phone. By phone I mean the actual phone. Worse case I can go two weeks with out portable internet.
I would just send it in as it looks like that will take less time then waiting for a bootloader crack..
Ok some how i got the phone to boot back up through odin with various files and it but now i have a bunch forced closes on like the direct pen input and process system isnt responded. And i dont have data...anyone know a way for me to fix the data issue?
Flash this in recovery (either side load or put it on your external sd
http://www.firmware-files.com/download.php?id=2&token=XkOmuTVDz8jO5NFRkaoxVbocRoKoQIeE
Thanks bro got it up and running smoothly now.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I have an AT&T Note 3. I was rooted using the KINGO app, but returned my phone to stock several weeks ago and the rom shows official and the knox count is 0. I am running the stock AT&T Note 3 Android 4.3
The other day, an official AT&T android update was pushed to my phone. The update bricked my phone and now I am unsure if I can even recover what was on my phone...or at the very least get it running again. For now, I am without a phone.
When I can get the phone to power up, the phone attempts to "Recovery Booting" (this is displayed in blue letters in the top left corner with the galaxy Note 3 Logo in the middle). It tries to install this AT&T update following the recovery wording when powering it on normally and when using Volume UP/Home/Power . The update progresses towards 100% then "completes" sometimes, but then the screen goes black and the phone does not start back up. I have to remove the battery for a period of time and replace to get the phone to do anything
I can get the phone to go into download mode (Volume down/Home/power), but my phone did not have USB debugging turned on the last time I was able to access the options, so it is not recognized by kies/odin, etc!
Even though their update caused the problem, AT&T wont help me (over the phone or at the store) as my phone is over a year old...their solution is to buy a new phone and plan as they say they can't do anything to fix the phone.
ANY HELP WOULD BE GREATLY APPRECIATED!
Can you get into recovery?..if so try to factory reset then maby you will be able to power up get to developer options and turn on debug so you can use odin...other option..I have heard of some doing this..go to Bestbuy Samsung counter..ask them if they have the odin tool. If they do they may be able to get you up and running.
FIREKAT V11/S5-V1
Don't worry bro.
Just follow this post to put your phone back to stock and get it rooted again. My phone used to brick and I went through it.
Follow the steps carefully, and you'll get your phone back.
http://forum.xda-developers.com/showthread.php?t=2559715
I purchased an S4 active from eBay with what I thought was a software bug, but now I'm not so sure. The phone black screens and you have to do a battery pull to reset the device. I've upgraded all the way to NE3 version by version trying to fix it. I've used ODIN to update ie. replacing everything, and still nothing. One thing also, ATT screen pops up after the Odin flash telling me the phone has unauthorized software. Then, the boot screen changes to an unlocked padlock and says Samsung custom. I figured that was what happened when the boot loader was unlocked. Is there anything else I can do before I sell this thing for parts or make it an iPod?
Edit: I've also replaced the battery.
Thanks.
Thread closed at OP's request.
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
Hi,
I have a T710 that's about 6 months old and had fairly light use.
Yesterday after charging up to 100% while off, it turned on only for the touch screen to fail to respond. The capacitive keys and fingerprint sensor and physical buttons all work perfectly, the tablet boots normally, and even responds to OK Google - but no touch is registered on the screen at all.
There is no screen protector on it and it has not been dropped or damaged. I noticed a day or two ago when playing a game that the screen was a little slow to respond, but put this down to maybe greasy fingers or a laggy game.
It is currently running a stock 5.01 Rom, although there was an update or week or two back - but I've had it working since then.
This happened once before about 3 months ago and I was in the process of returning it when I flashed a stock ROM through ODIN, which solved the problem and it worked fine until yesterday - this seems to suggest that it's not a hardware issue.
Before I go down the Odin process again and hence wipe it, are there any other things I can try that might work?
I've never rooted and the Knox counter is not tripped, so I could send it back under warranty, but that will mean sending it away and as I imported it from Hong Kong I don't know if Samsung will raise an issue (I'm UK based).
Previous googling when I had the issue before found a post or two suggesting that it was something to do with charging after letting it run down that led to others seeing the same issue - but can't find anything in this forum.
You don't need to wipe anything to flash with odin.
Just flash the latest stock firmware as is.
The easiest way to discover if it is hardware or software is to simply install TWRP.
However that will trip knox and potentially void the warranty.
The other test is to boot in safe mode.
Hold VOL DOWN while booting to the OS.
ashyx said:
You don't need to wipe anything to flash with odin.
Just flash the latest stock firmware as is.
The easiest way to discover if it is hardware or software is to simply install TWRP.
However that will trip knox and potentially void the warranty.
The other test is to boot in safe mode.
Hold VOL DOWN while booting to the OS.
Click to expand...
Click to collapse
I didn't realise that Odin flashing didn't wipe! Useful to know thanks.
I connected a mouse with a OTG lead last night so was able to back up what I wanted with Smartswitch - I then tried the device reset through smartswitch, which does wipe.
Unfortunately, that didn't resurrect the screen, so I've tried a couple of different ROMs through Odin since, with similar lack of success
Unfortunately, I don't want to find out that it needs warranty repair after installing TWRP and possibly getting that repair rejected because of a knox trip. Has anyone had experience of returning a knox tripped device with a screen fault and their response to it?
I'm going to let the battery run down fully and recharge to see if anything changes - as that is what seemed to work last time (don't ask me why though!)