Related
I cant load any module because something is wrong with my framework..pls help me.. It says latest version of framework is not active, i uninstall, install and reboot and problem still here.. Help please
caloneli said:
I cant load any module because something is wrong with my framework..pls help me.. It says latest version of framework is not active, i uninstall, install and reboot and problem still here.. Help please
Click to expand...
Click to collapse
Yes this is a problem faced by many who are not on ASOP or CM rom. Had your ROM being a STOCK/ASOP/CM this would not be the problem. Workaround: Go to setting and check disable resource hook This will solve your "Framework Not Active Issue" with this you would not able to play with UI and Status Bar, etc. But should able to work with modules which do not make cosmetic changes.
Please pardon my english.
Hope this helps.
Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
niedzwiedz102 said:
Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
Click to expand...
Click to collapse
Try with hard reset or try to flash another stock ftf
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
niedzwiedz102 said:
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
Click to expand...
Click to collapse
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Crash...X said:
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Click to expand...
Click to collapse
Well, I'll give it a go, however I did it before and the reboots occurred anyway... I'm now slowly uninstalling all the apps one by one to see when this craziness stops
I'm starting to suspect that it's a fault of Google Play Services, they're always on high positions in my Wakelock and Battery Usage lists, I heard people are also having some other problem with this app.
Edit:
Another thing is that I try to modify something in AppOps (I'm accessing it via some shortcut apps from the Store), but I cannot change permanently any settings (I click back, then enter again some app and it's all 'allowed' again), is this normal?
I'm digging up an old thread, but I narrowed down my problem to Stamina Mode, I think.
I wiped all data via factory reset, reinstalled clean system via PCCompanion and only townel-rooted. The soft-resets began to appear again shortly after first boot. I tried to eliminate differet things and it seems that the reboots occur only when Stamina Mode is on. I've switched it off like a week ago and the phone has been running smooth ever since.
Now I'm just asking out of pure curiosity, has anyone ever stumbled upon similar problem? Is Stamina Mode known for causing any issues of this kind?
Can someone help me like a fast answer maybe? I was working around some lollipop stuff for our device and i actually got it installed and booting...BUT it's stuck on the boot animation.The animation is constantly doiing it's thing.I wanted to make a logcat to see whats the problem but i dont really know how.I installed ADB and that stuff but the PC doesn't recougnize the phone while it's in the boot animation.So an ANYONE please help me i mean to tell me how do you do it? I would greatly appreciate some good answers
Okay... so I'm a biggest noob boob there is...
I installed xposed/etc and used RootCloak... ...but I think I made a major booboo... First I suppose I should say what device I have: RCA Voyager7 tablet{the $40 deal from Walmart's pre-Black Friday sale}.
I "accidentally" [on-purpose] succeeded in rooting my device.... ...I say accidentally because after several failed attempts using KingoRoot... ...I discovered that each time Kingo rebooted my device I needed to unplug the USB from the device at the first boot-up screen and quickly [but carefully] re-insert the usb cable **AS SOON** as the homescreen loaded... ...this wasn't the "accidental" part; this was just observation of behavior after several fails;.. ...kingo rebooted the device some ten or so times and each time I performed the same task... ...but after about the tenth time I accidentally unplugged the usb **AS SOON* as the screen turned off and **BEFORE** the reboot... ...I realized that the device didn't boot-up by itself so I quickly pressed the power button to boot-up [without the usb plugged in] and **AS SOON** as the homescreen appeared on the device I plugged in the USB and THEN Kingo said that root was successful... ...IDK, maybe if I had just "accidentally" did at first what I did after about ten times it would have worked?
Anyway, using RootCloak... ...and in anticipation of any future OTA updates; I hid the root from <all things "android" and "google"> so that my root would not be recognized... ...as much trouble as it was, I did not want to go through the ordeal of rooting again... ...I thought maybe it won't work a second time around... ...apparently I effectively hid the root altogether...
NOW, SuperSU, Titanium Backup, Xposed, and worst of all RootCloak are apparently invisible to/cloaked from my device. It's still rooted, I know, because some apps that require root [like Set CPU and Lucky Patcher] still work...
...so does anyone know how can I reverse RootCloak when I don't have access to it or xposed on my device... ...I tried to install Titanium Backup from Google Play but when installing it said the app was already installed... I tried to re-install xposed but get the error message "trouble parsing package"... ...I also tried to install Root Checker but after installing; it was invisible... ...go figure :/
I guess RootCloak does its job... ...REALLY WELL -lol.
I suppose I could just do a factory reset and start over... ...but I was hoping someone could provide a remedy because I had several apps that I hate to go through the trouble of re-installing and configuring... ...at any rate... ...maybe my "accidental" discovery will help others whom have been having trouble rooting their RCA to finally and successfully root their RCA tablet
Try activating Xposed safe mode as detailed here, then uninstall RootCloak.
If that doesn't work, reflash your rom or restore the backup you should have made before installing the Xposed framework.
Sent from my C6603
Thanks
kingvortex said:
Try activating Xposed safe mode as detailed here, then uninstall RootCloak.
If that doesn't work, reflash your rom or restore the backup you should have made before installing the Xposed framework.
Sent from my C6603
Click to expand...
Click to collapse
Thanks for the reply... ...I just got the chance to check my emails. I went ahead and did a factory reset and re-rooted, etc...
There were some important things I forgot to mention about how I got KingoRoot to work with my RCA... ...for anyone who tries to root their RCA using the method I described: Be sure to disable wireless so no updates will take place on the device and you MUST disable screen-lock...
...and just I had suspected; I only neeeded to do the unplug / re-plug thing once [the right way]. KingoRoot will reboot the device twice: The first time the screen boots into fastboot [*DO NOT* unplug the usb on ANY black screen]... ...ONLY unplug the cable *after* the screen with the dog appears and re-plug the cable **AS SOON AS** your homescreen appears... ...it worked for me; I hope it works for others having trouble rooting their RCA with KingoRoot.
...thanks again for the reply
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
x0nar said:
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
Click to expand...
Click to collapse
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
simms22 said:
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
Click to expand...
Click to collapse
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
x0nar said:
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
Click to expand...
Click to collapse
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
zelendel said:
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
Click to expand...
Click to collapse
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
cam30era said:
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Click to expand...
Click to collapse
Unfortunately that is what I believe I'll have to do.
x0nar said:
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
Click to expand...
Click to collapse
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
zelendel said:
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
Click to expand...
Click to collapse
I've dropped Multi ROM completely. The issue sad-fully still persists. I have even deleted Kernel Control Apps and any apps that revolve around Root. I really am not aware of what I should be doing next other than formatting and just hoping nothing worse happens. Also could you name a few apps that could take out logcat even while booting. In a surprising twist of events, now as soon as I hit reboot on the phone, it enters into bootloop and does not return back to normalcy, until connected to a charger or PC via USB. So I guess, I could take a logcat. Thank You again.