Hey guys here at xda!!
I've got a little problem and i'd like to know if someone can help me fix it
So, yesterday i used Rom Toolbox to disable some receivers for some apps....nothing too special, i just disabled the ones i though weren't really needed for those apps....also some notification ones or at boot time ones i think (also i don't remember touching any startup apps because i already had handled those with startup manager free)....anyway: now reboot is stuck...at, well, reboot (bootanimation)...
Does anyone know how i can restore Rom Toolbox changes, or reenable all receivers from recovery?
Or something else which might help?
Unfortunately, i don't have either a recent nandroid nor a recent titanium backup. So switching roms would be a pain...
MY ROM: Foxhound 0.1 for Galaxy S3 based on stock 4.2.2 (kernel is stock) and i have xposed framework, just in case that might help:good:
I really appreciate your help guys! PEACE!
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
boomboomer said:
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
Click to expand...
Click to collapse
thanks for the reply!
safe mode (which i had never even known existen on android) appears to not be working....i mean it keeps getting stuck at boot so who knows why,
i flashed the rom, rebooted, it booted (yay) and then the usual message popped up with "updating applications x out of x", and after having finished it appears to be stuck at the same message with "opening applications under way" (translation from italian). the title of the message is "updating/upgrading android os"...
i think i might be force to flash a new rom
Related
After flashing a new version of CM11, i found myself in a loop upon startup where many of the core applications of android stopped working. When i reverted back to the old version that worked(I didn't have a backup saved but rather i flashed the older nightly of the rom again), I noticed that my home button, lock screen, and notification bar/toggle screen wasn't working any more. I looked into it and looked at my apps, and saw an unnamed app with the description "com.android.keyguard". upon looking this process up, i found out that when people disabled this process their home button, lock screen, and notification bar stopped working (coincidental eh?), and decided that this was the source of the problem.
Is there any way to load on a new, fresh version of "com.android.keyguard" or should i just do a factory reset? I would prefer to save my local data, but if i must do it in order to have a phone that does anything useful, i obviously will.
If I need to do a factory reset, what is the cleanest and smartest method of doing so? I know titanium backup can cause a lot of problems (and in this case i'm worried it will duplicate com.android.keyguard), but I assume there is some sort of method that makes a factory reset while retaining the bulk of user data very easy. am i correct?
Do a full wipe and flash again, check the md5 of your download.
Only use titanium for use apps, never system apps or settings. There is no easier way to change rom.
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Jahid4 said:
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Click to expand...
Click to collapse
Flash back to stock and start over.
Beamed in by telepathy.
Problem occur in stock fw(3.2.4), Nexus 2.01 and even after rollback to .3.1.0
My HDX when lying on the table goes on and off every minute(clock resets to 0:00 after each reboot), but when I start to use it, it's working fine without auto reboot...
At first when I flashed Nexus everything was ok but then I was busy and haven't used my tab for few weeks and now I have this annoying problem.
Because of this battery goes low very fast.
Is this hardware or software problem?
Hope for your help.
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
futzmaster said:
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
Click to expand...
Click to collapse
I'm now on 13.3.2.3.2 and problem is still there... I get clock reset on stock fw not nexus, is this normal too?
I also did factory reset...
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Davey126 said:
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Click to expand...
Click to collapse
Did hardware reset, unfortunately without success...
What do you mean with "booted into recovery"? Fastboot or another fw slot with safestrap?
Flashed cm11 and still got this issue! I'm done...
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
futzmaster said:
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
Click to expand...
Click to collapse
alright, what's the steps to recover to clean stock from twrp with cm11?
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).
Hey guys i just recently unlocked my bl and rooted with twrp and Magisk.anyways my problem im having is that every once in awhile i will do something like disable a certain app or i most recently installed a zip that added init.d support and then i try to boot and it boots up my launcher gives me like 5 seconds of time and then INSTANTLY will shut itself down . i just tonight found out how to boot into twrp from button boot so i feel so much better about this ever happening again because i was having to quickly try to run my root quick reboot recovery app which took hours sometimes. But im just interested if anyone knows how to stop this from happening or even why/ what is causing it to make itself power off? Thanks in advance
GuwopMontana said:
Hey guys i just recently unlocked my bl and rooted with twrp and Magisk.anyways my problem im having is that every once in awhile i will do something like disable a certain app or i most recently installed a zip that added init.d support and then i try to boot and it boots up my launcher gives me like 5 seconds of time and then INSTANTLY will shut itself down . i just tonight found out how to boot into twrp from button boot so i feel so much better about this ever happening again because i was having to quickly try to run my root quick reboot recovery app which took hours sometimes. But im just interested if anyone knows how to stop this from happening or even why/ what is causing it to make itself power off? Thanks in advance
Click to expand...
Click to collapse
What kind of app are you disabling? System app that is needed? Or sounds like the zip you flashed screwed some stuff up?
Uninstall that, restore the TWRP back up you of course made before making all these changes.
I'm on rooted stock firmware with some Magisk and Xposed mods and my phone doesn't shut down.
Stock firmware -- especially last Oreo -- is very well optimized already. I know people coming from even older phones (pre 2017) have the idea they NEED to immediately remove and disable stuff but that actually often messes the phone up, big time. They are now putting in lag that wasn't there before. Or they are removing functionality they don't understand. System apps are no longer standalone silos. They are connected like a firmware web. If you blow holes in that you will now have unstable phone.
You can freeze some system apps in Titanium Backup and unfreeze them if you see problems. I have only frozen a couple myself as my rooted Oreo US998 runs very smoothly.
I'm pretty sure it's a phone/dialer app that is causing the issue when I freeze the app, and also I installed the fox recovery and flashed the init. D enabler zip that comes with it and it caused my device to do the same thing but since my last post I installed liquid Rom and everything is running great