Okey, my problem is this.
I have installed the phone locator beta from their website. Like the name says it's an app to see where your phone is if it gets stolen, wipe it through sms and do some other stuff. I did not manage to finish the application setup cause I got a phone call during the process. After that I'm locked out of the phone and the phone screen keeps shutting down. It instantly shuts back down after I turn it on. It stays on for like half a sec sometimes, sometimes less. I have managed to uninstall the application through adb to no avail. I have made a backup through recovery also hoping I will be able to restore it without getting the same problem.
But it appears that if I restore the data I get the same thing happening.
Other things I have tried:
Reflashing ROM. It's the stock one from Vodafone.
Reflashing CF-Root Kernel.
Trying to figure out which process I have to kill through adb. But I'm not experienced enough with this to do it.
Trying to remove everything about the app I find out. Still did not work.
Anyone has another idea. I really had a lot of data I don't want to lose.
Thank you.
Update: Solved in post 3.
justrome0 said:
Okey, my problem is this.
I have installed the phone locator beta from their website. Like the name says it's an app to see where your phone is if it gets stolen, wipe it through sms and do some other stuff. I did not manage to finish the application setup cause I got a phone call during the process. After that I'm locked out of the phone and the phone screen keeps shutting down. It instantly shuts back down after I turn it on. It stays on for like half a sec sometimes, sometimes less. I have managed to uninstall the application through adb to no avail. I have made a backup through recovery also hoping I will be able to restore it without getting the same problem.
But it appears that if I restore the data I get the same thing happening.
Other things I have tried:
Reflashing ROM. It's the stock one from Vodafone.
Reflashing CF-Root Kernel.
Trying to figure out which process I have to kill through adb. But I'm not experienced enough with this to do it.
Trying to remove everything about the app I find out. Still did not work.
Anyone has another idea. I really had a lot of data I don't want to lose.
Thank you.
Click to expand...
Click to collapse
What I would do is enter recovery mode. From there mount usb storage and transfer everything that's important to PC. Then wipe everything, format system, format sd card and reflash a ROM through CWM. Obviously mount again usb storage to push the ROM from PC to sd card. Maybe it's a little drastic but I can't think of anything else since I'm not a pro user or anything. Well, just an idea.
Hey thomas. Thanks a lot.
I think that's a great idea. At least it's something I did not try and might work well.
I just found out that you can enter usb storage from recovery, right now it seems I can only see the /mnt/sdcard partition. I will play with it a little to see if I can mount the other partitions before mounting USB. I think the application data is in /data/data am I right?
Okey I have managed to fixed it in the most stupid way possible.
I have noticed that if I leave the screen off for like 15 seconds then I get like 2 seconds window before the screen turns off again. I have managed to go to the screen timeout settings and it seems like the application changed that to a very low value as none of the defaults value were ticked. I have ticked the 1 minute value and now the screen stays on.
I have uninstalled the app and I'm really afraid to test it again I should probably make another backup in this state
Related
I flashed over Bionix V 1.3.1 with NextGen V2 last week by wiping data/cache/etc instead of flashing back to stock first. Everything worked really well (except for TW4 that force closes everytime) but I was just a little bugged by the 1 sec lag it takes to turn on the lock screen from sleep (the lag is absent when charging). I thought I would ODIN it back to stock and try again. Strangely, the stock has this lag now too. When I try to wipe Dalvik, I got an error "E: Can't mount /dev/block/mmcblk0p2 (File exists)". Also, my phone is still SIM unlocked after ODIN. Does this mean there are some parameters from previous flashes remaining in the system? How can I REALLY get it back to stock?
with windows plug the phone into pc then right click on the internal sd on my computer then format, should get rid of anything left from previous roms, remember to back your stuff up
dont know how to do it on mac
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
donnygg said:
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
Click to expand...
Click to collapse
id leave it from the moment it first comes on before
when i was flashing between 2.2 roms i always went back to simply galaxy and that had the old start up thing but i use to leave it before going through it then reboot then go through it then reboot after
1 reboot should do it though
Tried formatting but no improvement. Tried softlocker app and was able to turn on the lock screen instantly. However, I was losing about 5% battery life every hour, so that's not quite a solution. I then tried something really simple - remove the external SD. Immediately, I could see a reduction in lag when turning on the lockscreen from sleep (<0.5s vs >1s, if you call that a lag). It seems like the external SD card is the problem but I don't know what. The card seems to be lacking the ext2 partition, thus it couldn't be mounted or formatted in CWM. From what I understand, ext2 may improve I/O performance but I may be wrong. I couldn't get it to partition in my phone. The phone seems to format it back to FAT. I'll try getting a microSD adapter and partition it outside the phone and see if it helps, just out of curiosity.
After I restarted my Cell the boot animation keeps on replaying after the slight vibrate, same thing hapens for 10 mins then the mobile starts.
Its not normal
Can anyone help?
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
hirentherock555 said:
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
Click to expand...
Click to collapse
Found a partial solution after formatting the cell twice like a fool
Last night while playing Dangerous chambers 3D or somthing my cell got hanged.
Later it wouldnt restart or anything so had to pull out the battery.
After it started it went into loop mode.
I got worried
Formatted it once.
All ok later then again after some apps it went in loop mode.
Couldnt figure out which app was causing the prob.
Then today morning after some reasearch found out that:
In CM7 settings in settings menu> Tablet tweaks> disable lock screen> Tick
This is what i used to do to use an alternate lock screen.
After removing the check all is fine untill now.
Will update if anything happens next.
I also met this problem when trying to develop a CM7 ROM myself (from HPA CM7 BETA2). My problems are:
1. After building successfully, apps inside the output /system/app folder are bigger (in size, of course) than the original HPA ROM (ADWLauncher in HPA is 731.5K, and mine after building is 1M)
2. After flashing to DV, my phone hangs at the CM7 logo. It's OK to type "sudo adb devices" to see that my device is attached, but then any command other than that will receive "error: closed"
Guys, do you know what's the problem with my build?
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
TheDigitalSlacker said:
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
Click to expand...
Click to collapse
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Hälftebyte said:
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Click to expand...
Click to collapse
Thanks,
I'll be doing that today. How can i tell whats waking it up? The wakelock detector i have been using isn't ready for 4.4 yet.
Turns out it was noon walk that was doing it
Sent from my SCH-I605 using xda app-developers app
Haha good. How'd you find out?
Sent from my SCH-I605 using Tapatalk
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
go in e3 recovery and perform factory reset
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
Go to recovery and wipe cache and wipe dalvik Cache. If still not working then do Factory Reset. If the problem is still there than flash the rom again.
Sent from my GT-I9100 using Tapatalk
As my main goal was to get my data from the phone I suprised myself a lot and I'm copying as we speak the whole /emmc/ via SDK tools.
It's gonna take a while - I assume it's copying the whole 16GB.
After that I'll try factory reset's etc. and check if I can use my phone again.
I got my hands on a Galaxy Grand 2 sm-g7105. Performed a factory reset from device and the system worked nicely enough. A particular third party app I wanted to use wouldn't load so I kept tweaking.
I rooted and set up a CWM recovery with Odin, then considered going with Resurrection Remix. I made a backup with CWM, wiped the device and set it up. It looked great but 'audioFX.apk' or something along those lines kept crashing every 30 seconds or so. It didn't cause me any problem besides the annoying crash notification, so i figured I could just remove the apk and be done with it. To my dismay, then the notification then piled up non-stop and the system become unusable.
I went and restored the backup on CWM. Then I'd get error notifications for this and that stopping working (basically the apps present on the backup that weren't on the stock rom), so I figured the backup was useless. Another mistake, I guess.
Performed another wipe, deleted the backup for space. Tried removing every piece of bloatware I could find before unrooting (I wanted to do that). Finally everything seemed to roll... except I deleted some important apk, SecDownloadManager I've come to believe, and at that point the Play Store couldn't update a thing, it got stuck on 'Downloading'.
So I did another wipe, just to find out that didn't restore the missing apks. Got my hands on a stock rom for my model (a different build than my origibal one, but to hell with it... right?). I got that working work Odin, but to my surprise that didn't seem to completely restore the apk mess, and I got a ton of crash apl notifications and even after logging on Google the play store didn't let me in to try and see if apps could update.
Finally, I found what is supposed to be the device's original rom. Odin'd it all the way. Everything seems to be where it belongs, but I cannot really check 'cause... NOW THE ****ING WI-FI WON'T TURN ON. It's not like it doesn't connect to my network, it just won't activate. I press the switch, or goes back off.
I tried rebooting, taking out the battery for some seconds, performing a factory reset from within the system, wiping from CWM, dialing *#0011# to access service mode and deactivating power-saving mode. Nothing works.
HELP, please.
I'd be happy if the WiFi just worked, but knowing why the hell a stock rom should give any headache or what I'm doing wrong for it to go so wrong might be a step towards the solution.
PS: I'm writing this as I recall, so the details might not be completely spot-on, but the broader problems were those.