Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
botzen67 said:
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
Click to expand...
Click to collapse
If you have Titaniumbackup Pro then just freeze the update/updater apk. If not, I would suggest getting it, it is well worth the cost.
Great suggestion. I have TiBu Pro and have frozen the two Update apps I found in the list along with "VZW Package Installer 1.0" and "Field Test 2.1-update1" and "Field Trial 2.2.1", having done the last three just now. It did try to do yet another update a few hours ago, so we'll have to see if the last three do the trick.
Anybody got any other suggestions for Apps I should freeze to prevent OTA updates?
Update: None of the items I've frozen seems to have made a difference. Still looking for other ideas.
I'm thinking it was DM.apk or something similiar that controlled ota updates. I don't have a stock rom running atm so i can't be sure. When you find the correct one you won't be able to get to the update phone screen from settings any longer. Wish i could be more help but i just can't remember.
Sent from my HTC ThunderBolt using Tapatalk
I was having that same problem and I just broke down and applied the update. I used clockwork rom manager and a rooted/deodexed update file that I found on the forums (linked from androidpolice, i think). Flashed the update, without wiping the current setup, then flashed the radio from the bootloader. Worked like a charm. I've got the update, it's not searching for more, and it reinstalled all the bloatware that I deleted instead of freezing when I got the phone. I went back through and freezed all the bloat junk, and my TB is running better than ever. Oh, and I'm just running a rooted stock rom.
I too suffered the same problem. I just ended up installing a custom rom to get rid of it for good. Best decision I ever made, I really like the Synergy build.
Related
I get this message when I boot up.
I cannot access settings so I cannot perform a factory reset.
Is there any way to factory reset when you cannot access "Settings" because of constant force closes.
I am running stock but with lots of side-loaded apps.
I can access the file explorer. That is the only thing I can open that will remain open even though I get constant force close popups like "android.process.acore has stopped... android.process.media has stopped unexpectedly...
Is my gtab toast? Can it be saved or should I return it?
I get this all the time, with all the mods I do. Don't worry, your system is fixable.
For me, I use clockworkmod recovery .08. There's a "fix permissions" option and this always fixes the problem for me. It also allows a data wipe within recovery.
If you are 100% stock, you could try one of the stock ROM's here as well - that might get you working. You have a few options, here. Check out the FAQ in my signature. I'm actually posting up the new stock update that I pulled from TnT, today.
EDIT: Direct link the the stock ROM updates -- http://forum.xda-developers.com/showthread.php?t=842000. You'd need to understand how to actually run these, which I mention in the FAQ section.
thx Roebeet, I was able to update to the new stock rom.
But I still have the same problem. Is there any other way to wipe my data. Can it be done while connected by usb or do i have to root it?
Is there any hardware button method to do a factory reset?
I still cannot open settings... it gets canceled by the force closes.
I am ready to give upon my G-Tab which I was enjoying so much.
Does anyone know how to wipe the date if you cannot open settings???
Try clockworkmod - it really is a great tool. You can find it in the Tnt Lite dev section as I have a link for .08.
For UID issues, "fix permissions" will correct it. And you can wipe data via clockworkmod as well. You can even remove it by flashing back to stock -- the latest stock firmware works as I've done it myself, the other day.
Btw, there are so many threads here that I sometimes miss replying. I dont ignore, I just might miss a post. Always feel free to PM me if you have a question.
I had a similar issue where something got corrupted in my user data and I was completely unable to start the settings or open the keyboard. I had to flash back to the full vanilla ROM because it contained clockworkmod, which was the only option available to accomplish a factory reset. That wasn't a fun day.
Think I figured out a key reason for sudden UID issues
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Again, the Tap UI team and who hired them and approved it on the Gtablet should be fired, rehired for a minute and then fired for good. Word.
This sounds kind of "preachy," but don't give up.
There is a learning curve to the G-Tablet, and it takes a good bit of reading on this site and assimilating the info.
I will testify that I had a hugely bad malfunction and and even worse fix on my tablet.
Using suggestions from helpful folk -- and carefully researching what I needed to do -- I was able to get my tablet back working just fine. To be sure, it's not stock any more!!! But I actually believe that with all I learned about flashing, mods, etc., I now could go back and make it stock again if I wanted to.
Don't give up. Just keep reading and researching the learning.
Rev
rushless said:
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Click to expand...
Click to collapse
Not true for me, I installed the new Gmail from the Market with no problems. I am on TNTLite 2.2.1.
Google Voice has always been a hack for a tablet, since it is not actually phone. You might want to pull it out and see if your issues are solved.
I am back up and running thanks to clockwordmod. Thanks again!
ninjaprofessor said:
I am back up and running thanks to clockwordmod. Thanks again!
Click to expand...
Click to collapse
Good to hear and thanks for the update!
I am currently having this problem. I am hoping to sell my 10" Android 2.2 Tablet PC on Craigslist... I need to fix this Error... I've only used it 10 times to play Angry Birds. The forum with the links I am confused as to what one to use... I am younger I must say. I am not a 21 year old "computer whiz"/.NET/OS maker... I do make websites. Besides that... I do not know how to "Wipe my system partition" as my Error message says to. Especially due to the fact I cannot open Settings. PLEASE HELP. I may have repeated things said above in his problems but I would like a "NOOB" walk through... (Because I am one). Please help. Thanks in advance. -Sophomoric
Hey, I had a same after my phone battery was empty and it turned off. I kept it off and recharged it, then I had the feeling "I'm feeling Lucky" -.-' so nice from google. xD
Had to wipe everything then full reinstall... such a pain.
Probably the cleanest solution HERE
I'm wanting to install [ROM][AOSP]LiquidSmooth-ICS-v1.5-MR3[10/02/2012] But I can't get it or any other rom to install. I'm running ota ics with root and all that good stuff. I don't know all that much about the thunderbolt because I'm always had Motorola and my nexus 7. When I try it just doesn't do anything. Fails. I have been trying for months but have taken a long break from it due to just giving up. But now my phone is trying to push a 20 Mb update that just makes my phone not boot because of my recovery.
which recovery are you running as its known 4ext has issues with ota ICS. also did you check the md5 to make sure they match. it sounds like its not downloading right and your download is getting corrupted.
Sent from my Infected HTC Rezound using Tapatalk 4 Beta
The problem is that you downloaded the second update that Verizon pushed out. It wasnt very big since it only patched some apps to update them, updated the cdma radio and fixed an hac audio issue people were having problems with. I doubt it will work but try flashing santods ota killer v2 and then clear caches in recovery.
Sent from my ADR6400L using Tapatalk 2
I'm really more worried about installing that liquid smooth rom rather than the annoying update. I just defer it everyday. I have downloaded it SEVERAL SEVERAL times and it always does the same thing. I tried again last night and It made me remember what exactly happens. It does install and boot but I can't get signal at all and then the whole rom just stops working. Doesn't let me do anything. The whole updating applications or something.
Hi,
I'm having this issue where I get a pop-up window saying "Android is upgrading..." and "Starting applications..." every time I reboot the phone. It's not the same as when I wipe the dalvik cache where it states "Optimizing applications # through #" for about a minute or two on reboot. What I'm seeing is about 1 to 3 seconds.
I did a complete factory reset, re-flashed the ICS RUU as well as the ROM. It was fine in the beginning and for quite a while after I reinstalled my apps but it eventually came back.
I tried uninstalling apps a few at a time and it didn't change anything until I got down to the last four and then it went away. So, I then tried restoring from nandroid backup and just removing those four apps but it didn't work that time. The issue was unaffected.
I realize that the symptoms point to one or more of my apps but I was wondering if there is some kind of diagnostic logger that I can use to record whats happening during reboot that might offer some hints as to which one(s). One possible indirect culprit might be Superuser. I've had a permanent issue with updating the SU binary. When I do, I lose the ability to add new root apps. I keep root for existing root apps, but SU won't detect any requests from new apps. Therefore, I simply don't update the binary and I have no problems with new apps.
Any suggestions or recommendations would be greatly appreciated.
Thanks.
RuLEoF2 said:
Hi,
I'm having this issue where I get a pop-up window saying "Android is upgrading..." and "Starting applications..." every time I reboot the phone. It's not the same as when I wipe the dalvik cache where it states "Optimizing applications # through #" for about a minute or two on reboot. What I'm seeing is about 1 to 3 seconds.
I did a complete factory reset, re-flashed the ICS RUU as well as the ROM. It was fine in the beginning and for quite a while after I reinstalled my apps but it eventually came back.
I tried uninstalling apps a few at a time and it didn't change anything until I got down to the last four and then it went away. So, I then tried restoring from nandroid backup and just removing those four apps but it didn't work that time. The issue was unaffected.
I realize that the symptoms point to one or more of my apps but I was wondering if there is some kind of diagnostic logger that I can use to record whats happening during reboot that might offer some hints as to which one(s). One possible indirect culprit might be Superuser. I've had a permanent issue with updating the SU binary. When I do, I lose the ability to add new root apps. I keep root for existing root apps, but SU won't detect any requests from new apps. Therefore, I simply don't update the binary and I have no problems with new apps.
Any suggestions or recommendations would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
1.) How did you root the rez? some are very picky 2.) are you using Titanium backup to restore system apps or using an app like kernel tuner?
I used the ICS RUU installation guide on TeamBAMF which walks you through using the HTC bootloader unlocker, flashing a recovery and a custom ROM. Later on, I used the S-OFF tool from JuopunutBear and flashed RezROM Ex 3.4.
I do use TBU but not to restore system apps or any data in general. I understood a long time ago that restoring data can lead to trouble so I rarely do it. I occasionally use TBU to restore user apps (no data) but have gotten into the habit of using the market links to get the app directly from the market.
RuLEoF2 said:
I used the ICS RUU installation guide on TeamBAMF which walks you through using the HTC bootloader unlocker, flashing a recovery and a custom ROM. Later on, I used the S-OFF tool from JuopunutBear and flashed RezROM Ex 3.4.
I do use TBU but not to restore system apps or any data in general. I understood a long time ago that restoring data can lead to trouble so I rarely do it. I occasionally use TBU to restore user apps (no data) but have gotten into the habit of using the market links to get the app directly from the market.
Click to expand...
Click to collapse
what recovery are you using? Amon ra 3.1.6 has the su and superuser installer built in and ive never had issues....id also suggest after actually running an RUU.exe and not an OTA (ph98img file) to do the amon ra method and a pure clean flash...should fix your issue
Ok. I'll try your suggestion to help solve the Superuser problem, but what do you think about getting rid of the "upgrading" messages? Is there a way to record what the system is doing during reboot?
RuLEoF2 said:
Ok. I'll try your suggestion to help solve the Superuser problem, but what do you think about getting rid of the "upgrading" messages? Is there a way to record what the system is doing during reboot?
Click to expand...
Click to collapse
if you are familliar with adb you can pull a logcat....to be honest though this does sound like either a bad or unclean flash of a rom or the whole rom itself
REV3NT3CH said:
if you are familliar with adb you can pull a logcat....to be honest though this does sound like either a bad or unclean flash of a rom or the whole rom itself
Click to expand...
Click to collapse
You are correct that the re-flash will solve the problem, but only temporarily. If this was a first time occurrence, I agree that a pure clean re-flash is the best approach but I've already done that numerous times, well over a dozen in the past year or so.
Only a couple weeks ago I did a complete wipe of everything (factory reset, data, cache, dalvik cache, boot, system, rotate settings AND battery stats) and then re-flashed the RUU four (4) times back-to-back. The TeamBAMF guide says to flash it twice so I doubled it to be sure. I then flashed the ROM twice. That solved the "Updating" problem as it always has. However, once I finished re-installing my most frequently used apps, the problem came back.
It hasn't been consistent. It doesn't always come back. Doing the wipe and re-flash works about 50% of the time. I'll go months without it showing up again and then all of the sudden, there it is. It doesn't seem to correlate to the installation of any one particular app. I've tried installing only a few at a time and watching it but when it does come back, it never occurs until after I've installed my most basic line-up.
If there is any one activity that it seems to follow it is after I've had another issue (usually tinkering with a root app or mod and didn't like the way it turned out) and performed a wipe and nandroid restore. It doesn't come back every time, but it's on that initial reboot when I usually first notice it. In those cases, it's always hard to say whether the root app or mod caused the problem or did the wipe and restore do it.
RuLEoF2 said:
You are correct that the re-flash will solve the problem, but only temporarily. If this was a first time occurrence, I agree that a pure clean re-flash is the best approach but I've already done that numerous times, well over a dozen in the past year or so.
Only a couple weeks ago I did a complete wipe of everything (factory reset, data, cache, dalvik cache, boot, system, rotate settings AND battery stats) and then re-flashed the RUU four (4) times back-to-back. The TeamBAMF guide says to flash it twice so I doubled it to be sure. I then flashed the ROM twice. That solved the "Updating" problem as it always has. However, once I finished re-installing my most frequently used apps, the problem came back.
It hasn't been consistent. It doesn't always come back. Doing the wipe and re-flash works about 50% of the time. I'll go months without it showing up again and then all of the sudden, there it is. It doesn't seem to correlate to the installation of any one particular app. I've tried installing only a few at a time and watching it but when it does come back, it never occurs until after I've installed my most basic line-up.
If there is any one activity that it seems to follow it is after I've had another issue (usually tinkering with a root app or mod and didn't like the way it turned out) and performed a wipe and nandroid restore. It doesn't come back every time, but it's on that initial reboot when I usually first notice it. In those cases, it's always hard to say whether the root app or mod caused the problem or did the wipe and restore do it.
Click to expand...
Click to collapse
which leads me to believe its a rom issue for that specific rom...ive never used that one so i cant verify thats what it for sure is....but having to flash the same rom twice for it to work seems like what can cause it in the first place because it already obviously clearly has some bugs...also flashing an RUU (which is a windows .exe based program...many people confuse this with an OTA ph98img file) is actually partitioning, wiping, and re installing the pure factory OS, HBOOT, and Recovery... which no recovery can do....which shouldnt be done directly before a rom install...a full thorough wipe in a custom recovery and then the install of the actual rom you are trying to obtain is how it should be done...to be honest though with how buggy this rom sounds id just suggest going to a new rom....which i have good suggestions for sense based ones
REV3NT3CH said:
which leads me to believe its a rom issue for that specific rom...ive never used that one so i cant verify thats what it for sure is....but having to flash the same rom twice for it to work seems like what can cause it in the first place because it already obviously clearly has some bugs...also flashing an RUU (which is a windows .exe based program...many people confuse this with an OTA ph98img file) is actually partitioning, wiping, and re installing the pure factory OS, HBOOT, and Recovery... which no recovery can do....which shouldnt be done directly before a rom install...a full thorough wipe in a custom recovery and then the install of the actual rom you are trying to obtain is how it should be done...to be honest though with how buggy this rom sounds id just suggest going to a new rom....which i have good suggestions for sense based ones
Click to expand...
Click to collapse
Well, if you wouldn't mind offering some of your ROM suggestions and perhaps a sound RUU download source I'll give it a go and see what happens. I'm sure the initial results will be positive, it's the long-term that will be the real test.
One more piece of potentially useful information. I've converted one market app from user to system and froze, uninstalled or converted several user apps that were installed as system apps by the ROM. I read in one thread where someone had the same issue and a responder theorized that it could be from converting a user app to system. The responder followed saying the issue could be a symptom of the converted app not having corresponding "odex" files. I'm only a modest tinkerer and certainly not a developer so I'm not sure what that means or how important that is. However, I tried reversing the three conversions that I did and the issue persisted.
RuLEoF2 said:
Well, if you wouldn't mind offering some of your ROM suggestions and perhaps a sound RUU download source I'll give it a go and see what happens. I'm sure the initial results will be positive, it's the long-term that will be the real test.
One more piece of potentially useful information. I've converted one market app from user to system and froze, uninstalled or converted several user apps that were installed as system apps by the ROM. I read in one thread where someone had the same issue and a responder theorized that it could be from converting a user app to system. The responder followed saying the issue could be a symptom of the converted app not having corresponding "odex" files. I'm only a modest tinkerer and certainly not a developer so I'm not sure what that means or how important that is. However, I tried reversing the three conversions that I did and the issue persisted.
Click to expand...
Click to collapse
if youve already used an ruu once you dont need to do it everytime you flash a rom....and depending on the rom certain recoveries wont work for them...good example amon ra will not work for JB or higher....if staying on ICS or sense based roms stick with amon ra only....im guessing your looking for a good Sense based rom correct?.....as for converting apps...i highly suggest against it on sense rom and can cause issues with the rom...on aosp its fine but sense just doesnt like some of them
REV3NT3CH said:
if youve already used an ruu once you dont need to do it everytime you flash a rom....and depending on the rom certain recoveries wont work for them...good example amon ra will not work for JB or higher....if staying on ICS or sense based roms stick with amon ra only....im guessing your looking for a good Sense based rom correct?.....as for converting apps...i highly suggest against it on sense rom and can cause issues with the rom...on aosp its fine but sense just doesnt like some of them
Click to expand...
Click to collapse
My mistake, but I should have been more specific. I've only re-flashed the RUU three... maybe four times since I've owned the phone and only as a last resort to fix a problem that a wipe and/or ROM re-flash alone wasn't correcting.
As for recovery, I've only used Amon Ra on my Rezound. It's what was recommended in the Team BAMF guide and I've stuck with it. I do prefer a sense-based ROM and ICS works fine for me right now. The HTC Incredible was my first smart phone and I rooted that within a month of getting it. I tried a few ROMs but eventually settled on Skyraider which I really liked. RezROM is the only comperable ROM that I've come accross for the Rezound, but if you have recommendations, I'll give them a try.
Here's what I've done so far. The ICS RUU linked in the Team BAMF guide was an internal flash through the bootloader. To eliminate that as a possible cause, I found a couple .exe versions to run from my PC.
On the first run, I immediately flashed RezROM and used Amon Ra to install Superuser and SU as you suggested. I updated Superuser and then installed a few basic root apps: Titanium Backup, Root Explorer, QuickBoot, Busy Box, Root Checker and Root Validator. There were no issues until I starting using those root apps. I was periodically rebooting and it wasn't until I updated Busybox and ran TBU and Root Explorer that the "Android is upgrading..." message came back. Worse than before, it was doing the "Optomizing apps # through ##" part where before it was just the "upgrading" message. I uninstalled all of them one-by-one but whatever happened was perminant because it didn't go away so I did a full wipe and used the second ICS RUU .exe. On the second run I stayed stock. Again, I used Amon Ra to install Superuser and SU. I updated Superuser and then installed those same basic root apps. So far, no issues.
With these results, it's pretty evident that the problem is ROM related, but not necessarily a bug as much as a compatibility discrepancy. This issue has never been this persistent until the last few months and within that time, there has been several updates for TBU, Root Explorer and Busybox. I agree that switching to a different ROM may be the ultimate solution, but unless there is one that is a RezROM comparable, I'm not ready to write it off just yet. If there's a way to pin point which app is the cause, I might be able to find a workaround or persuade the developer to come up with a fix, I'd much rather try that first.
But again, I'm certainly interested in trying out any ROM suggestions you might have to offer in the meantime.
In the process of trying to nail down this problem, I've discovered that it appears to have something to do with the relationship between superuser and RezROM.
Since I first flashed RezROM, I haven't been able to update superuser or the binary in any way. In addition to downloading from the market, I've tried re-installing superuser with Amon Ra, flashing it from the sdcard in recovery and from adb. No matter how I do it, I either lose root or it shuts down superuser's ability to detect requests from new root apps. I tried to find a solution but had no success so I just decided to ignore it as long as it didn't effect functionality. I've had root app issues here and there but always chalked it up to a bug with that particular app and either found a fix or ditched the app altogether.
I've been able to isolate superuser as the cause of the "upgrading" message issue with several full wipes, RezROM and RUU re-flashes. In my last three attempts to narrow it down, I did completely sterile RUU and RezROM flashes and used Root Explorer and Root Checker as test apps. In each attempt, I lost root and the "upgrading" messages returned as soon as I updated superuser or the binary. I tried doing the same with the stock ROM and with one of the BAMF ROMs and these problems don't occur with either of them.
So, with the "Android is upgrading" message popping up repeatedly, having new stability problems with previously dependable apps and increasing system bugs, it's apparent that the consequences of having such a severely outdated superuser has finally caught up with me. It definitely looks like RezROM is the problem and unless there are some options that I might try to fix it myself, it's up to the developer. I've contacted them but I'm not optimistic that they'll be willing to put any time into coming up with a fix since the Rezound is so "dated".
I had this popup on every boot on my Evo 3D with the stock ICS Sense 3.6 ROM, I still have it on my Rezound with a custom ICS Sense 4.1 ROM. I just assumed it's standard behaviour from Android, why would you think it's an issue if it doesn't cause any problems?
Hey all,
I have a Razr Maxx (well until a few months from now when i can get a better phone).
It is rooted. and has SafeStrap (I used to use the other slots to try some 4.1.2 and 4.3 roms but they all had issues with the radio signal so just been using Stock rooted rom), and VooDoo OTA rootkeeper (Verizon updated my phone OTA the other day, VooDoo seemed to work yay.... still was at 4.1.2, think it was only a security update heh).
Anyway, I'd like to do a Factory Reset since the stock rom, after installing all the apps I thought I wanted, becomes so slow.
Curious if I can do it via SafeStrap->Wipe->Advanced Wipe for the Stock Rom Slot .... or should I do any safety things like remove SafeStrap or TempUnroot it via VooDoo then do it via the phone way of doing it (by pressing some buttons at once). I'd like to still keep root. Wasnt sure what best procedure is.
Probably will just have Google Maps and Spotify on there (Titanium Backup, VooDoo, and a few others) and never install the 100 'used only once/twice a year' apps on there currently.
Thanks for any advice,
Ari
Rant: My phone seems to always get so slow once install the cool apps I want... and I've tried all the cache-clearing solutions on the stock rom but never works. (not sure why, me and all my android friends seem to have these issues once install apps. None of these apps seem to be doing anything on boot/startup based on Memory/TaskKiller apps I use to look at current apps, so not sure what slows the phone down).
armyofda12mnkeys said:
Hey all,
I have a Razr Maxx (well until a few months from now when i can get a better phone).
It is rooted. and has SafeStrap (I used to use the other slots to try some 4.1.2 and 4.3 roms but they all had issues with the radio signal so just been using Stock rooted rom), and VooDoo OTA rootkeeper (Verizon updated my phone OTA the other day, VooDoo seemed to work yay.... still was at 4.1.2, think it was only a security update heh).
Anyway, I'd like to do a Factory Reset since the stock rom, after installing all the apps I thought I wanted, becomes so slow.
Curious if I can do it via SafeStrap->Wipe->Advanced Wipe for the Stock Rom Slot .... or should I do any safety things like remove SafeStrap or TempUnroot it via VooDoo then do it via the phone way of doing it (by pressing some buttons at once). I'd like to still keep root. Wasnt sure what best procedure is.
Probably will just have Google Maps and Spotify on there (Titanium Backup, VooDoo, and a few others) and never install the 100 'used only once/twice a year' apps on there currently.
Thanks for any advice,
Ari
Rant: My phone seems to always get so slow once install the cool apps I want... and I've tried all the cache-clearing solutions on the stock rom but never works. (not sure why, me and all my android friends seem to have these issues once install apps. None of these apps seem to be doing anything on boot/startup based on Memory/TaskKiller apps I use to look at current apps, so not sure what slows the phone down).
Click to expand...
Click to collapse
did it work out?
endofwed said:
did it work out?
Click to expand...
Click to collapse
Yeh it did work out. I think I just the regular button? combo to do a Hard Factory Reset.
I may have done the VooDoo Unroot and re-added it back in via VooDoo...
that or I may have had to re-root the phone though (think latter is what i did).
Either way I got root back.
The annoying thing is Verizon or Google? backed up which programs I had installed and it just reinstalled all of them immediately after a factory reset.... so it became mostly unusable again. Tried a few programs to figure out if its CPU or Memory and cant figure out why still slow.
armyofda12mnkeys said:
Hey all,
I have a Razr Maxx (well until a few months from now when i can get a better phone).
It is rooted. and has SafeStrap (I used to use the other slots to try some 4.1.2 and 4.3 roms but they all had issues with the radio signal so just been using Stock rooted rom), and VooDoo OTA rootkeeper (Verizon updated my phone OTA the other day, VooDoo seemed to work yay.... still was at 4.1.2, think it was only a security update heh).
Anyway, I'd like to do a Factory Reset since the stock rom, after installing all the apps I thought I wanted, becomes so slow.
Curious if I can do it via SafeStrap->Wipe->Advanced Wipe for the Stock Rom Slot .... or should I do any safety things like remove SafeStrap or TempUnroot it via VooDoo then do it via the phone way of doing it (by pressing some buttons at once). I'd like to still keep root. Wasnt sure what best procedure is.
Probably will just have Google Maps and Spotify on there (Titanium Backup, VooDoo, and a few others) and never install the 100 'used only once/twice a year' apps on there currently.
Thanks for any advice,
Ari
Rant: My phone seems to always get so slow once install the cool apps I want... and I've tried all the cache-clearing solutions on the stock rom but never works. (not sure why, me and all my android friends seem to have these issues once install apps. None of these apps seem to be doing anything on boot/startup based on Memory/TaskKiller apps I use to look at current apps, so not sure what slows the phone down).
Click to expand...
Click to collapse
armyofda12mnkeys said:
Yeh it did work out.
I may have done the VooDoo Unroot and re-added it back in via VooDoo...
that or I may have had to re-root the phone though (think latter is what i did).
Either way I got root back.
The annoying thing is Verizon or Google? backed up which programs I had installed and it just reinstalled all of them immediately after a factory reset.... so it became mostly unusable again. Tried a few programs to figure out if its CPU or Memory and cant figure out why still slow.
Click to expand...
Click to collapse
so you would advise against
SafeStrap->Wipe->Advanced Wipe for the Stock Rom Slot.
the reason why im asking is because I cant seem to load back into my stock rom, and i carelessly did not make a backup. I was thinking maybe a factory wipe on the stock would help.
armyofda12mnkeys said:
Hey all,
I have a Razr Maxx (well until a few months from now when i can get a better phone).
It is rooted. and has SafeStrap (I used to use the other slots to try some 4.1.2 and 4.3 roms but they all had issues with the radio signal so just been using Stock rooted rom), and VooDoo OTA rootkeeper (Verizon updated my phone OTA the other day, VooDoo seemed to work yay.... still was at 4.1.2, think it was only a security update heh).
Anyway, I'd like to do a Factory Reset since the stock rom, after installing all the apps I thought I wanted, becomes so slow.
Curious if I can do it via SafeStrap->Wipe->Advanced Wipe for the Stock Rom Slot .... or should I do any safety things like remove SafeStrap or TempUnroot it via VooDoo then do it via the phone way of doing it (by pressing some buttons at once). I'd like to still keep root. Wasnt sure what best procedure is.
Probably will just have Google Maps and Spotify on there (Titanium Backup, VooDoo, and a few others) and never install the 100 'used only once/twice a year' apps on there currently.
Thanks for any advice,
Ari
Rant: My phone seems to always get so slow once install the cool apps I want... and I've tried all the cache-clearing solutions on the stock rom but never works. (not sure why, me and all my android friends seem to have these issues once install apps. None of these apps seem to be doing anything on boot/startup based on Memory/TaskKiller apps I use to look at current apps, so not sure what slows the phone down).
Click to expand...
Click to collapse
When you try other rom you must download the cdma if u are in USA...the gsm don't work
for the stock slow rom try greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=it
and clean master https://play.google.com/store/apps/details?id=com.cleanmaster.mguard&hl=it
and when you do a factory reset and set google account uncheck backup or when play store start download,go in my app and stop the all the download
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1