Related
Hi guys. My SGN is permanently freezing while booting. Suddenly the red lines appear and phone is stucked. It stucks on boot logo, or boot animation, or after successfull boot into system. It looks like this:
http://dl.dropbox.com/u/61718936/IMAG0003.jpg
Phone becomes quite hot on the back near camera.
I bought phone with stock 2.3.6. It was running for about 2 hours and i made OTA update to 4.0.4. It started to reboot itself while i was using it. So thought, i might use custom ROM to get rid of this freezes and reboots. But no change. Even on 4.2.1. I reverted back to 2.3.6. I noticed, that these red lines changes and moves (or even whole screen becomes red) while i'm twisting or pressing phone on various places. So i think, there is cold solder joint somewhere on motherboard. Maybe on graphic chip, because i didn't notice this problem while in recovery or download mode.
Can anybody help me with this problem, or point me on right place to look at on motherboard? Thanks in advance.
Seems to be defective device. Check with service center.
Sent from my GT-N7000 using xda premium
If you're able to, run this app to check for errors, I take it you have root. If it crashes mid scan, you've got problems with your emmc.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Sent from my GT-N7000 using xda premium
Frozen Note
I hope you will find a solution for your problem.
But I have to admit I had to smile ("grinsen" in German is a much better word for it) when I saw your title:
Freezing even when >30°C
i'm not able to run device anymore but i already tried this app for checking emmc and this is the one with that bug. But it doesn't matter, because i was flashing only safe kernels, and i don't think this emmc is problem. I think the culprit is graphic chip, or CPU, or CfRF (Chip for Random Freezes)
I was not able to find any similar problem. Tomorrow, i will try to put device into download mode, flash any custom safe kernel with CWM, leave device in this recovery, and see if it freezes again. If yes, the only option is to get device warmer for a few degrees (300-350°C with my heat station haha ) and i will see if there was any cold solder joint. If not, device will be dead anyway so i have nothing to lose
ThaiDai: you mean grin?
Tuxxperia said:
i'm not able to run device anymore but i already tried this app for checking emmc and this is the one with that bug. But it doesn't matter, because i was flashing only safe kernels, and i don't think this emmc is problem. I think the culprit is graphic chip, or CPU, or CfRF (Chip for Random Freezes)
I was not able to find any similar problem. Tomorrow, i will try to put device into download mode, flash any custom safe kernel with CWM, leave device in this recovery, and see if it freezes again. If yes, the only option is to get device warmer for a few degrees (300-350°C with my heat station haha ) and i will see if there was any cold solder joint. If not, device will be dead anyway so i have nothing to lose
ThaiDai: you mean grin?
Click to expand...
Click to collapse
Hope you find the answer dude, let us know what the outcome is.
Sent from my GT-N7000 using xda premium
Have the same problem with CM9/10 and PA ROM, freeze and getting hot...
The best ROM closest to stable for me is the RocketROM_ICS_XXLPY_v1
I got reboot problem but it is useable with this ROM
I Cant even install a Stock ROM (GB/ICS)... Stuck in Samsung LOGO, or Force Close in many apps...
diasdroid said:
Have the same problem with CM9/10 and PA ROM, freeze and getting hot...
The best ROM closest to stable for me is the RocketROM_ICS_XXLPY_v1
I got reboot problem but it is useable with this ROM
I Cant even install a Stock ROM (GB/ICS)... Stuck in Samsung LOGO, or Force Close in many apps...
Click to expand...
Click to collapse
Have you repartitioned?
Sent from my GT-N7000 using xda premium
guys i've made a small progress. I put a pressure on back side of the phone near camera, and i turned the phone on. It successfully booted to system. When i stopped pushing phones back, red lines appeared immediately and phone freezed. When i start to twist phone in hands, lines were getting bigger or smaller. When i pressed the back cover again, lines disappear (but phone was still frozen).
So now my task is, to find out, which chip is badly soldered.
ThaiDai said:
I hope you will find a solution for your problem.
But I have to admit I had to smile ("grinsen" in German is a much better word for it) when I saw your title:
Freezing even when >30°C
Click to expand...
Click to collapse
Lol perfect device for overclocking....
Sent from my GT-N7000 using Tapatalk 2
warfareonly said:
Lol perfect device for overclocking....
Click to expand...
Click to collapse
few months ago i had Samsung Omnia i900 only working in fridge or when it was freezed with frost spray
this phone is mystery. When the battery is fully charged, it works like a charm. I can twist the phone as much i want, it won't freeze. I don't understand.
My n7000 has also this same problam pl. any one help me..
Tuxxperia said:
this phone is mystery. When the battery is fully charged, it works like a charm. I can twist the phone as much i want, it won't freeze. I don't understand.
Click to expand...
Click to collapse
My galaxy note n7000 has same problem from last 3 days i also not found any solution for this when i use phone without scrow fited on back cover my phone working fine only in 1 % of battey but when i tite scrow in back cover my phone frize at galaxy boot logo or samsung logo with or without red line...pl. any one help me... pl....
You guys started having strange issues with ur notes. Maybe its something like a self destruct programmed on your phones so that after a year or two people will switch their phones. Besides the bigger the phones are getting the more issues they are having.
A phone should be like a device that shouod work flawless, in case of emergency one is needing to make a call and found that the phone freezed.
Sometimes i blame everything to android. Despite years of open development. Its yet not stabilizing, i guess because of it being open source vendors are putting crap in it making it more vulnerable to issues.
I dont rely on android rather i use a cheap phone for calls and text or iphone. Its just good for internet, ebooks, movies, music and camera.
Sent from my GT-N7000 using xda app-developers app
Try pulling out the battery and then let the phone dry like a pair of wet socks. Clean the contacts and fit any loose thing that there may be.
Check your cable, if is loose or not, this way you could find if there were any unwanted sparks applied on the device.
Notice how it gets hot when is plugged in and you're using it? the battery reaches quickly 55 degrees which is not optimum, wait to cool to below this temperature.
My condolences in this sad event. Take care.
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
interesting, try to catch the evnts in the logs, use elixer/logcat/android tuner for that.
Check the battery dude.
I had similar problesm due to bad battery.
Phone was closing itslef. And before it closesi thescreen was turning crazy
Then no boot at all....
ardicli2000 said:
Check the battery dude.
I had similar problesm due to bad battery.
Click to expand...
Click to collapse
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
JolyonS said:
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
Click to expand...
Click to collapse
I was outside when faced such a big problem. It was happening before like reboobs and stucks on logo. But after i took out the battery for 15 min I was able to boot the phone.
However, eventually, one day phone got stuck with a flickering screen and then it never booted. Tired nandroid restore. Did not help. Changed kernels etc. It was no good either. Then I changed battery. Did not work again Then made a factory reset. It worked. Using it without any problem now. But even at that time I was able to see my files in the phone via Qadb. This could be your case as well.
Try changing battery if it is older than 9 months. Make a full pit fresh Stock install.
Then Reboot. I hope t will work
JolyonS said:
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
Click to expand...
Click to collapse
Me too, i have some problem.
delete-
ardicli2000 said:
if it is older than 9 months.
Click to expand...
Click to collapse
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
JolyonS said:
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
Click to expand...
Click to collapse
Glad to hear that problem is solved
As the title suggests, I downloaded the app AParted by sylkat through Google Play in order to partition my EXTERNAL SD-card. However, in the hurry of doing this, I believe I have formatted the INTERNAL SD-card, which has resulted in a pretty much dead phone.
It does not respond to anything. I have tried all combinations, the hard-reset button, everything I can think of. My computer is no longer able to recognize it either.
I am then wondering if there is a way to recover the data in the internal SD-card, or just any fix?
Some info:
- My device is fully rooted with BL unlocked.
- I had installed iHackers 2.0 ROM on it
- I have backups made through TWRP-recovery
All help is highly appreciated. Thank you
- Sari95
Sari95 said:
It does not respond to anything. I have tried all combinations, the hard-reset button, everything I can think of. My computer is no longer able to recognize it either.
Click to expand...
Click to collapse
So you can't get into recovery, fastboot, or flash modes?
What happens if you plug the device in to charge?
Unless you can get into recovery, it's unlikely that you'll be able to recovery anything. If you do manage to flash a bootable ROM onto the phone, you'll be writing onto the internal SD card and physical overwriting all your old data, removing the possibility of recovery.
If you can get into recovery, you may be able to connect USB, mount the internal SD partition, and then try running a file recovery tool on it. I don't know if the whole USB mounting bit will actually work, haven't tried that.
If you formatted the internal memory of your phone forget to try recover the data. It's close to impossible and for laboratory experienced only. Even if you try many files can be corrupted and it will not work anyway. I try many apps for classic HDD and they recover almost pictures and mp3 only, and if many files are in sub-folders this get more complicated.
If you have a backup of your entire system I will suggest to go back to Stock flashing original FTF then go through all the process to get again iHackers 2.0 ROM on your phone and when you can access to the TWRP recovery, restore your latest backup and you will have your phone back like it was before formatting.
eclyptos said:
If you formatted the internal memory of your phone forget to try recover the data. It's close to impossible and for laboratory experienced only. Even if you try many files can be corrupted and it will not work anyway. I try many apps for classic HDD and they recover almost pictures and mp3 only, and if many files are in sub-folders this get more complicated.
If you have a backup of your entire system I will suggest to go back to Stock flashing original FTF then go through all the process to get again iHackers 2.0 ROM on your phone and when you can access to the TWRP recovery, restore your latest backup and you will have your phone back like it was before formatting.
Click to expand...
Click to collapse
I expected that. My main problem is that it does not do anything at all. If I had been able to connect it to my computer, I would have probably been able to fix it, but it does not connect to anything at all.
My only saviour would be a so-called "Jig", which boots the device into android through an SD-card, but I am not sure whether there exists one for Z1 or how to make one myself.
So is there any way of connecting or just giving the phone a breath of life through an SDcard-solution?
Probably only through the Update Service or Emma...
http://developer.sonymobile.com/services/flash-tool/
jamespmi said:
Probably only through the Update Service or Emma...
http://developer.sonymobile.com/services/flash-tool/
Click to expand...
Click to collapse
I have tried both EMMA and SUS without success.
xasbo said:
So you can't get into recovery, fastboot, or flash modes?
What happens if you plug the device in to charge?
Unless you can get into recovery, it's unlikely that you'll be able to recovery anything. If you do manage to flash a bootable ROM onto the phone, you'll be writing onto the internal SD card and physical overwriting all your old data, removing the possibility of recovery.
If you can get into recovery, you may be able to connect USB, mount the internal SD partition, and then try running a file recovery tool on it. I don't know if the whole USB mounting bit will actually work, haven't tried that.
Click to expand...
Click to collapse
Yes, I have tried all those.
1. Tried powerbutton + volume up -> nothing happened
2. Powerbutton + volume down --> nothing
3. plug into the wall --> nothing
4. Plug to computer --> nothing
Considering the internal SD-card, which acts as the brain of the phone, is formatted. The "brain" has been removed, thus it does not know what to do when I push the buttons or plug it to the computer.
Sari95 said:
Considering the internal SD-card, which acts as the brain of the phone, is formatted. The "brain" has been removed, thus it does not know what to do when I push the buttons or plug it to the computer.
Click to expand...
Click to collapse
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.
You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
xasbo said:
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.
You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
Click to expand...
Click to collapse
Hmmm... that I am not sure of.
Exactly! no vibration nor LED light when I push the powerbutton. Imagine yourself pushing the button, yet it is as if you did not push it at all. I have tried the force-off button too, so my last and final solution seems to be the service center.
Thanks for your replies! HIghly appreciated
xasbo said:
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.
You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
Click to expand...
Click to collapse
Sari95 said:
Hmmm... that I am not sure of.
Exactly! no vibration nor LED light when I push the powerbutton. Imagine yourself pushing the button, yet it is as if you did not push it at all. I have tried the force-off button too, so my last and final solution seems to be the service center.
Thanks for your replies! HIghly appreciated
Click to expand...
Click to collapse
WOOOPPP! I have some kind of development actually. Now, when I plug the device to the wall or computer, a red
LED lights up for about 3 seconds before disappearing. However, from here nothing happens and it is dead as usual.
Any idea how to go further from here ?
From what I've read. That means the battery is completely dead.
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
lil-diabo said:
From what I've read. That means the battery is completely dead.
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
Click to expand...
Click to collapse
This is a good point, I didn't consider a dead battery scenario (though it makes a lot of sense versus the phone just doing nothing). I haven't actually read about cases where USB charging will bring back a super dead phone, but it's theoretically possible if the battery were removed and charged manually. That process, however, is definitely only for people who know what they're doing with potentially explosive battery chemistry. If nothing else, leave it plugged in for a while and see what happens.
I remember posting in another thread where someone killed their battery. The best preventative measure is to make sure you never get below 10% or so. The generally dispersed "knowledge" that taking the battery to 0% is good for calibration is NOT TRUE. These are Li-ion batteries, and deep discharges permanently reduce the battery capacity.
lil-diabo said:
From what I've read. That means the battery is completely dead.
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
Click to expand...
Click to collapse
xasbo said:
This is a good point, I didn't consider a dead battery scenario (though it makes a lot of sense versus the phone just doing nothing). I haven't actually read about cases where USB charging will bring back a super dead phone, but it's theoretically possible if the battery were removed and charged manually. That process, however, is definitely only for people who know what they're doing with potentially explosive battery chemistry. If nothing else, leave it plugged in for a while and see what happens.
I remember posting in another thread where someone killed their battery. The best preventative measure is to make sure you never get below 10% or so. The generally dispersed "knowledge" that taking the battery to 0% is good for calibration is NOT TRUE. These are Li-ion batteries, and deep discharges permanently reduce the battery capacity.
Click to expand...
Click to collapse
Great point, you two.. This reason seems quite probable too. However at the same time, it is WEIRD if the battery suddenly dies as a result of formatting the internal SDcard :l
Maaan, I had a slight hope, but I'll try charging it overnight.
Worst case scenario, the service center finds out I had rooted it and I have to pay for the service....
Sari95 said:
Great point, you two.. This reason seems quite probable too. However at the same time, it is WEIRD if the battery suddenly dies as a result of formatting the internal SDcard :l
Maaan, I had a slight hope, but I'll try charging it overnight.
Worst case scenario, the service center finds out I had rooted it and I have to pay for the service....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2574764
There's an entire thread dedicated to how people bricked their phones. Have a look there for some info
It all relates to flashing phones, but maybe what you done had some kinda of a similar effect
Do you remember how much charge you had left?
Supposedly the system loses calibration with the battery and and and and (Most of this relates to flashing though, so hopefully you just have a completely dead battery and an overnight charge will fix it back up.
I also don't think you lose warranty from having your phone rooted?
Think voiding warranty only applies if you unlocked your boot loader... - I could be wrong though.
Good Luck!
Sari95 said:
WOOOPPP! I have some kind of development actually. Now, when I plug the device to the wall or computer, a red
LED lights up for about 3 seconds before disappearing. However, from here nothing happens and it is dead as usual.
Any idea how to go further from here ?
Click to expand...
Click to collapse
Actually I saw this behavior on deads Z1 thread, sorry to say, this actually is not a good sign.
lil-diabo said:
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
Click to expand...
Click to collapse
Yes, I will suggest this too and when your phone apparently will be charged try just to push volume down and connect via usb to pc and see if it will be recognized. If he dose flash a stock FTF immediately.
lil-diabo said:
http://forum.xda-developers.com/showthread.php?t=2574764
There's an entire thread dedicated to how people bricked their phones. Have a look there for some info
It all relates to flashing phones, but maybe what you done had some kinda of a similar effect
Do you remember how much charge you had left?
Supposedly the system loses calibration with the battery and and and and (Most of this relates to flashing though, so hopefully you just have a completely dead battery and an overnight charge will fix it back up.
I also don't think you lose warranty from having your phone rooted?
Think voiding warranty only applies if you unlocked your boot loader... - I could be wrong though.
Good Luck!
Click to expand...
Click to collapse
Yea, I read through a few pages of that thread, but didn't feel it covered my case. I had a minimum of 89% of battery and it was charging. Hmm.. about the battery calibration, the day before this happened, I charged my phone to 100% and used Battery calibrator, which is an app in Play Store to calibrate it, so this shouldn't be a problem.. However, I suppose something has happened during the formatting.
I am quite certain one loses warranty when rooted or has unlocked BL.
eclyptos said:
Actually I saw this behavior on deads Z1 thread, sorry to say, this actually is not a good sign.
Yes, I will suggest this too and when your phone apparently will be charged try just to push volume down and connect via usb to pc and see if it will be recognized. If he dose flash a stock FTF immediately.
Click to expand...
Click to collapse
Indeed, this seems to be my last way out of this. Either it comes back to life in the morning, or I am doomed! haha I have even prepared FLASHTOOL and the firmware, if the phone actually comes back to life and is recognized by the computer.
I will update you on this! You are a very helpful group of people. I am grateful for your help so far :good:
Sari95 said:
Yea, I read through a few pages of that thread, but didn't feel it covered my case. I had a minimum of 89% of battery and it was charging. Hmm.. about the battery calibration, the day before this happened, I charged my phone to 100% and used Battery calibrator, which is an app in Play Store to calibrate it, so this shouldn't be a problem.. However, I suppose something has happened during the formatting.
I am quite certain one loses warranty when rooted or has unlocked BL.
Indeed, this seems to be my last way out of this. Either it comes back to life in the morning, or I am doomed! haha I have even prepared FLASHTOOL and the firmware, if the phone actually comes back to life and is recognized by the computer.
I will update you on this! You are a very helpful group of people. I am grateful for your help so far :good:
Click to expand...
Click to collapse
Woke up today and tested it. No sign of life at all so it is now sent to the service center..
Thank you for your help! You have helped me a lot
I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol
Is there a way I can test the internal memory?
Hello, guys! I had my Xiaomi Redmi 9t for 6 months now and so far I only encountered minor problems, not until now. Before that, I never did turned my phone off for a very long time or I have never restarted it, but since I noticed that my GPS was crappy---because it didn't show any accurate data while I'm using the Strava app to track my bicycle rides. So, I restarted it and after that the screen just went total black, it never responded despite of how long I pressed the power button, and also I just unplugged it from the charger because it was almost full. I was also able to use it few minutes after the restart without any problems, I heard from other users who owned this phone that this also the same problem they are encountering.
Also, it's not bricked or anything because it was still functioning normally. For not being bricked, I cannot access the fastboot mode since I cannot even turn it on.
If you try to charge it again, does the screen turns on then shows a charging animation?
dinsel said:
If you try to charge it again, does the screen turns on then shows a charging animation?
Click to expand...
Click to collapse
It doesn't do anything. There's no display neither a vibration.
Your device is dead booted. The cause might be related to hardware. So, what I recommend for you is to bring that to a service center to get fixed or replaced. F.
dinsel said:
Your device is dead booted. The cause might be related to hardware. So, what I recommend for you is to bring that to a service center to get fixed or replaced. F.
Click to expand...
Click to collapse
yeah, there are a lot of fellow Filipino users who complained about the same problem. But I think it's also about the latest firmware update, because my younger sisters had the phone but they did not have any of my problem and their firmware versions aren't updated yet.
And just to think of it, the latest update also made my phone cranky. The wifi suddenly turns off and on and the GPS thing (which i mentioned in the post).
You have not been able to press the power + volume button for 10 seconds to achieve something?
ceesarsu said:
You have not been able to press the power + volume button for 10 seconds to achieve something?
Click to expand...
Click to collapse
No. He can't.
derunheimlich said:
Hello, guys! I had my Xiaomi Redmi 9t for 6 months now and so far I only encountered minor problems, not until now. Before that, I never did turned my phone off for a very long time or I have never restarted it, but since I noticed that my GPS was crappy---because it didn't show any accurate data while I'm using the Strava app to track my bicycle rides. So, I restarted it and after that the screen just went total black, it never responded despite of how long I pressed the power button, and also I just unplugged it from the charger because it was almost full. I was also able to use it few minutes after the restart without any problems, I heard from other users who owned this phone that this also the same problem they are encountering.
Also, it's not bricked or anything because it was still functioning normally. For not being bricked, I cannot access the fastboot mode since I cannot even turn it on.
Click to expand...
Click to collapse
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Did it get wet?
LR7875 said:
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Click to expand...
Click to collapse
LR7875 said:
Plug it into a computer. Search for device manager in the windows search box. If it shows 'Qualcomm 9008' or something like that, it can be fixed but only in a service center. If it shows 'unknown usb port' then you lack the usb drivers, but still can be fixed. If it does not show in computer, not even 'unknown usb device', your device is not bricked, it is gone for good (or maybe the usb port is fried and also the battery drained, you can replace them as a last resort)
Click to expand...
Click to collapse
I turned it over to the service center yyesterday. They told me that it'll be fixed tomorrow or friday. Which I'm really hoping.
blackhawk said:
Did it get wet?
Click to expand...
Click to collapse
No. I haven't even dropped it
Had the same problem today, phone is updated to the lastest firmware. Just woke up and the phone isn't even turning on, tried fastbooting while charging but nothing at all on the screen. Didn't get it wet nor dropped it. Guess we gotta replace the phone huh.
I don't update. The first thing disable is OTA updates. Many apks still running factory load versions as well.
In over 1.5 years on Pie, no factory resets due to malware. My current load is over a year old, still fast and stable.
Rule#1 if your OS is running fast, stable and fulfilling its mission... let it be.
blackhawk said:
I don't update. The first thing disable is OTA updates. Many apks still running factory load versions as well.
In over 1.5 years on Pie, no factory resets due to malware. My current load is over a year old, still fast and stable.
Rule#1 if your OS is running fast, stable and fulfilling its mission... let it be.
Click to expand...
Click to collapse
Completely agreed if you have a Xiaomi. I regretted updating to MIUI 12 because it is s l o w.
LR7875 said:
Completely agreed if you have a Xiaomi. I regretted updating to MIUI 12 because it is s l o w.
Click to expand...
Click to collapse
Doesn't matter what OS; leave a strong running OS alone... as long as you understand it's vulnerabilities. Even a malware forced reload be easier than putting up with a doggy OS every second of every day
blackhawk said:
Doesn't matter what OS; leave a strong running OS alone... as long as you understand it's vulnerabilities. Even a malware forced reload be easier than putting up with a doggy OS every second of every day
Click to expand...
Click to collapse
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
LR7875 said:
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
Click to expand...
Click to collapse
Yeah the whole Hulk SMASH thing... maybe a lobotomy is more civilized.
LR7875 said:
MIUI android 11:
Unfortunately, system UI has stopped.
Me:
Grabs a drill
Click to expand...
Click to collapse
At the moment my mobile is all great, it is a little more fluid with android 11
No idea, man. Sounds serious problem.