My XT resets everything to stock after the battery dies... - Sony Xperia T, TL, TX, V

A week ago I noticed that after my phone's battery was drained out it reset itself. Every app datawas deleted permamently. The phone acted like a new one. The only apps that were untouched were system apps. Some of the apps installed a previous day were also deleted but its data stayed untouched in /data/data. I had to move these datas one folder up, install these apps again and then move datas back to use the apps just like the day before. But this case with datas happens only for the "uninstalled" ones, the rest of the apps that were not magically self-uninstalled were reset to the state when they are just installed.
About 20 minutes ago it happened again. But I noticed how my phone acted before the battery-drainage death. It dropped just to 2% and then suddenly switched off without any information about "shutting down" or anything. Only the LED blinked 3 times but nothing else... I plugged my phone to the charger and switched it on and voila... it was turning on for about 3 minutes nd everything is reset AGAIN.
Is anyone able to help me? I use .141 FW but this happened on .140 too. Also I have DooMKernel v7 flashed...
Tapped from The Bond Phone!

I have similar problem, after doing many restarts with usb dis/connections, partitions remounts, etc.
I have endless bootanimation and from log I can see that IMEI has 0 lenght and ATcmdfwd service won't start.
Manual factory reset solves it. (I learned to make backups with titanium every day)
Sometimes this happens after shutdown without notification.
Also using DK7 and my rom.
What other mods do you have same as I do?

No serious mod installed at all. Only DK7 on stock ROM and nothing else. I'm really worried because it never happened before, my phone was shutting down with an information and everything was ok. But for a week I was insanely careful not to discharge the battery completely because I didn't want to restore old backups again... but I was curious if this happen again and my thoughts became true...
Tapped from The Bond Phone!

Hmm, so I am suspecting the kernel. I think I will try to return to v5 for a few days.
Maybe it is caused by the Dynamic file sync.

Try everything stock , stock ROM ,stock kernel ,no mods at all. See if it still happens.
Sent from my LT30p using xda app-developers app

Try flashing a other kernel if that does not maybe trying a different ROM will work "cough" cm10.1 "cough

ArmaNineTSeven said:
Try everything stock , stock ROM ,stock kernel ,no mods at all. See if it still happens.
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
AndroidHoneyComb said:
Try flashing a other kernel if that does not maybe trying a different ROM will work "cough" cm10.1 "cough
Click to expand...
Click to collapse
Thanks for the tips! I discharged my phone again and this time it shut down at 4% but with the notification so everything is ok this time but earlier I uninstalled Kernel Tuner and these two resets happened with KT installed. I've installed it again and I will drain the battery another time and see if this was a cause.
Tapped from The Bond Phone!

Damn, guys... my phone did that again. I'm on XperimenT 3.0 ROM and I was playing Galaxy on Fire 2 when I fell asleep and my phone died. I woke up, turned it on and it was like waiting in a huge queue for about 15 minutes and voilà - everything is reset to stock except from all messages were kept, all accounts were kept, all setting were kept. This is pretty annoying as I don't want to do a backup every single day...
Is anyone still able to help me? If this problem persist I will be thinking about selling this phone and moving to another and I don't want to do this because for now it's a waste of money for me...

Returning to DK v5 solved this kind of problem for me.

Related

[Q] Bricked Milestone, stuck at Motorola logo

Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result

Boot loop after CM7 & Baseband 15

Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
bytecodeboy said:
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
Click to expand...
Click to collapse
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Mod issue or battery or hardware fault
Cheshire-Cat said:
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Click to expand...
Click to collapse
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
bytecodeboy said:
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
Click to expand...
Click to collapse
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
stamatis16 said:
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
bytecodeboy said:
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
Click to expand...
Click to collapse
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
stamatis16 said:
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
Click to expand...
Click to collapse
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
bytecodeboy said:
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
Click to expand...
Click to collapse
yea, i guess your battery almost dead.....and i dont think its a good idea to by new battery, you better buy new phone,as the batteries are quite expensive if you think that the worth of the x8 right now would be 50 euros....
Try ebay bro
Sent from my E15i using Tapatalk 2
Flash rom with xrecovery not cwm
Sent from my X8 using xda premium

[Q] Help with my s3mini

My s3 mini is freaking out I don't know if it is a virus, but my home button freaks out. Without me touching it, it will bring up the recent apps menu and close out my apps and return to the homescreen and it goes on forever can someone help me plz.
droidgeek 18 said:
My s3 mini is freaking out I don't know if it is a virus, but my home button freaks out. Without me touching it, it will bring up the recent apps menu and close out my apps and return to the homescreen and it goes on forever can someone help me plz.
Click to expand...
Click to collapse
I'm pretty sure it's not a virus (are there even mobile viruses?) so you should be 50% calmed down now. As for the problem, I've got no idea what's happening, but you should flash a completely stock ROM (without wiping nothing at first) and see if the problem persists. If it does, try factory reseting the newly installed stock ROM and then everything should be OK (however make a backup of all your important data as you'll lose it).
koragg97 said:
I'm pretty sure it's not a virus (are there even mobile viruses?) so you should be 50% calmed down now. As for the problem, I've got no idea what's happening, but you should flash a completely stock ROM (without wiping nothing at first) and see if the problem persists. If it does, try factory reseting the newly installed stock ROM and then everything should be OK (however make a backup of all your important data as you'll lose it).
Click to expand...
Click to collapse
if you tried above and didnt worked. its probably a hardware problem

[Q] Random soft-reboots (Stock 1.205, root)

Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
niedzwiedz102 said:
Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
Click to expand...
Click to collapse
Try with hard reset or try to flash another stock ftf
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
niedzwiedz102 said:
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
Click to expand...
Click to collapse
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Crash...X said:
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Click to expand...
Click to collapse
Well, I'll give it a go, however I did it before and the reboots occurred anyway... I'm now slowly uninstalling all the apps one by one to see when this craziness stops
I'm starting to suspect that it's a fault of Google Play Services, they're always on high positions in my Wakelock and Battery Usage lists, I heard people are also having some other problem with this app.
Edit:
Another thing is that I try to modify something in AppOps (I'm accessing it via some shortcut apps from the Store), but I cannot change permanently any settings (I click back, then enter again some app and it's all 'allowed' again), is this normal?
I'm digging up an old thread, but I narrowed down my problem to Stamina Mode, I think.
I wiped all data via factory reset, reinstalled clean system via PCCompanion and only townel-rooted. The soft-resets began to appear again shortly after first boot. I tried to eliminate differet things and it seems that the reboots occur only when Stamina Mode is on. I've switched it off like a week ago and the phone has been running smooth ever since.
Now I'm just asking out of pure curiosity, has anyone ever stumbled upon similar problem? Is Stamina Mode known for causing any issues of this kind?

[Q]Suddenly shutdowns on MI3 Need help

I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Maybe there's a problem on your phone's battery. Try to bring it on a service center.
error01671 said:
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Click to expand...
Click to collapse
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
paul c said:
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
Click to expand...
Click to collapse
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
error01671 said:
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
Click to expand...
Click to collapse
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
paul c said:
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
Click to expand...
Click to collapse
OK, I got some conclusions, and it might be a hardware problem.
First, I replaced the battery with same ROM, it still got SOD.
Then I flash Omni, PAC, Euphoria-OS, all got SOD like before.
So I return to MIUI, no SOD, but I got random reboots and sometimes Wi-Fi will disconnect itself even in its range.
Now I'm using Ivan's AOSP, still got random reboots and Wi-Fi problem.
And now I need this phone to work because I don't have a backup, waiting for new Nexus!!

Categories

Resources