Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
lilhaiti said:
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
Click to expand...
Click to collapse
You flash anything or change anything with a2sd etc, before this started happening?
It's not doing it on an older NANDROID (from 4/22).
I flashed Drowning 7-6 ad then noticed it. But since my last restart before that, I've installed a lot of stuff. I will try it for a while on this NANDROID and see if it does it again after updating my apps, too many changes to rebuild from here...
Basically what happened was I flashed the Kernel (7-6) and restarted, things were fine...but then (per Drownings advice) I restarted again, and then all hell broke loose. I recovered my last NANDROID but experienced the same thing with just a restart, so now I am on an earlier NANDROID and tried a restart and all went well..Like I said I will try to update my apps when I get home (damn ATT data caps) and see what happens then...
OK...several restarts after installing updates, and everything seems normal it's definitely got something to do with either drowning 7-5 or 7-6, or n75 and/or n76.
Right now with the NANDROID I am running n42 with drowning 7 with aufs enabled (as was with the newer ROMS)
I also run DT A2SD with apps and dalvic on SD.
I will try to upgrade to n76 and drowning 7-7 in a few and see how that works out...
n76 and Drowning 7-7 has been good so far...I think the problem is solved...there was definitely something wrong with my setup that was common to the later NANDROID...thank god I saved some NANDROIDS
Wasn't there some kind of known issue with 7.6? I don't remember the details, but I seem to recall that there was some reason why I didn't flash it at the time (aside from general laziness).
Did a fresh install of n76 with S2E and Drowning 7-7, all is running smooth again and I have restarted a dozen times with no issue. After flashing over top of ROM's for the last few months there was probably some trash getting in the way, so I decided to clean house.
for some reason every rom I flash works great until I Install my apps. Now I use Titanium for my backup and installation of all my apps . Ive ran a scan in my app data and everything is clean. Ive even gone so far as to manually download every app I have from the market one by one . But every time I finally get everything set up and customized the way I want my phone start rebooting every 5 min.it reboots and loads everything fine and once i start using my phone my soft keys stop working but my screens touch works fine I can scroll click on things etc . thats when I know its going to reboot.then it starts every five minutes... now Ive used Cyanogen 9,Mikrom,Viper,Synergy and every one does this. Of course I do a complete wipe of all my data ,cache and partitions etc before I flash Every rom but nothing helps. Ive gone through the process of factory resets and wiping everything at least 10 times with each rom. Upon my days and hours apon hours of research the only suggestions I found was the possibility of a corrupted partition, and to re-install the ruu to completely clean all partitions and set everything back to original then try again . so I did , then I rerooted and and flashed a rom. with the same results. i know its either something Im doing or not doing thats causing this because to have his happen with every rom I flash isnt just the rom. now ..when Im on my stock rom I dont have this issue . so I know Its not a hardware issue. its just when I flash a new rom.
and another thing I noticed is after a couple random reboots it takes a while to connect to my 3g and turn my signal on. in fact sometimes it wont automatically connect until i open my connection in settings. I dont have to click on connect or anything ,all i have to do is basically open my settings or my quick toggles in my navigation bar.
and on a side note. well maybe its a side note maybe might be the actual cause of the problem haha.. when i do a factory reset through recovery everything works fine but i get an error [E: format_volume: make_extf4fs failed on /dev/block/mmcblk1p2] but everything finishes and resets fine as far as I know ... but could this be whats causing these reboots? when i look through my file explorer I find all of the mmcblk files but it seems that this file is the only one not there. can I fix this ?
Evo3d cdma rooted s-off hboot 1.4 revolutionary
Your "side note" might just be your problem. Have you tried a factory reset with another recovery, or maybe redownload and flash the same recovery.
Also, are you restoring data for system apps with titanium backup?
Are you flashing the correct hboot for the Rom you're installing?
Wikd said:
Your "side note" might just be your problem. Have you tried a factory reset with another recovery, or maybe redownload and flash the same recovery.
Also, are you restoring data for system apps with titanium backup?
Are you flashing the correct hboot for the Rom you're installing?
Click to expand...
Click to collapse
I redownloaded and installed the same recovery when I unrooted and rerooted ...is there another recovery you suggest trying ? I used the recovery that came with the revolutionary.zip
No I'm just restoring user apps from the market and 3rd party downloaders (4shared etc.)
And as far as the h.boot. when i was downgrading my h.boot to 1.4 ,after I downgraded my bootloader said 1.4 but I couldn't root through revolutionary . And I found that I needed to downgrade my software from 2.18.... In order for me to be truly at 1.4 hboot and run revolutionary. So I did and it worked perfectly . So now my software is 1.13.651.7. To be honest I wasn't sure if me upgrading to a newer software and running a newer RUU (not an ota ,just higher than 1.13...if it would cause any problems with my root as far as upgrading my h.boot to one that doesn't work with revolutionary as I had that issue with trying to root originaly.
Sent from my PG86100 using xda app-developers app
So I think its something to do with me moving my apps to sd. I only move my user apps and use titanium to do so. Now I have all my apps restored from titanium but didn't move any to sd and I havent had any reboots ...my internal memory is kind of low but its not lagging ... But I can't put any of my games on because they are big on memory . And I'm already low . Does anybody know what's causing my reboots when I move my apps to sd ? Would creating a partition on my sd card fix this ?
Oh and I used a different recovery to do my full wipe ( team wins recovery ) and it didn't give me the error I was getting before . Which is good .but I still got my random reboots .. but I noticed I only get them when I move all my user apps to sd . ( besides my lwps , widgets, system apps and things like setcpu etc.)
Sent from my PG86100 using xda app-developers app
My pocket felt hot, so I pulled out my phone and saw that it kept rebooting itself. It just shows the initial Samsung splash for maybe a second or two, then loops again. I can get into Recovery and Download modes fine. I tried wiping the cache, factory reset, restoring a cwm backup. No luck so far. I've been using the CM9 rom for months. I haven't flashed or changed anything in months, I haven't even installed new apps in a while. Before this happened, it said I had no signal, so I had to restore my EFS(which I've had to do several times since I got the phone, mostly when I was switching back and forth from CM9 and stock to see which I prefer). After going into and out of airplane mode to reset the antenna, the signal and all worked fine. I let the phone cool down to make sure it wasn't just rebooting due to heat, but that didn't change anything. I've been searching here and google for anyone else with an identical issue, but I've failed so far. Everyone else seems to get to the home screen or just having random reboots during use.
Just to clarify, my question is: How can I fix my phone? Is there any other information I can give that would help?
I have the international i9300. I also tried removing the SD card and SIM card, since one thread concerning a different kind of rebooting issue reported success with that. Nope.
Try to reflash a stock rom on Odin
Is that different from restoring the original rom with CWM? I did that already. I don't have or know how to use Odin, but I'll download it and figure it out if that's the next step.
Solution?
Ok, I never didn't have to figure out Odin. I fixed it by wiping dalvik, factory resetting, restoring the stock rom, wiping it all again, rebooting into stock(it worked), then restoring back to the backup I made after the crash. Some of these steps might not be crucial, but at worst you waste a few minutes to make sure it works right again. Hopefully it'll help others with similar problems.
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?