Related
Please help me guys, I have no one else to turn to. My parents are gonna kill me if they find out what I did to my phone.
So my phone accidentally fell at school with the bluetooth still on.So I put the battery pack, power it on, but then it started to go on a boot loop i.e.
Sony logo-->Xperia Logo-->color animation-->black screen. But after 3-4 hours, it managed to do a complete boot! But I noticed that the bluetooth wasnt turning on. So stupid me, I restarted the device, then it started to go on a boot loop again. I got home and I tried it a couple of times more with the power and volume rocker combinations... didnt work either.
I even started using pc companion. didnt work (kept on doing the same thing
SUS --> same thing
NOW: I tried it using a different computer so I went to an internet shop and downloaded pcc and sus. I started pc companion... but halfway through the download... MY PHONE RAN OUT OF BATTERY and didnt finish the update. :'( Now, whenever I'm booting the phone, I only get the Sony logo and A TRIANGLE WITH AN EXCLAMATION MARK AND A PHONE UNDERNEATH.....
PLEASE HELP ME! My Phone is a Sony Xperia TX Lt29
Last Version before the crash: JB 4.1.2
No root (Noob here)
please... please. i dont know what to do. thank you in advance to anyone who can help me
calm down.
Charge the phone until it is fully charged.
Download PCCompanion and do a fresh install of it.
Run PCCompanion and choose software update.
Use the option to repair your phone, then follow the instructions.
Let us know how you get on
PS
This will only do a software repair, if something broke because you dropped it (Which it sounds like) you are going to have to come clean and tell your parents to get it fixed.
HI gregbradley '^^
gregbradley said:
calm down.
Charge the phone until it is fully charged.
Download PCCompanion and do a fresh install of it.
Run PCCompanion and choose software update.
Use the option to repair your phone, then follow the instructions.
Let us know how you get on
PS
This will only do a software repair, if something broke because you dropped it (Which it sounds like) you are going to have to come clean and tell your parents to get it fixed.
Click to expand...
Click to collapse
THANK YOU FOR YOUR REPLY!!! really thank you :'(
I already did something with the phone because I've been doing a lot of searching on the net lately...
I reinstalled the software using Sony Update Service (SUS) and it booted normally! (but sadly it was only during the FIRST BOOT UP) when I turned off the phone to re insert the sim card and micro sd, It started doing it again... but then, after 6 or 7 tries, it managed to skip past the sony logo-->xperia--> logo-->color animation? and do another complete boot
Now I decided to go to settings and do a complete factory reset cause I thought it would fix everything... but it didn't. It started doing the same thing, and I had to give it 10 or 12 tries before eventually booting up again. When it booted up normally, I was even able to play music with it and change the settings like brightness, volumes, equalizers, and even arrange widgets!
SITUATION NOW:I turn on the Wi-fi and it's in a boot loop again and I'm charging the phone up to 100%
(i did the vol.up vol down power combination before charging)
gregbradley, is it because of our slow internet connection??? (it took me like 4 nerve racking hours to finish the update) but sus was able to complete the download and install the software... what the f*ck is wrong with my phone (((( ohgod
AND:
I'll follow your instructions when the charge is complete...... and I'll be back to you with the results.God I hope this works.Thank you again.
Have you tried only partially flashing part of an ftf file. I know when my phone was on the brink of death I discovered that if I only flashed part of an ftf using flashtool that it would work. I think I would check everything that has exclude (ie: Exclude System) and it would work for me. Its not the end of the world though as the phone does work. Just a bootloop. If you can get it into flash mode then just exclude everything except System, Kernel, and baseband if I'm not mistaken.
hi Cammarratta '^^
Cammarratta said:
Have you tried only partially flashing part of an ftf file. I know when my phone was on the brink of death I discovered that if I only flashed part of an ftf using flashtool that it would work. I think I would check everything that has exclude (ie: Exclude System) and it would work for me. Its not the end of the world though as the phone does work. Just a bootloop. If you can get it into flash mode then just exclude everything except System, Kernel, and baseband if I'm not mistaken.
Click to expand...
Click to collapse
Thank you for the reply man '^^
um... to tell you the truth, I have no idea how to partially flash a tft file, let alone flashing. O_O (see how noob i am?) its saddening. So am I in the point right now where my phone's problem is unsolvable via pc companion or sony update service??? Plus I've been doing some searching here on xda and I saw this thread about xperia TX users updating to version b 167 and that their bootloaders are now locked.
This is what my phone is exactly doing whenever I try to boot it up:
Sony Logo---->Xperia Logo----> Color waves animation?---> FREEZE-->black screen then the Sony Logo again.
Whenever I try to boot up for the 2nd time this happens:
Sony Logo----> Black Screen---> Phone turns off---> Sony Logo again
(((
You have flashtool yes? If you load up like you're going to flash a ftf file. Once you click to load up the ftf file it'll pull a menu where you pick what you want to flash. On the right side of flashtool that's where the exclude part is. That's where you have to check the *exclude option. The same thing happened to me when I accidentally flashed a T cm10 rom on my phone. I had to partially flash a ftf file to get it to boot. It should work but since you're not familiar with flashtool its going to make it a bit harder for you in the end. :/
carloptimus3d said:
Please help me guys, I have no one else to turn to. My parents are gonna kill me if they find out what I did to my phone.
So my phone accidentally fell at school with the bluetooth still on.So I put the battery pack, power it on, but then it started to go on a boot loop i.e.
Sony logo-->Xperia Logo-->color animation-->black screen. But after 3-4 hours, it managed to do a complete boot! But I noticed that the bluetooth wasnt turning on. So stupid me, I restarted the device, then it started to go on a boot loop again. I got home and I tried it a couple of times more with the power and volume rocker combinations... didnt work either.
I even started using pc companion. didnt work (kept on doing the same thing
SUS --> same thing
NOW: I tried it using a different computer so I went to an internet shop and downloaded pcc and sus. I started pc companion... but halfway through the download... MY PHONE RAN OUT OF BATTERY and didnt finish the update. :'( Now, whenever I'm booting the phone, I only get the Sony logo and A TRIANGLE WITH AN EXCLAMATION MARK AND A PHONE UNDERNEATH.....
PLEASE HELP ME! My Phone is a Sony Xperia TX Lt29
Last Version before the crash: JB 4.1.2
No root (Noob here)
please... please. i dont know what to do. thank you in advance to anyone who can help me
Click to expand...
Click to collapse
just let it plug in with the charger and keep your phone on for day, usually that will fix it after a few hours with that logo running
Use a battery charger, charge for at least half the entire batt and then follow the thread on flashing, download some files while charging to minimize downtime
Sent from my LT29i using xda premium
Hey guys...... ))))
First and foremost, thank you for all your replies.. really helped me a lot (
It's okay now guys! '^^ I re installed the software via Sony Update Service and it worked. At first I thought the phone was a goner cause it didn't manage to do a complete boot right after the installation. (Phone was stuck on the Sony Logo) But then the next morning, I tried it again and it worked!!
BUT: What I fear now is that the phone might suddenly crash again if I turn on the WI-FI (just like what happened in my previous attempts) If the phone crashes, I fear that the phone would start going on a boot loop again.So basically, I'm just using the phone for media purposes only i.e. Walkman, Gallery,Camera, Movies.
Any thoughts on this, cool, awesome people of xda? '^^ (cant update my apps and google now f*ck)
just.. sad. I miss Flipboard,Modern Combat 4, My Daddy Was a Thief, Real Racing 3, DEAD SPACE (((
one question...
Did something broke inside my phone when it fell?? If yes... WHAT EXACTLY IS IT?? why is it behaving this way??? Why does it keep on boot looping??? should I go and let an expert open it????
carloptimus3d said:
First and foremost, thank you for all your replies.. really helped me a lot (
It's okay now guys! '^^ I re installed the software via Sony Update Service and it worked. At first I thought the phone was a goner cause it didn't manage to do a complete boot right after the installation. (Phone was stuck on the Sony Logo) But then the next morning, I tried it again and it worked!!
BUT: What I fear now is that the phone might suddenly crash again if I turn on the WI-FI (just like what happened in my previous attempts) If the phone crashes, I fear that the phone would start going on a boot loop again.So basically, I'm just using the phone for media purposes only i.e. Walkman, Gallery,Camera, Movies.
Any thoughts on this, cool, awesome people of xda? '^^ (cant update my apps and google now f*ck)
just.. sad. I miss Flipboard,Modern Combat 4, My Daddy Was a Thief, Real Racing 3, DEAD SPACE (((
Click to expand...
Click to collapse
If it's only when you start the wifi it's an hardware problem.
Send it to service
hello
Cammarratta said:
You have flashtool yes? If you load up like you're going to flash a ftf file. Once you click to load up the ftf file it'll pull a menu where you pick what you want to flash. On the right side of flashtool that's where the exclude part is. That's where you have to check the *exclude option. The same thing happened to me when I accidentally flashed a T cm10 rom on my phone. I had to partially flash a ftf file to get it to boot. It should work but since you're not familiar with flashtool its going to make it a bit harder for you in the end. :/
Click to expand...
Click to collapse
What version for ftf version for xperia tx should i flash???? the ics one??? the latest??? helppp
and should i check everything that's in the exclude option?
The latest one, and don't exclude anything
Sent whilst sat on the toilet.
hi all
I think I probably know the answer to this but just to make sure..
I have for a long time had gregs Assaye-V2.0.1, which was great but was starting to slow down somewhat. so for my sins I tried with CM 10(.1 i think) still not quite sure about the differences between cm10 versions, but I digress.
anyway I put cm 10.1. I tried both FXP and so called stable CM release and its been a nightmare.
GPS problems, camera problems, browser problems - basically multiple reboots daily making the phone pretty much unusable. so thinking that I would like to get back to the beginning. I would like to maintain root and retain CWM but avoid the standard bloat that comes with stock roms.
Happy to bung a custom kernel on there, not after massive speed as I don't play games, battery life and reliability are paramount for me.
I wonder if someone could recommend the best way to go about this, and possibly a FTF/Kerne/ROM to go with that recommendation.
is it worth re-locking the bootloader for instance? can you even do that and maintain root.. ? so many questions - sorry I have gotten rather out of touch.
I would stick Assaye on again but seems it hasn't moved for quite some time and not sure if there is a better option.
any help very much appreciated
just to be clear - my current situation is:
Xperia T bought from Phones 4U
rooted
unlocked bootloader
currently running CM 10.1
thanks
nat
Thanks for using my rom, I hope it worked fine for you
In order to go back to stock you MUST relock the bootloader. Or you can flash doomkernel (which is for stock roms) and before you let it boot properly go into recovery and flash a stock based rom
If you relock the bootloader your phone will bootloop on CM if you try to turn it on, don't worry, just run pccompanion and force a repair of the software.
Then your phone will be exactly the same as when you took it of the box, so you can start again..
EDIT
My rom never updated because it was always just for me, and I was happy with it, now I have a Z1 and my daughter has my T, she hates my rom ;( and insists on CM
hi greg
thanks for the reply
guess I would be happy with a stock based rom to retain root. could you recommend one - other than your own?
which as it happens I am bunging back on as i type this...
thanks
also how do I set the buttons back to the original ones..?
sur eI have asked this before but cant find the answer...
To get back to original stock then once you have locked the bootloader just run pccompanion and force a repair of you r software in software update,
To get the button back to stock just push a stock systemUI.apk to system/app or better still install xposed framework and xblast module.
I think it works on the T, try it
http://forum.xda-developers.com/showthread.php?t=1574401
then with the xblast module you gat a choice of buttons plus a load of other options as well
hi
so, I flashed the ftf re-lock bootloader.
all appeared to go well but....
I have been trying to no avail to get pc companion to run a repair.
the phone will not turn on, all I get when i hit the power is the led flashes red briefly twice, I can keep holding the power and it will keep doing a double rad flash every second or so.
when I plug into the pc - as part of the repair process - ie. holding down vol + power. I get a windows sound for connecting then another for disconnecting - I havent of course actually pulled it out at this point.
any ideas?
guessing its just not getting the green led for flashmode thus pc companion is not going to run a repair...
any other suggestions..?
thanks
edit: seems it has connected with a green led now.. however - it does not stay connected long enough for pc companion to fully download the update and i have to start all over again..
is there any way I can download the update separately and sort it that way..
Leave it on charge on your wall charger for the rest of the day, then try pccompanion later tonight
hi
thanks for the replies.
I had left it charging all last night. seems that it will only stay in flashmode for a short time, which isnt long enough to complete the flashing
the downloading part of the pc companion had completed and it was doing to pc -> phone bit, but never completes as green light goes off before it finishes..
I will leave it charging again overnight, but fear the worst.
presumably flashing a stock ftf with flashtool would achieve similar results?
will give that a go too and see how it goes..
hoping that I could run pc companion after doing that if it works?
n
xda-nat said:
hi
thanks for the replies.
I had left it charging all last night. seems that it will only stay in flashmode for a short time, which isnt long enough to complete the flashing
the downloading part of the pc companion had completed and it was doing to pc -> phone bit, but never completes as green light goes off before it finishes..
I will leave it charging again overnight, but fear the worst.
presumably flashing a stock ftf with flashtool would achieve similar results?
will give that a go too and see how it goes..
hoping that I could run pc companion after doing that if it works?
n
Click to expand...
Click to collapse
if lfashtool works then yes...but not sure what your issue is here...
finally success, managed to use flashtool to flash parts of the ftf at a time, left it charging overnight and booted up fine in the a.m.
then have just ran pc companion to get a fresh stock one on.
thing is even though I have done that, it has still kept all the random folders on the internal storage, is there any way to clear them. PC companion says it will wipe them but it doesnt seem to have done so..
thanks
nat
xda-nat said:
finally success, managed to use flashtool to flash parts of the ftf at a time, left it charging overnight and booted up fine in the a.m.
then have just ran pc companion to get a fresh stock one on.
thing is even though I have done that, it has still kept all the random folders on the internal storage, is there any way to clear them. PC companion says it will wipe them but it doesnt seem to have done so..
thanks
nat
Click to expand...
Click to collapse
Backup everything you want to save to your pc, then format internal storage in settings
Glad to hear you have it working again
Hi
i had paranoid android installed but the baseband was the wrong one..
(I installed iHackers 4.1 without flashing kernel + baseband because then i landed in a bootloop)
When on ihackers i installed paranoid android 4.4.4 over it and it worked. But also like in ihackers
i could not connect to my network because of the wrong baseband.
So i downloaded C6903_14.4.A.0.108_Generic_DE.ftf and flashed only the baseband without wiping anything..
Restarted .. baseband hasn't changed but the system booted and everything was fine.
Than i flashed only the kernel and the baseband without flashing anything else and wiping anything.
The phone went dead. Really dead. Power + vol+ which allways worked (3xvibrate) not working.
LED not working .. Just dead!!! i have it on the charger because before the last flashing it was @ about 15 - 20 % accu.
But even when i connect the charger .. no led .. nothing .. its playing dead.
Any Idea? (it is .. now that i remember .. not the first time a z1 went that dead on me.. I had a z1 before which did the same. now in retrospective I remember flashing kernel and baseband (ONLY) also on that phone.. and it went dead.
If somebody likes to trash his/her z1 try flashing only baseband and kernel. (I am sure the kernel and the baseband are the correct one for the firmware.)
Any ideas how to reanimate my z1?
vG
Thomas
You have flashed a stock kernel to a custom rom, so of course you will get a bootloop.
Solution, flash a stock FTF, after leaving the phone on charge for a few hours
and post your questions in the Q&A section
Cant get into flashmode or fastboot mode.. it does not react on any button combination
gregbradley said:
You have flashed a stock kernel to a custom rom, so of course you will get a bootloop.
Solution, flash a stock FTF, after leaving the phone on charge for a few hours
and post your questions in the Q&A section
Click to expand...
Click to collapse
Leave it for a few hours....
gregbradley said:
You have flashed a stock kernel to a custom rom, so of course you will get a bootloop.
Solution, flash a stock FTF, after leaving the phone on charge for a few hours
and post your questions in the Q&A section
Click to expand...
Click to collapse
gregbradley said:
Leave it for a few hours....
Click to expand...
Click to collapse
Thank you for your answer. =) I have unlearned to read messages till the end. Sorry =)
Have you tried the red button on the SIM tray slot?
Also refer to this thread:
http://forum.xda-developers.com/showthread.php?t=2574764
Poesini said:
Have you tried the red button on the SIM tray slot?
Also refer to this thread:
http://forum.xda-developers.com/showthread.php?t=2574764
Click to expand...
Click to collapse
yes .. i pushed it several times and also for ab 12 sec. nothing happens.
This happened to me when I first got my Z1. Unfortunately I had to send my phone back to Sony which they ended up replacing the motherboard.
They won't be able to detect any custom firmwares. Waiting time is unfortunately about 14 business days once they receive it...
If you phone is unlocked be sure to let them know so you get an nck unlock code. You will have a new imei.
khhhhris said:
This happened to me when I first got my Z1. Unfortunately I had to send my phone back to Sony which they ended up replacing the motherboard.
They won't be able to detect any custom firmwares. Waiting time is unfortunately about 14 business days once they receive it...
If you phone is unlocked be sure to let them know so you get an nck unlock code. You will have a new imei.
Click to expand...
Click to collapse
This is not a motherboard issue, it just needs charging for a few hours and then reflashing. Also he has lost his warranty due to unlocking so since this happened as a direct result of flashing custom roms he wont e able to claim on warranty
I understand this is not a motherboard issue, however the exact same problem happened to me months ago. Even after waiting overnight and trying to enter flash mode again it would not respond properly.
Sony's solution is to replace the motherboard at the repair facility I'm assuming because it is the easiest method.
I can almost guarantee this is what will happen when you send it in and they won't deny you warranty.
If you cannot get your phone into flash mode after a few hours, try again overnight. If not I would send it in, or get your carrier to replace it.
Repeat this magic phrase: "I updated my phone and it wouldn't turn on"
gregbradley said:
This is not a motherboard issue, it just needs charging for a few hours and then reflashing. Also he has lost his warranty due to unlocking so since this happened as a direct result of flashing custom roms he wont e able to claim on warranty
Click to expand...
Click to collapse
khhhhris said:
it.
Repeat this magic phrase: "I updated my phone and it wouldn't turn on"
Click to expand...
Click to collapse
Please do not condone fraud on XDA
Now you are deviating from the original intention of this thread. This is absolutely not fraud. It is a vague statement at best.
Your "Recognized Contributor" status and high post count does not give you authority to belittle other users.
Just trying to spread community support which is the purpose of xda, is it not?
Unsubscribed.
gregbradley said:
Please do not condone fraud on XDA
Click to expand...
Click to collapse
Well that excalated quickly...
Sent from my C6903 using XDA Premium 4 mobile app
TommyX235 said:
yes .. i pushed it several times and also for ab 12 sec. nothing happens.
Click to expand...
Click to collapse
Did you try the guide posted there?
http://forum.xda-developers.com/showthread.php?t=2646405
Well you flashed a stock kernel on a CM based rom and thought it would work?
Don't come for Greg as he's the nicest member on here.
Need help
Hi,
I've run pac-rom on my Z1. Now I want to flash from the current .109 firmware only the base band. In Flash Tool under exclude everything except I labeled baseband. Then the flash process starts without error message. When I start the phone is still the old baseband version. What am I doing wrong?
Thank you
[email protected] said:
Hi,
I've run pac-rom on my Z1. Now I want to flash from the current .109 firmware only the base band. In Flash Tool under exclude everything except I labeled baseband. Then the flash process starts without error message. When I start the phone is still the old baseband version. What am I doing wrong?
Thank you
Click to expand...
Click to collapse
Maybe its the same baseband?
No,
old version is .39, and the new from .108 is .51
Hey thanks for your answers @ all!!
The failure was that i flashed roms / ftf with very low battery. Than i charged for a few hours and flashed again .. and on and on.
At some point the accu seems to got broken.
I send it to a repair facility used by sony and they confirmed that the accu is dead.
It seems that i get a replacement. (on warranty)
Thank you again. ! SO!!! What we learn from this is "Only flash your device when its charged!"
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Lohot said:
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Click to expand...
Click to collapse
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
http://www.flashtool.net/index.php
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Hnk1 said:
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
Click to expand...
Click to collapse
Lohot said:
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Click to expand...
Click to collapse
There's nothing sweeter than using a phone for a long time and getting a brand new !
Enjoy mate. No trouble. Just quote me again in case you have any query for me.
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