Hey guys.
Had some trouble on my Z2 and thought I'd create an account here and ask for your advice before I did something stupid. Have no experience with rooting or modding whatsoever, so bear with me please.
I bought a Z2 whose screen never slept. I found out that the responsible was com.sonyericsson.startupflagservice v2, who would always run when I turned the phone on and remained on my notification area with no text, just an icon resembling two blue screens superposed. If I force stopped the process, the phone would sleep normally until I powered it off. When I turned it on, the process would be there again preventing sleep.
I did some research and learned how to flash a different ROM, wipe cache, wipe dalvik... Did all that and the process would still be there. Rooted my phone, bought Titanium Backup and froze the process... it worked fine, but would I reset to factory settings, there was the process again.
And finally I come to my question: would un-installing the process and wiping its data with Titanium backup work? Would I be at risk of bricking my phone?
I'm running out of options on what to do and returning isn't really an option!
Thank you very much!
Phone: Xperia Z2 D6503
Android v: 4.4.2
Build number: 17.1.2.A.0.314
Please let me know if there is any other info I can provide you with in order to find a solution. Thanks again!
busseto said:
Hey guys.
Had some trouble on my Z2 and thought I'd create an account here and ask for your advice before I did something stupid. Have no experience with rooting or modding whatsoever, so bear with me please.
I bought a Z2 whose screen never slept. I found out that the responsible was com.sonyericsson.startupflagservice v2, who would always run when I turned the phone on and remained on my notification area with no text, just an icon resembling two blue screens superposed. If I force stopped the process, the phone would sleep normally until I powered it off. When I turned it on, the process would be there again preventing sleep.
I did some research and learned how to flash a different ROM, wipe cache, wipe dalvik... Did all that and the process would still be there. Rooted my phone, bought Titanium Backup and froze the process... it worked fine, but would I reset to factory settings, there was the process again.
And finally I come to my question: would un-installing the process and wiping its data with Titanium backup work? Would I be at risk of bricking my phone?
I'm running out of options on what to do and returning isn't really an option!
Thank you very much!
Phone: Xperia Z2 D6503
Android v: 4.4.2
Build number: 17.1.2.A.0.314
Please let me know if there is any other info I can provide you with in order to find a solution. Thanks again!
Click to expand...
Click to collapse
Interesting questions... I've also experienced this.
After about 30 mn of waiting, startupflagservice had finished its job (I don't know what it is doing).
Anyway, I don't recommend to uninstall it.
See if flashing the .402 FTF solves this? Maybe it is a random bug in the .314 firmware. I haven't got this process running so I can't comment on it. Have you got power saving features enabled? If so, is the battery drain still bad with the process running?
I know I am asking a lot of questions but there are multiple things that could be causing the issue. When you factory reset the stock ROM, does it occur after you have installed apps or before? There could be a rogue app keeping the phone awake. Install either:
Betterbatterystats (https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats)
Wakelock detector (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector)
Hopefully either app should give you a better insight as to what is keeping your phone from deep sleep.
EDIT: Also, according to quite a few lists, that particular thing (com.sonyericsson.startupflagservice v2) is safe to delete. If you are rooted and have a custom recovery, make a nandroid backup (ask if you don't know what it is or how to do so) and then go ahead and delete it using ES file explorer. Worst case scenario your phone reboots/gets stuck in a bootloop or something and you can just restore the nandroid.
Thanks for the replies, guys!
I'll try flashing the .402 FTF next weekend. Unfortunately, I don't have much time to tinker with the phone on weekdays anymore. I have reasons to believe the current firmware is not the responsible though, as this problem occurred on the firmware that came on the phone (don't remember which one it was), and continued after I updated to .314 through the PC Companion.
Answering your questions, Devzz:
I have no power saving features enabled.
I haven't noticed any battery drain, as I didn't allow it to happen... I usually turned the screen off with the power button, which worked... the only problem was the phone not sleeping by itself after the inactivity period I set.
The problem occurs right after I turn the phone on. As soon as I turn it on after a reset and every time thereafter, I'm greeted by a black screen with a big black button that reads: POWER OFF. If I click it, nothing happens. When I press Back or Home, I'm on my home screen with the icon I mentioned on my original post on the notification bar.
I'm starting to think I just had bad luck and got a defective piece of hardware. There's another problem now that didn't happen before the update: the volume of the notifications now is always low, regardless of how much I set on the slider on Settings > Sound > Volumes. I've noticed some people had this problem as well, and I could temporarily fix it by enabling Dynamic normalizer and xLoud on the Sound Effects, although that is hardly an ideal solution.
Thanks very much again for your help! I'll look into the nandroid backup and try that next weekend.
P.s.: another piece of information that I haven't mentioned and may be relevant: I was never able to access recovery mode, despite my efforts to do so. I had to install XZDualRecovery to be able to boot into recovery mode.
busseto said:
Thanks for the replies, guys!
I'll try flashing the .402 FTF next weekend. Unfortunately, I don't have much time to tinker with the phone on weekdays anymore. I have reasons to believe the current firmware is not the responsible though, as this problem occurred on the firmware that came on the phone (don't remember which one it was), and continued after I updated to .314 through the PC Companion.
Answering your questions, Devzz:
I have no power saving features enabled.
I haven't noticed any battery drain, as I didn't allow it to happen... I usually turned the screen off with the power button, which worked... the only problem was the phone not sleeping by itself after the inactivity period I set.
The problem occurs right after I turn the phone on. As soon as I turn it on after a reset and every time thereafter, I'm greeted by a black screen with a big black button that reads: POWER OFF. If I click it, nothing happens. When I press Back or Home, I'm on my home screen with the icon I mentioned on my original post on the notification bar.
I'm starting to think I just had bad luck and got a defective piece of hardware. There's another problem now that didn't happen before the update: the volume of the notifications now is always low, regardless of how much I set on the slider on Settings > Sound > Volumes. I've noticed some people had this problem as well, and I could temporarily fix it by enabling Dynamic normalizer and xLoud on the Sound Effects, although that is hardly an ideal solution.
Thanks very much again for your help! I'll look into the nandroid backup and try that next weekend.
P.s.: another piece of information that I haven't mentioned and may be relevant: I was never able to access recovery mode, despite my efforts to do so. I had to install XZDualRecovery to be able to boot into recovery mode.
Click to expand...
Click to collapse
I have the exact same problems with my phone not going to sleep and the big "power off" button. What the heck does it mean? Anyone fix this problem yet?
matase said:
I have the exact same problems with my phone not going to sleep and the big "power off" button. What the heck does it mean? Anyone fix this problem yet?
Click to expand...
Click to collapse
In spite of my efforts, I couldn't find a way to get rid of the problem. Currently I have the phone rooted, installed Titanium Backup and deleted the files related to the process.
It's working, although if I ever revert to factory settings, the problem will be there again.
Best of luck to you and please let me know if you find a fix.
busseto said:
In spite of my efforts, I couldn't find a way to get rid of the problem. Currently I have the phone rooted, installed Titanium Backup and deleted the files related to the process.
It's working, although if I ever revert to factory settings, the problem will be there again.
Best of luck to you and please let me know if you find a fix.
Click to expand...
Click to collapse
Which process/es did you exactly delete? What are those files for the process are even doing? When did this problem start for you? Thanks
On mine that service displayed a persistent notification and on every reboot it prompted to power off or use phone. Anyway, as soon as I saw that I rooted and froze com.sonyericsson.startupflagservice in titanium backup. Problem solved! As far as I've tried it's not essential and can be uninstalled as well. I really don't get how they overlooked this, it's a huge annoyance for anyone that can't root the phone I imagine.
Solution!!!!!
I had the same issue on a Z2 I bought off a guy. It was on 4.4.2 and it kept saying no update available. I downloaded and flashed the 5.0.2 update via Sony Flashtool. At first boot the issue appear again after a few seconds. It got very intense with the screen becoming unusable. The phone shut itself down and rebooted without the issue. Gone and nowhere to be found. I immediately got another prompt to update to a newer Android version - same 5.0.2 (17MB file).
So flash away, guys!!!
Related
Does anyone know what this is, Or why it happens. my phone would crash and this screen would pop up. I did alot on my phone before it started to happen. I think it has something to do with GPS, but the only other people I have seen on the net to have this problem have different stories.
One says its after he rooted
Another person on the T-mobile forums reported it but didn't give a suspected reason.
Mine did it after three things happened I used the supl.google.com gps fix, and my battery showed an overheat warning when charging turned off. And My girl tried to send 15 pics she took to herself and cousin one through E-mail and the other through mms. The email and text messages to my girl gave me error messages that and a way to solve the problem (which didn't work) The only thing that worked was deleted her thread and the email.
I have since restored factory setting to see if it fixes the problems. I'll keep everyone updated.
If anyone has any ideas or has had this happen chime in maybe we can find out whats going on.
Factory Data reset was useless, it was a waste of time. It appears to be related to the GPS. After thinking about it, the radio probably burned out when i was trying to use gps while charging it in the car yesterday, it had to be 94 degrees outside probably hotter on the dash. The phone actually reset to the battery indicator and flashed a battery heat warning. Gps didn't last last long after that. It was the next morning when I started to get the error.
Called rep, and he gave me an exchange right away, no questions, will be getting another phone sat. or monday.
I realize this is a little old, but I just wanted to say that I just had the same problem today while I was using a navigation tool (Waze). I thought it might be related to the app, but maybe it is the GPS as op said.
I do realize this thread is months old but, likewise, I just had the same thing happen to me.
I wasn't using GPS though, I was simply trying to tether through usb.
Next thing I know the "kernel panic, upload mode" screen came up rendering my phone useless
I pulled the battery restarted, and did the same thing yet this time the screen didn't come up allowing me to tether and search the issue.
From the google search results I came across a thread where a guy said it had something to do with task managers/killers. He said since he unistalled the version he was using "advanced task manager" he never had the problem again.
which led him to believe it came from the wrong proccesses being killed or stopped by it which caused the kernel to crash.
Likewise...I too was using a task killer--Auto killer. So I uninstalled it as well, and now use the system default task manager to kill unwanted apps manually.
So far so good...Idk if this is the solution, but to any future readers that run across this and are having the same problem, I suggest you rid of any task killing apps that may be running. Manually kill apps on your own, and let android handle the rest.
I'm not saying dont use them at all but...unless you are an advanced enough user to understand how they work a little more, your best benefit is to leave it be.
Here are some tips that helped me fix this issue:
1. As someone said earlier, uninstall task killers. It's better to install an app that changes the os default task killer. I use autokiller and I use the preset optimum. This way the os can manage the processes and it will stay stable.
2. If you have setcpu, make sure to go to menu, autodetect device, and then set the minimum to 200.
3. If you flash a rom, if it's possible use a clockwork recovery image instead of using Odin.
After these steps, it never happened to me again.
crazy25000 said:
Here are some tips that helped me fix this issue:
1. As someone said earlier, uninstall task killers. It's better to install an app that changes the os default task killer. I use autokiller and I use the preset optimum. This way the os can manage the processes and it will stay stable.
2. If you have setcpu, make sure to go to menu, autodetect device, and then set the minimum to 200.
3. If you flash a rom, if it's possible use a clockwork recovery image instead of using Odin.
After these steps, it never happened to me again.
Click to expand...
Click to collapse
I was using Autokiller too....I uninstalled it and everything seems fine, Idk, may had nothing to do with it...because I've used Autokiller for quite a while, way back on my G1 and never had that problem, oh well...appreciate your input.
I had several "kernel panic" warnings on my handset which I replaced. If I remember it was after using Google maps right after an update and it was hot as a ***** and could smell components melting. As far as autokiller the experience I had was that say I was online Google reader decided to check XDA for instance,go back to Steel would have closed the App out.this happened using visual task swithcher and the default last used programs panel. So I don't use it for that reason.
if your phone is Loki, use Odin, you'll be Thor.
Thread moved to Q&A.
I think this is related to some applications. This is happening to me also, I am on Stock 2.2 Rooted. First I noticed this one when I was online on Nimbuzz and my yahoo account was logged in through nimbuzz, and when I started Yahoo messenger with the same login ID I got "USER FAULT NOT KERNEL PANIC". It happened with same scenario again & again. So I dont use both together.
Again I noticed when I kept my phone on charging through USB connected to a PC, sometimes my fon went in the same Panic mode without doing anthing.
Somebody needs to find out why this is happening. some application or process is causing this problem which needs to be find out.
Vibrant Crash Response
I have the same problem! It's happened about 20 times to my phone. It crashes, gets hot as ****, and gives me the 'user fault kernel panic upload mode' screen.
I think I've narrowed it down a little though.
Things I've noticed:
1.. It only happens when the phone is charging, never on battery.
2.. It only happens after the screen is turned off, never while I'm using it (anywhere from 5 min to hours after the screen has been off).
I'm guessing its some kind of background process that uses a lot of processing power and overheats the phone..
Hope this helps. Be sure to post up if you find a solution.. I don't want to burn it up!
Just for confirmation sake are we all seeing the same Kernel Fault error? are you seeing the same codes?
RST_STAT 0X4
PMIC_IRQ1 0x0
PMIC_IRQ2 0x0
PMIC_IRQ3 0x0
PMIC_IRQ4 0x0
PMIC_STATUS1 0x0
PMIC_STATUS2 0x0
Also i have tried three different Kernels so i am pretty sure this is going to be a hardware issue.
I may be wrong though, in my case it could be a task killer.
Need help! What can we do?
My cousin had the same problem but, It did happenned on battery power, he did not activated the GPS or Google Map.
The phone is practically bricked. It does not boot to android. We tried everything and came up with no results. Even we get the battery off and waited like a minute or so, plug it back and try to turn it on and it just got us to the same screen with the message saying something about kernel panic upload mode and a bunch of red numbers at the upper left corner. He does not installed any task killer either.
I think he was trying to install a .zip file from the SD Card in clockwork recovery mode. Now we can't even get to recovery mode!
What can we do?
hardware problem
I have been running on I997UCKI4 rom. Now a days the phone suddenly keeps getting into "user fault kernel panic upload mode" and phone would not even go into 3e recovery mode.
I have to take out the battery and put it back again. It keeps heating up until I do that.
Please help.
My original vibrant had this error...
turns out was bad hardware, replaced phone and havent had the problem since.[lots of other problems but not this one]
good luck
i have some issue too
anyone can resolve it?
i get this when i reload new ROM for my galaxy tab..
always shown "KERNEL PANIC RELOAD MDOE"
please help
Same problem
Mine too. What should I do?
I was flashing to stock firmware. Then this error appeared. and i couldn't restore because it doesn't even boot.
PLease help asap. It was my birthday gift.
its nothing to do with GPS.
Jnt
My samsung infuse 4g keeps turning itself off. If I take the battery out then put it back, the phone starts working eventually shuts down again.and gives message user fault not kernal panic upload mode And phone going heat also. Plz tell solution
do anyone find any solution please?
Ok, so I have a rooted Vibrant on stock firmware and I've been having a problem with my screen becoming unresponsive. It originally happened on a smaller level when the phone was newer and unrooted, however the problem has gotten much worse. I've done a factory reset of the phone along with a nandroid backup of it before the problem was severe, yet it comes back just as strong.
I already went through the problems with the no wake from setcpu, even thought it was my lock screen becoming unresponsive until I disabled it with NoLock. Also, I have the Logcat live wallpaper, and usually when you tap the screen, you can see the system processing the information, however when the problem occurs there is no response on the logcat live wallpaper. The phone doesn't freeze at all though. All the soft keys still work perfect as do the volume and power buttons.
Any ideas, tips, suggestions that might help me narrow down this problem? Could it be from a bad version of busybox? Autokiller maybe? I have it set to strict(was previously on aggressive) but no change. Maybe Autostarts is causing something to freeze up. Thanks for any help. Seams like these phones have alot of wake up issues.
I would reflash back to stock with Odin and see what happens when you don't have task killer, set CPU, etc. Also, be careful with autostarts
So I removed Autostarts and rebooted, same deal. I did a factory reset and still the same. I just unrooted a few minutes ago and the problem seams to have gone away. I'm gonna leave it like this for a bit without installing any apps and see what happens. Is it possoble I have a bad root.zip file or bad version of busybox? Doesn't make sense to happen when I have root, then go away when I don't. Any reason it could cause this? I'm really close to sending the phone back, but don't want to waste my time if it's just a bad root file or user error.
Well I don't know for a fact, hopefully someone more knowledgeable can chime in. Maybe when you are unrooted, changes made by autostarts no longer have the permissions to affect anything. Personally I would use Odin (have done it twice already) and start from scratch. But then you risk accidentally screwing up the phone if something goes wrong.
I removed Autostarts and rebooted just to make sure the changes took effect though. Even did a factory reset. Those removed all apps that required root access and the problem was still so bad it took me an hour to get the screen responsive again. Once I did get into my phone I booted into recover and unrooted. Restared the phone and now the issue seams to have gone away. Touch screen is very responsive now which leads me to believe it was something that had to do with the root file i'm flashing, or possibly busybox. Very very strange.
Hopefully someone much smarter than me could give some insight as to what could potentially cause the touch screens to just stop recieving signal. It's just bizarre that the phone continues to run fine, just not the screen.
Hi guys. I'm totally new to the android/smart phone world btw. Anyways, I recently got my Samsung Galaxy S2... first thing I noticed, my touch screen wasn't working. I popped the battery in and out and then it started working as it should.
My phone was working fine this morning, then all of a sudden out of no where, the touch screen stopped working again. I've tried turning on/off the phone multiple times. I've taken out the battery and even my SIM card nothing... i'm worried.
Has this happened to anyone else? Is there a fix? Do i have to go through Samsung? I hope not. Incase anyone asks, I did not root my phone.
Any help/feedback would be appreciated.
When the touchscreen stops working... were you charging the phone at that time?
The first time i turned on my phone, was actually by accident and it was charging.
However, just earlier now, it was not. it was just sitting on my computer desk. The home button, lock button and touch capacitive buttons work.... but i can't get past the lock screen
you could try a factory reset to see if its software related, but it sounds like hardware. I would definitely Return the phone .
I guess I can't do a factory reset, since I can't get into any of the menus... man this sucks. I spent $900 *gulp*
To do a factory reset,
1. Turn the POWER OFF, pull the battery out and put it back again.
2. Simultaneously press and hold the Volume Up, Home and Power button
3. If the Samsung Symbol appears, release the Power button
4. A Boot Menu will then show, Use the volume up/down to choose wipe data/factory reset.
touch screen not needed this way.
oo that's interesting... I tried it. and it didn't get to a boot menu. maybe I was doing it wrong. I tried a few different ways, but no success. It turns out I have warranty with the store. They're going to replace it for me Thanks for the feedback guys. Awesome forums.
Something similar happened to me yesterday. When I had the in-box USB cable attached to a BoxWave VersaCharger (combined AC/DC charger), and the VersaCharger was plugged into 120V AC, the touchscreen would stop working. As soon as I unplugged the USB cable from the SGS2, or plugged the VersaCharger into a 12V DC lighter socket, the touchscreen would work fine.
I've got the same problem as the OP... I had my phone charging overnight and this morning when I first went to use the phone I could not unlock the screen. I could wake the screen via the home button, and see I had a missed call etc but it just wasn't responding to touch. BTW I can't remember if when I first tried to unlock the phone if it was charging or not but really this shouldn't matter.... oh and btw, I'm not rooted or anything either! Naturally I rebooted the phone but still the same problem....so I tried a battery pull and still the same problem. Just now I did a factory reset but the touch screen still isn't working! I guess this is a hardware problem so I'm going to get it fixed under warranty by Samsung! Gutted that I will likely be without my phone for a week or 2!
EDIT, UPDATE...
Well, I was just on my way to the repair shop Samsung warranty had told me to take it too, and I took my sim card out to put in my old Hero (the only thing I hadn't tried!) and I couldn't believe it but the touch screen started working fine again! Weird, but that is now my advice if anyone else has a problem with their touch screen not working - oh and I took the sim out whilst the phone was still turned on. Crisis averted!
UPDATE 2
Sadly this has happened about 4 times to me now and I'm just waiting for the inevitable next time. Each time doing a factory reset then taking the sim card out seems to bring the screen back to life (though last time not immediately) but I shouldn't have to put up with this. Problem is, I don't want to send off a seemingly perfectly working phone to get repaired as I fear they will struggle to notice the problem, never mind fix it! I'm hoping a new firmware comes out soon, in the hope that it may resolve my issues...
Me as well ...
I have had this happen to me twice now (Touchscreen not responding).
The first time I had just installed a game and thought it must have been related to that. Pulled the battery and no joy, left it for a while and it came back to life...
Second time I was surfing the web and it stopped responding, pulled the battery and left it for maybe a minute but no joy .... pulled the battery again and left it for probably 20min and it came back to life. When it came back up I noticed the livewallpaper had been turned off and my widgets were gone from the homescreen.
What I did notice when it wasn't working was it had "safe mode" displayed at the bottom left of the screen
Have the Same Problem
Have the same problem i Mine and was super exicedat first it worked fine and after charging the touchscreen stopped working i pulled the battery out and put it back in but no luckso im gonna return mine to the shop hope they replace it
Moral:AT FIRST SUPER EXICTED BUT NOW SUPER ANGRY
Same issue - Is there ANY way to save my data before I send it in for repair/replace?
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
blaubeer said:
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
Click to expand...
Click to collapse
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Nitrile said:
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Click to expand...
Click to collapse
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
blaubeer said:
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
Click to expand...
Click to collapse
get a USB jig off ebay or amazon to reset the flash counter. should not cost more than 5 or 6 euros, shipped.
anyways you need to flash CF-root through ODIN if you are coming from stock. instructions are all in chainfire's cf-root thread.
Nandroid Restore
So I successfully rooted, used CWM to do a Nandroid backup, mounted the sd_card and saved the contents (including the nandroid backup) to my PC, reflashed the stock rom & kernel, usb-jigged it to get the counter back to zero/original and sent the phone in for repair. My efforts paid off as they repaired it without question under warranty. I just received the phone back and today set about restoring my backup:
Copied the sd_card contents I'd saved to my HDD back onto the phone
Re-roooted it with Cf-mod.
Used CWM to restore the backup I took before sending it in
It restored boot/system/data/cache successfully
selected reboot now in CWM
The result is that it is still missing all my apps. It only seems to have the "data" like my camera shots and SMS messages, system settings like whether bluetooth is on or off, the volume level, Wifi networks etc. So something was restored. But there is no Google Account configured, the lock screen picture is the default not the one I had beforehand, and as I said, all the apps - the main reason I did this whole thing as my personal data is all backed up to the cloud on a regular basis anyway - have not been restored. Am I confused? I thought a nandroid backup took a complete snapshot of everything, apps included.
Finding out the list of Apps I had in order to reinstall them is not an issue - I have a list of everything I had installed saved on AppBrain. But if I reinstall the apps, all the settings (or progress in the games) within those freshly installed apps will be back to square one, not where I left them, right? Or should I reinstall the apps and then restore the data partition over the top again?
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
achillies400 said:
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
Click to expand...
Click to collapse
Nope, no screen protector or any kind of case for that matter. Anyway, that isn't my issue anymore. The touch-sensitive unit was defective, the phone was repaired under warranty. My issue now is getting my apps & settings back. I have meanwhile read elsewhere that Nandroid doesn't back up the apps - pretty deceptive "backs up everything!" "it is like time travel" etc comments around here then.
Anyway, I reinstalled all the apps I had previously, and thought by reapplying the data partition from the nandroid backup it might then bring back the settings for the reinstalled apps. Instead all it did was remove all those apps again - now I am really confused. How come the restore DOESN'T bring back the apps I used to have, but DOES remove the ones I subsequently install. Does Nandroid touch the apps or doesn't it?
Touch screen not working
So i am having a very peculiar problem related to the GT-I9100 Touch Screen.
I bought the phone from Saudi Arabia and I live in Bangladesh at the moment. So for now I don't have warranty.
I bought it on 4th of this month. It had 2.3.3. So I updated it to 2.3.5. I did not use the phone much before that so I don't know if this problem was there before.
So here is the problem.
First time I noticed it when i pulled the phone from my pocket and could not unlock the pattern. First I thought I forgot the pattern. After sometime I noticed that i could not touch the buttons. I was dragging my finger over the points but there was no connecting line. I restarted the set. But it still did not work. After sometime I took the battery out. And after that it started normally and unlocked. And the touchscreen is totally fine.
I tested it using *#0*#. And every single point in the screen registers touch.
After that this happened couple of times. First couple of days I thought it was a pattern unlock problem. But i tried PIN and Password even using no unlock. It happened in every case.
So after couple of days it totally stopped happening.
But from yesterday it is happening again. And today it happened 3 times.
So today as I had no unlock protocol i tried tapping Home twice. As this brings on the voice command menu. And for the first time i was in the phone without touching the screen.And first i noticed the Menu and Back Soft keys works.And the touchscreen still does not work. And i noticed some thing weird. Always some thing in the screen is Selected. In Menu the + Icon is selected. In first screen the Map icon is selected. Also in Recent Apps the first App is selected. So after a lot of reboots it is back to normal again. Now i see something interesting. In the Battery Usage Graph i can see some really sharp drops. 3 times. Looks like when this happens phones charge takes a nose dive.
So here is the Gist.
Info related the Problem:
1. Usually happens when the phone is my pant pocket for sometime. It does not happen if it is sitting on the table.
2. Touchscreen gets totally disabled.
3. I have no idea why this happens.The exact reason behind it.
4. Battery Charge takes a nose dive when this happens. See the attached images.
5. I still don't know how to bring it back. Sometimes a simple reboot works. Sometimes I have to pull the battery. And sometimes it works on its own.
6. Every other function of the phone works. Like music playback using my UE 200vi music keys using PowerAMP, Siri(Android version), Call can be received using headset.
Battery nose Dive:
dl.dropbox.com/u/30943431/SC20111115-203017.png
dl.dropbox.com/u/30943431/SC20111116-202913.png
Also the selection
dl.dropbox.com/u/30943431/SC20111116-202146.png
So this is the thing. My biggest problem right now is, I don't know why it happens and I don't know how to bring it back from this situation. If I knew I could make sure I don't get it again or I would just fix it every-time. As when this happens I cant make calls or anything which requires the touchscreen.
So guys help me if you can by giving ideas. As i will not go back to KSA in 6 months. So buying a $550 phone unlocked was a total waste. As i cant use it here.
Thanks a million in advance.
---------- Post added at 09:29 PM ---------- Previous post was at 09:13 PM ----------
Sorry for this. But looks like i cant post outside links before i have 8 posts. So i removed the "ht tp : //" part of the links. Copy paste in browser address bar and it will open fine.
And also the next time it happens i will do a video to shou you guys.
Having the same problem while charging touch screen doesn't work
Stock charger and usb cable
i was on CM7 but that happend so i flashed stock but no luck
I will write more observations
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
OK, this is really weird - after getting the 4.2.2 update, my phone reboots itself every night, not 100% sure it's exactly the same time, but it's been while sitting in my pocket or on the table, not even in use. At first I assumed it was Zooper, which I had installed right after the update, but I disabled it yesterday and got the reboot again tonight.
I even checked my Tasker to make sure some auto-reboot profile hadn't installed itself!
Any hints about how to diagnose this? Do I have no choice but to remove apps one by one? Most of the apps I run are the same ones I run on my TF300 tablet which also has 4.2.2, so don't know if it could be an app.
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
PhysicalEd said:
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
Click to expand...
Click to collapse
the Factory reset will erase all ur Apps and will stay in 4.2.2 ......
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
PhysicalEd said:
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
Click to expand...
Click to collapse
The update may have screwed up somewhere in the middle, you could try to re-ruu your phone or unlock the bootloader and flash a custom rom, also the thing about the power button not putting the phone to sleep or doing anything than reboot on long press happened to me on each and every custom rom and I never did any OTA, got my phone, unlocked bootloader and flash away from sense, my hboot is still the one that it came with, but for me that thing happens really randomly, like once every 1 or 2 weeks, and when that happens for me the volume buttons stop working also till reboot, I was thinking I was the only one facing it so I kinda decided not to talk about that as I saw no one say anything about it, but I am also one of those for who the phone turns off exactly when my phone goes to 6% battery whatever I do, on whatever rom I am and even in the recovery, so I was thinking that maybe vodafone modified something on it, that's an other reason I didn't say anything about the buttons becoming unresponsive...
So what I would recommend is to re-ruu your phone or go to a custom rom (or if none solves anything the phone may have some kind of hard brick).
Just to help out anyone else who ever has this problem.
It was not location services.
I can see clearly in two logs an HTC process crashing. This seems to cause a cascade that leads to reboot.
I contacted HTC tech support, they suggested I boot up in a recovery mode and try to wipe data cache. They were surprised to find that attempting to do that caused a reboot.
So as Ranomez suggests above, they want me to re-do the update with the RUU when they release it, which they said would be "soon" last weekend.
On the other hand, my battery life after this update is fantastic, so I've decided I can live with this to not have to worry about recharging by mid-afternoon!