Okay, so I was on BlackBean 3 up until yesterday, when I decided to flash over the Paranoid Android ROM. After a few mix-ups and flashing BlackBean 4, only to flash back to Paranoid Android, I've encountered an issue that, if I recall correctly, began yesterday. Actually, it seems to coincide with the install of Paranoid Android, though I'm thinking it's an issue on my end since I can't find anyone else on here (or even Google) who's posted the same issue...
My SuperUSER permissions mean NOTHING now. Whenever I have my system does something that usually requires an "interactive shell", I'll get asked multiple times to "Allow" or "Deny" (between two and four times)... I've cleared the cache and data inside the app, I've installed Root Checker to make sure I didn't lose root somehow.. Tried updating Busybox (pointless).. I've done all that I've thought to do, and none of my automatic functions from root ever returned. It's kind of annoying having to watch your screen so you can press "Allow" five times before it makes a tweak to your UI or something. How do I restore my fully interactive shell???
If it helps, after my last flash of PA 2.14, I flashed the new Semaphore Kernel (albeit a few hours after I flashed the ROM).. This was my first time flashing a Kernel, but I Wiped Cache + Wiped Dalvik Cache before flashing.. Everything looked fine until my phone rebooted and after showing the Vibrant logo, it would just go blackscreen. Not even my booting animation. So I went back into Recovery, cleared Cache, Dalvik, Format/System, all that.. and then reflashed PA 2.14. I never reflashed the Kernel cause I don't know what happened the first time. Eh..
Thanks in advance!
Try flashing SuperSU zip. I don't have the zip but if you search it, you should find it. That should fix it, it did for others with this issue.
sent from the depths of helly bean
samsgun357 said:
Try flashing SuperSU zip. I don't have the zip but if you search it, you should find it. That should fix it, it did for others with this issue.
sent from the depths of helly bean
Click to expand...
Click to collapse
Thanks, I just located a zip for it. Should I do anything like Clear Cache/Dalvik first or just flash the zip??
Iam2Smooth said:
Thanks, I just located a zip for it. Should I do anything like Clear Cache/Dalvik first or just flash the zip??
Click to expand...
Click to collapse
You can clear cache and dalvik but not required. FYI, clearing cache and dalvik cache regularly reduces lag.
sent from the depths of helly bean
samsgun357 said:
You can clear cache and dalvik but not required. FYI, clearing cache and dalvik cache regularly reduces lag.
sent from the depths of helly bean
Click to expand...
Click to collapse
Oh okay, I was wondering how I go about kind of "refreshing" a ROM without having to flash again. Thanks!
Related
hey guys i hope i put this in the right section... anyways, i was using cm7.1 stable on my fascinate with the stock kernel that came with it, which was awesome i must say. but recently i decided to try out the glitch kernel 13.1 as ive heard its even faster and overclocks better. and it is lol, its reallllll freakin fast but now my wifi wont work. worked perfectly on the other kernel but now when i hit the button to turn on the wifi, nothing happens, it kinda lights up and just stays there and wifi never turns on. does anyone have any work arounds for this? i really want to keep this kernel because its damn stable and fast but wifi is my only issue.
thanks guys
toggle airplaine mode off/on
Make a Nandroid, the wipe data. (restore the Nandroid if it doesn't work) I had this problem on my Iconia Tab after I did a dirty flash.
am I reflashing the kernel or cm7? I tried to airplane mode toggle and it just says error when I try to enable wifi in the settings menu
Don't reflash anything, just wipe data & dalvik.
did nandroid backup and cleared dalvik and did factory wipe, still no dice. am i missing something? did i get a corrupted kernel install file or something?
username8611 said:
did nandroid backup and cleared dalvik and did factory wipe, still no dice. am i missing something? did i get a corrupted kernel install file or something?
Click to expand...
Click to collapse
I've seen this before... I only have a minute to type this. There is a kernel cleaning script you can get.. by lippol I believe. Sorry to send you on the hunt. If that don't work, backup all your apps/data and do a full wipe (just wipe, not flash) on the phone and reflash kernel.
-Maniac
what does a kernel cleaning script do? theres an option to clean the kernel in the glitch kernel, is that the same? ive reflashed the glitch kernel too after reclearing dalvik and factory reset and still no wifi. would using a kernel cleaner do anything after reflashing?
ok i decided to go ahead and try the script, i was able to find it without a problem. cleared cache, ran it, and reflashed a redownloaded kernel and........ it works!! thanks so much guys!
username8611 said:
ok i decided to go ahead and try the script, i was able to find it without a problem. cleared cache, ran it, and reflashed a redownloaded kernel and........ it works!! thanks so much guys!
Click to expand...
Click to collapse
Sweet. You're welcome. That's my good deed for today!.
-Maniac
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!
I've had my NT for quite a while now. Once I got it, I'm pretty sure I used the nook & zergy tool to root, and that's been it.
I've been on 1.4 forever, with CWM 5.5.04 as my recovery (on the emmc maybe? I don't need an sd to boot into it).
I've noticed that my stability has been declining, with random reboots here and there and rapid battery drain, so I decided it was time to get back to some flashing. I started with this http://forum.xda-developers.com/showthread.php?t=1494367, using the first 1.42 version as the others are dead. Everything loaded and booted fine, but it reboots with little provocation...you know, like, touching it, and may or may not go into a reboot cycle 3-4 times before chilling out. I still can't do much without triggering a reboot though. Search in the market? Reboot.
I attempted to restore using this http://forum.xda-developers.com/showthread.php?t=1402190, but it just boots right up normally. If I manually flash it it fails.
So, here I am with a non-bricked NT that doesn't do me much good, and I'm wondering how to get it back in order.
Are you wiping cache and dalvik cache from recovery?
Also, are the reboots occurring on battery power, or on charging as well?
Sent from my ST27i
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
n8w said:
I've done a data wipe and wiped the dalvik from cwm. I've not wiped the cache partition if that's what you're asking. Reboots are when it's unplugged or plugged.
Click to expand...
Click to collapse
Ok. Data wipe does wipe cache as well.
You could try a cm Rom to see if the problem persists, but if you are looking for warranty, better to stay on stock.
Also, if you pull last kernel message ( from /proc/kmsg) , some dev may be able to determine cause for reboot.
I think it's possible this is a hardware issue.
Sent from my ST27i
Thanks for jumping on this. I went ahead and wiped the cache partition, because "why not?" and I'll be damned, but I haven't had a reboot yet. Hitting search in the market was a sure trigger, and it's behaving well so far.
satan89 said:
Ok. Data wipe does wipe cache as well.
...
Click to expand...
Click to collapse
/Cache and /Data are two separate partitions on emmc, and unless something change in recent CWM/TWRP Recovery, there are separate menu options to wipe each of them.
/Data is typically used to hold user downloaded/installed apps, and should not need to be wiped except when upgrading to a different ROM or a different ROM version.
I really don't know much about how all that works, but for whatever reason, wiping the cache fixed my issue.
Sent from my DROID RAZR using Tapatalk 2
After flashing a couple of Roms I found my recovery i made of the stock Rom now says android is updating everytime i turn it on.
are using TWRP and wiped Davlec cashe but now restart and upgrading again..
started with about 43 updates and this time after davlesc reset is 80 updates..
Ive only ever seen this when installing Gapps to a new build it does it once..
This recovery never had Gapps on it and shouldnt be doing this?
Ive searched but cant find specific advice on the S3..
Anybody can help?
Thanks..
MRBR7 said:
After flashing a couple of Roms I found my recovery i made of the stock Rom now says android is updating everytime i turn it on.
are using TWRP and wiped Davlec cashe but now restart and upgrading again..
started with about 43 updates and this time after davlesc reset is 80 updates..
Ive only ever seen this when installing Gapps to a new build it does it once..
This recovery never had Gapps on it and shouldnt be doing this?
Ive searched but cant find specific advice on the S3..
Anybody can help?
Thanks..
Click to expand...
Click to collapse
This is because your cache is being rebuilt on every reboot. Most likely from restoring a stock rom after using custom roms. This is never a good idea. If you need to return to stock you should do it by Odin. Stock roms do not back up/restore properly.
so this only happens after you wipe Dalvik? That's what's supposed to happen
No its been doing it every time i turn phone on for ages.
Just i read somewhere to wipe davlec should fix it.but then doubled the amount of updates after...
anyway i think will re flash rom from odin again should be better.
was just wondering if there was something simple i didnt do..but i guess its cause i came from non stock rom before..
Thanks for answers..
Are you sure that somewhere in twrp settings or anywhere else that you haven't set the device to wipe dalvik on each boot?
Did you delete some odex files from your system/app
Sent from my GT-I9300 using xda premium
freddy1991 said:
Did you delete some odex files from your system/app
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
This has nothing to do with the issue. The issue is that the delvic cache is being deleted on reboot. A full wipe and reflash should fix him/her right up.
Whenever I use ANY rom that isn't based on stock I get random reboots. I'm currently on stock ics and really want to be able to run later versions of android. I can run padawan rom and blackstar perfectly fine without any random reboots but for other roms I somehow get random reboots. Am I flashing roms the wrong way or is something wrong with my phone?
Any help is appreciated!
shaftgobbler said:
Whenever I use ANY rom that isn't based on stock I get random reboots. I'm currently on stock ics and really want to be able to run later versions of android. I can run padawan rom and blackstar perfectly fine without any random reboots but for other roms I somehow get random reboots. Am I flashing roms the wrong way or is something wrong with my phone?
Any help is appreciated!
Click to expand...
Click to collapse
After flashing new ROM, did you wiped cache+dalvic cache and factory resetted your phone?
If not then do so, it'll be helpful for you.
Also try to clean flash your ROM, after wiping system and data.
PS: Also check the ROM your flashing is stable enough and don't have major bugs.
Regards,
hitman-xda
hitman-xda said:
After flashing new ROM, did you wiped cache+dalvic cache and factory resetted your phone?
If not then do so, it'll be helpful for you.
Also try to clean flash your ROM, after wiping system and data.
PS: Also check the ROM your flashing is stable enough and don't have major bugs.
Regards,
hitman-xda
Click to expand...
Click to collapse
I tried that many times lol but it still didn't help though. Might try again though.
shaftgobbler said:
I tried that many times lol but it still didn't help though. Might try again though.
Click to expand...
Click to collapse
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
hitman-xda said:
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
Click to expand...
Click to collapse
k will try when I have the chance I appreciate the help:good:
hitman-xda said:
Clean flash ROM > wipe cache+dalvic cache > reboot > flash gapps > wipe cache+dalvic cache > reboot > factory reset > reboot
Hope the above thing works
Regards,
hitman-xda
Click to expand...
Click to collapse
Order is incorrect. Factory reset, wipe cache and dalvic cache, flash ROM, flash a compatible gapps package, wipe cache and dalvic cache again, reboot system. Let rom fully boot. Only enter your wi-fi and google account info at this time (If asked) .Let settle for at least 10 minutes after boot before playing with your newly installed ROM. Best to use gimmeitorilltell's TWRP version 2.8.0.0 or possibly newer or most recent CWM. Use of incorrect gapps, or fiddling with a roms settings before letting it settle in will result in problems. Follow instructions/tips in the OP of the forum thread dedicated to your your chosen ROM.
Sent from my SAMSUNG-SGH-I717
developweb said:
Order is incorrect. Factory reset, wipe cache and dalvic cache, flash ROM, flash a compatible gapps package, wipe cache and dalvic cache again, reboot system. Let rom fully boot. Only enter your wi-fi and google account info at this time (If asked) .Let settle for at least 10 minutes after boot before playing with your newly installed ROM. Best to use gimmeitorilltell's TWRP version 2.8.0.0 or possibly newer or most recent CWM. Use of incorrect gapps, or fiddling with a roms settings before letting it settle in will result in problems. Follow instructions/tips in the OP of the forum thread dedicated to your your chosen ROM.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
k will try that thanks guys for the help
Well I followed the steps exactly as told and I'm still getting random reboots. What shud I do next? I'm using beanstalk 4.3 since some of the kitkat Roma I use seem buggy and I can't get gaps to work on lollipop
shaftgobbler said:
Well I followed the steps exactly as told and I'm still getting random reboots. What shud I do next? I'm using beanstalk 4.3 since some of the kitkat Roma I use seem buggy and I can't get gaps to work on lollipop
Click to expand...
Click to collapse
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Edit: and lollipop gapps come in 5.0 and 5.1 and like I said earlier make sure you've got the right ones.
Sent from my SAMSUNG-SGH-I717
developweb said:
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I did both of those already. I'm currently using a new battery and went back to stock multiple times then returning to a rom. Nothing seemed to work.
developweb said:
Ok, I'll bite again....
Many who have had ongoing, unexplainable things going on with their phone recommend 1)a new or different battery (a fresh battery does wonders) or 2)wiping everything and going back to full stock....whatever shipped with your phone. Like a reset. Start over.
Edit: and lollipop gapps come in 5.0 and 5.1 and like I said earlier make sure you've got the right ones.
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Well im not having random reboots now thanks for the help though I hope it stays this way. But I get reboots when changing cup speed and governor or stay in camera app for too long. Probably just the rom itself. Thanks all for the help! I'll tell if anything goes wrong:good: