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
Related
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
mooter said:
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
Click to expand...
Click to collapse
logcat or it didnt happen.
task650 said:
logcat or it didnt happen.
Click to expand...
Click to collapse
I see some logs in the root folder, is that what you're referring to? I'll happily help you investigate if I can but it'll help if you point me in the right direction. Actually, maybe I'll try again and see how I get on? Restoring from backup was pain-free so not much to lose but 20 mins
Regardless, I very much look forward to seeing your work progress on this one over time! I know you're busy but superstars have obligations dude haha ;D
edit - trying again now with logcat reader installed - I'll report back!
do you have Ti backup installed? I would first try to see if there is some kind of phone apk in there. If there is try to clear the phone apk data and cache. If that doesnt work maybe try freezing it. Its strange that you have this error since tasks rom is a stock galaxy tab 10.1 ics build. Maybe try to wipe everything again and follow tasks instructions one more time step by step. sometimes weird things happen and a reflash might fix that. And just a stupid question but you have the wifi p7510 tab right
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
SimplyShane said:
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Click to expand...
Click to collapse
Twrp should be the recovery that is included with this ROM.
If you want a cwm recovery,, look at my thread in the general section.
Unjustdev said inject doesn't work.
For Google search:
I would try wiping dalvik cache and fixing permissions from recovery.
skepticmisfit said:
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
SimplyShane said:
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
Click to expand...
Click to collapse
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
skepticmisfit said:
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the info.
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?
Welcome to wilson3q's CM12 Unoffical Build!
As requested by some users, I started to build cm12 for I605. I don't own a I605, please help to test. If you like my work, you can donate here.
Disclaimer: I take no responsibility for bad things that happen as a result of flashing this.
My kernel source is standard cm12 kernel without any modifications.
SaberMod tool chain source is HERE.
All the rests are pretty standard cm12 stuffs, except a few patches I applied on top of them.
[Download]
ROM (please don't mirror):
build - 20150513
build - 20150602
Gapp:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Recommended launcher:
Nova Launcher (really like its JB zoom app animation, hate L slide up animation)
Recommended theme:
Deep Darkness
If you need enable soft buttons, flash this: View attachment softkeys.zip or soft+hardkeys.zip
[Flashing Guide]
1. Reboot to CWM/TWRP recovery
2. Flash ROM zip file
3. Flash Gapps
4. Reboot
* Wipe data first if you come from another rom *
* Newer boot loader, modem and recovery is highly recommended (don't use twrp 2.8.4, use 2.8.1 instead) *
* No other kernel will be supported, use the stock one, for your best experiences too *
[Patches]
My additional patches over cm12 includes:
Enhancements and bug fixes cherry-picked from other ROMs, including Slim LP, Nameless
SaberMod for ROM and kernel
O3, JustArchi optimization
Pthread enabled & strict aliasing
Latest sqlite db library
Added Boeffla sound engine 1.67
Added CPU governor zzmoove, smartassv2, savagedzen
Added io scheduler row, bfq, zen, vr
Disabled some useless Samsung processes
Fixed GPS
Fixed low in call volume
Video playback forward/backward fix
Removed all kernel debuging stuffs
Fixed keyboard not showing up during setup wizard
Fixed a crash of music app
Changed DPI to 280
Fixed Camera issue
Fixed Day Dream
Fixed Netflix streaming (one more reboot needed after installation of Netflix)
Enabled Multi-user
LMK minfree tweaks
Misc tweaks
more...
For better experience, change Nova animation/scroll speed to Fast...
[Known Bugs]
I am not sure what issues you will get, but one thing is for sure: YOUR PHONE WILL FLY!
chrome glitch: type chrome://flags as URL and disable GPU thank @bigmarv31)
Thank cm team for the amazing ROM.
Thank sabermod for the amazing toolchain.
Special thanks to: @DerTeufel1980, @sbrissen, @rogersb11, @TheBr0ken, @DreamFX, @frankie...
[Screenshots]
Always nice to see a new thread for i605. This doesn't happen often. Thank you!
Thanks again for building this for us we all appreciate it!
will be testing this out and see how it spars. thanks for this! I was going to try and "port" it over from the t0lte with replacing some libs and such, lol.
Thank you! I'm downloading right now. Looking like a slow day at work, so why not?
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
UPDATE
thefinancemaster said:
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
Click to expand...
Click to collapse
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
thefinancemaster said:
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
Click to expand...
Click to collapse
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
baseband unknown no data
bigmarv31 said:
baseband unknown no data
Click to expand...
Click to collapse
Will fix this today.
Keep a close look.
wilson3q said:
Will fix this today.
Keep a close look.
Click to expand...
Click to collapse
Yes Sir Thanks
New build online...
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
LvnInOC said:
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
Click to expand...
Click to collapse
Can you get a logcat?
I guess my proprietary blobs are not correct...
wilson3q said:
Can you get a logcat?
I guess my proprietary blobs are not correct...
Click to expand...
Click to collapse
I already went back to Liquid but I dont mind doing another try at it especially if it would benefit. let me get ir flashed and try to get you the Logcat
. give me a few
---------- Post added at 05:38 AM ---------- Previous post was at 05:10 AM ----------
ok so I got this flashed again strange this time after booting it said no sim card inserted and to insert my sim, it was not out and i skipped and moved to wifi , setup worked all the way and I got a log cat, hope I did it correct as this is new to me. I have to re-flash to Liquid for now so that I have a working phone as I go to work in an hour,
Again let me know if you need any more details
Same on this build baseband unknown so no data
wilson3q said:
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
Click to expand...
Click to collapse
Yes, I flashed the gapps from your post. gapps-lp-20141109 is what the file name was. I use TWRP, not sure if it's the latest but it works fine. I always do the "factory reset" wipe option in twrp, because I believe that's a full wipe with one swipe... Now, just to test it out and see if I was doing something wrong, I tried the Liquid Smooth build (latest nightly) from 1/7, and it loaded and booted just fine. Had to flash the ROM, Gapps, GPS Fix, and Super SU (so I can restore my apps in Titanium). It connected to data, and ran me through the setup in a flash. It's working well enough to be a daily driver. Do you have any other suggestions? I'm willing to help if you want me to try something else.
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
glockman4519 said:
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
You're like me you change roms by the hour.
DreamFX said:
You're like me you change roms by the hour.
Click to expand...
Click to collapse
I love to flash and then go through a process of testing. I actually got 2 gt-n5110s so I could test a couple builds at same time, kind of a back to back comparison.
I would love to pick up another i650 that still has unlocked bootloader for testing that way on this device as well.
Well back to this rom, I couldn't get past the getting data screen and had to abort. I did a clean flash and wiped everything with both philz and TWRP 2.8.3.0. I tried both stock and shift kernels.
Lets face it, I'm a flashaholic. lol.....
"Chances Favors the Prepared"
I have a Samsung G900T1 with rooted stock 6.0.1. This problem has been going on for 2 months or longer. My apps are set to auto-update without notifying me, over any connection. So I was unaware exactly when this problem started.
App updates barely crawl, then ending up stuck at 100% downloaded after taking an incredibly long time to complete (as long as several minutes). I know that new installs sometimes fail.
What I've done:
- Selectively disabled wifi, to force T-Mobile data for updates
- Cleaned every way I can do, used Trimmer app, stopped using more than one "kernal editor"
- Performed nandroid backup then factory reset and restored
Nothing seems to help.
Initially, I also erased all media files and unused apps. At this point I have 70 apps pending update. If I want to install a new app I first have to halt the update process to deprioritize those, then attempt install, which behaves as stated above.
I'm thinking the problem likely resulted from installing a couple of "App 2 SD" programs, attempting to open up primary storage. I'm guessing I tinkered too much. For a time I directed downloads to the SD card, but the performance degraded. I used the specified "backout" then uninstalled the app2sd apps. I had hoped the phone would return from crippled to slow, but now I have both.
Any detailed suggestions and all on-point questions appreciated.
Odin back to stock rom ... re root then reflash twrp then flash your custom rom.
Remember, if you are on 6.01 then you need to flash stock 6.01 you cannot flash a previous older rom
~~~oka1
Thank you for the suggestion. I am using stock rom (rooted + TWRP) and followed a longer path to fix the issue. Unfortunately, I now don't remember the exact steps, but I believe the source of those steps was not on XDA. I realize not much help, but I wanted a process less risky than factory reset or rom reinstall (risky when I do them, not necessarily in general). I assume not a big issue here at XDA since I just researched and found only one other direct question on the topic that was never stated as resolved. I would expect your method to work, and appreciate your help.