Morning all,
I have a bit of an unusual issue at the moment. I currently have my Z3c rooted, with unlocked bootloader and running the latest .77 firmware. I also have the read/write permissions fixed through the recovery flash method. . I'm busy trying to uninstall apps via rom toolbox and it just resets the phone when I try to do this. They arent even system apps, just apps I may have installed earlier that I now want removed. Not sure what the issue is here because I've uninstalled rom toolbox and tried again but with no success. It will freeze them fine but it wont uninstall them without causing a phone reboot.
Anyone else come across this issue at all and if so, is there a way to sort this out.? Any other information you may need to help out with this issue, I will be glad to provide.
Thanks very much.
Related
yesterday, I pluged in my charger and started browsing.
at one moment phone freezed, purple led flashed and phone rebooted
after that a lot of apps I had installed are missing. among them are gmail, google search widget, play store, titanium backup, some office from market (can't remember which) ...
and one widget I use can't be loaded on startup but if I remove it and add again it works.
I tried all I can think off except factory reset.
I tried deleting cache, dalvik cache, switched app2sd off (which were on, although I remember leaving it off), fixed permissions from recovery ...
I even reinstalled kernel and ROM and gapps, but no change at all which is really strange.
I use MiniCM7-2.2.0 ROM and 2.6.29.6-nAa-11 kernel
SD card is working, I can browse files and swap is working.
It also seems that rebooting doesn't work well. Sometimes, I choose reboot but it doesn't boot up until I pull out battery and press power button.
I'm not sure if this is connected because I didn't reboot much phone with this kernel and ROM
Any ideas before I wipe data?
Overclocked ?
Sent from my E15i using XDA
Apps2sd that's why ur apps r gone. Full wipe and reflash rom. Reboot issue can be fixed with latest flashtool reflash kernel with that. Worked for me no reboot problems no more
Hit thanx if I helped
Sent from my E15i using XDA
thank you for fast replies
phone is not overclocked.
I also guess it has something to do with app2SD
but I do not use it.
when I installed ROM I wanted to use Link2SD but it couldn't work because of build in App2SD.
I tried that App2SD but I couldn't control which apps to move, I even didn't exactly understood how it works, so I gave up of it.
Everything worked until yesterday.
and I only browsed internet when this happened. what could go wrong?
Is there a way to fix this before I wipe the whole thing?
I would like to make some backups and for that I need missing apps.
thank you
Oh,
and the strangest thing to me is that even after I reflash gapps, I don't have any google apps (at least which I use) except google talk
Try this:
Root again your phone with SuperOneClick.
Go to Settings >CM Settings >Performance >a2sd, and deactivate it. Then, activate it again.
Reboot.
Hopefully... it will fix your problem (worked for me ).
any particular version of superoneclick I should use? I tried one I have (which I used to root my phone a long time ago) and it fails to root it.
but why do you think I should root again? This is custom room and it is already rooted.
I tried turning on and off app2sd but there's no change, except some files are in one case in sd-ext directory and in other arent. but that are not missing apps :-(
Use the newest version, it will work. If not... use any method to root your phone again and follow the above guide (YES, I know that your ROM is rooted, just do it).
Why you should root again? Well, I already had that problem and all root apps were having problems (I dunno if you are having problems too, try it), so I rooted again my phone and all the problems were solved.
I repeated this with superoneclick 2.3.3 but no difference.
I had to full wipe the phone.
thanks all for suggestions.
EDIT: just to be clear, it did root this time, but no difference about this apps.
Hi everyone,
I've owned a HTC One since 3 months now, and I started trying to customize it a little. So, I followed the different guides I found on this site, and successfully managed to unlock my bootloader, install TWRP and finally flash a custom rom.
I flashed the Android Revolution HD v12.1 , and everything worked fine. Then, I made a backup with Titanium Backup Pro, no problem again. So I decided to push a little further by installing the CM 10.1 nightly version for the One; indeed, that's a nightly, for sure. I then got back to my previous custom rom and used my TB's backup to restore my datas.
I did not notice the problem immediately, but it was obviously present from the beginning : it appears that I'm not receiving anymore any notifications coming from any app I installed from the Store. I tried to uninstall then install the apps again, did not work. I looked a little bit in TB's option and I found one called "Manage Android ID", TB told me my One had a different Android ID from the previous one; I tried to restore the previous one, but still, I don't receive any notification from my apps !
I have no problem with message, call, missed call... notifications.
So, how can I fix this quite annoying problem ?
Thanks a lot.
A little bump, I need you guys!
try formatting your phone and installing an app, then check for notifications.
Ideally before changing from ARHD to CM, you should format the phone. Also titanium backup tends to have issues when you restore across different implementations.
Currently, I have ARHD. I just tried CM but TB tends to bug the entire system while restoring, anyway that's not the problem.
Of course, even though I didn't mention it, I made a FULL Wipe with TWRP each time I installed a new ROM.
I think -obviously I'd say- that the problem is caused by TB, but I'd like to know if there is any possibility to fix it without wiping the phone and installing ARHD, without using TB; Doing it this way would solve the problem I guess, but if I could avoid to lose quite a lot of data, I'd be glad !
Thanks for trying to help me.
Hello guys,
Yesterday I OTA-updated my xperia sp. Before the updating I made sure Voodoo Rootkeeper was installed and had a backup. After the updating root was still present, so I didn't have to use it. But, I tried to restore my old build.prop from .211 but after that phone crashed and rebooted. Same when installing xposed framework and trying to enable it. Also it won't let ES File-explorer mount /system R/W and won't let me uninstall the SuperSU app (crashed and reboots). Can anyone help me with this?
Kinda looks like I have to reroot my phone, but it's running fine (except for what I mentioned) and even offline charging works.
I'm pretty sure root access in this phone is not meant to be kept across versions. Besides, .2.254 uses a different way to root the phone compared to .211.
Catching my breath, letting it go, turning my cheek for the sake of the show
Solved
I already solved it, RIC wasn´t stopped at boot anymore. Thanks anyway
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Sorry I don't have a solution but I just wanted to bump this thread because I'm having the same issues as you. Wakelock detector also gets stuck on loading screen and supersu fails to open.
vahx129 said:
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I also had the same issue. I am using the image with busy box and Xposed framework installed. After a an hour or so super user said that the binary was not installed, and most of my root apps stopped working. Root checker said my Turbo was not rooted, though gravity box and a few other Xposed modules continued to work. I rebooted the phone, but had the same problem. I turned notifications for the supersu app back on, and after about a minute it said the binary had to be updated, and I had root again. I'm not sure what is going on, but I will come back if I find anything
I'm not having any issues. I would reboot the phone into recovery and wipe the cache there. Hope that helps.
Glad I saw this thread...I'm having the exact same issue!
A hard reboot will solve the problem every time...but its quite annoying...
I'm going to try a factory reset and see if that helps
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Seems to have resolved itself
I just wanted to mention that between clearing the cache and flashing a different rooted image this issue appears to have resolved itself.
I will update after some time to see if this fix maintains or if anything else pops up. Thanks for the suggestions!
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
What cache did you clear? I tried to clear the cache from the recovery, but my phone freezes and I have to reboot. Then I loose root a while later.
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
I cleared cache in recovery...didn't help...gonna have to try a factory reset
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk