Any ideas as to why my phone will randomly restarts when it's sitting idle after a fresh ROM install, full wipe, cache, dalvik, system?
I'm installing the latest MeanROM and latest Infected Eternity, same result.
I reinstall all my apps from previous ROMs from either myback up pro or the market
incarceration said:
Any ideas as to why my phone will randomly restarts when it's sitting idle after a fresh ROM install, full wipe, cache, dalvik, system?
I'm installing the latest MeanROM and latest Infected Eternity, same result.
I reinstall all my apps from previous ROMs from either myback up pro or the market
Click to expand...
Click to collapse
what hboot are you using? sounds like the rom isnt getting the permission it needs to install the boot systems and data partitions also are you unlocked if youre on hboot 1.5 or if you have atleast hboot 1,4 with s-off?rooted?
incarceration said:
Any ideas as to why my phone will randomly restarts when it's sitting idle after a fresh ROM install, full wipe, cache, dalvik, system?
I'm installing the latest MeanROM and latest Infected Eternity, same result.
I reinstall all my apps from previous ROMs from either myback up pro or the market
Click to expand...
Click to collapse
I also had this problem on my Replacement EVO 4G, which scored me a free upgrade to an EVO 3D lol. Is your phone Refurbished?
Are you restoring apps+data or just apps???
#Root-Hack_Mod*Always\
If your using an after market battery, take a look at my post :
http://forum.xda-developers.com/showthread.php?p=24126392
Sent from my PG86100 using Tapatalk
Thanks for replies!
Bit of background:
-This is a new phone (and by new, i've owned it since it was out of the original box), not a refurb.
-HBoot 1.4
-S-OFF
-When I mentioned restoring the apps from MyBackup Pro, It was only with APKs; but it also happened when I just had it redownload them all from Google Play. I did the restore method via MyBackup Pro as an attempt to see if it would help.
-Stock battery
The only thing I can think is it's an app that is just not sitting right with the ROM?
I'm using the Infected Eternity ROM now and it just will randomly restart when it sits there idle.
incarceration said:
The only thing I can think is it's an app that is just not sitting right with the ROM?
I'm using the Infected Eternity ROM now and it just will randomly restart when it sits there idle.
Click to expand...
Click to collapse
What software are you guys ? 2.17 or 2.08 ? I have seen a few folks have issues flashing 2.17 builds because they are still on 2.08 software and never updated to the latest...
When I look under "About phone" it says my software number is 2.17.
I've done the RADIO Only update, other than that I haven't done any other updates. I know there's the software update thread but I was hesitant to do it because I wasn't clear on what it was doing except for the RADIO ONLY update. I don't want to update my HBOOT to 1.5 lol
Bump? To the top!
Are you flashing a different kernel with your rom??? Also you should flash the aio that freezas or haux put up because I'm taking a guess here but I think your running a newer base Rom with out the updates and from what I've read that can cause some issues. Here's the hboot link that haux posted flash the one with out the hboot. I've personally flashed both of theese zips without issue. Also you should "IMO" not ever use Google to restore your apps or data. It has been know to cause system conflicts. I've never used mybackup so I can't comment on that but I'm sure its better than Google Lol I'd recommend using tb or tb pro. Also I'd recommend only backing up really important apps and just reinstalling the rest to avoid conflicts in the future. Hope this helps.
http://forum.xda-developers.com/showpost.php?p=21441428&postcount=403
Also after you flash that you should do this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
That should help with the issues. Hope it does.
#Root-Hack_Mod*Always\
The first link I get this: "Valid download request check failed.
Please click here and try your download again."
I just did this about 20minutes ago before reading your reply: http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Do you think that is the same thing and sufficient for what I may be missing that's causing it? Next I'll do an SD card wipe if it continues
Are you trying to download this from your phone ??? If so try a pc. Also i have the zip if you cant download it. However I just tried it and the link works. Remember download the non hboot zip. Also if your trying from your phone use the stock browser and open up the settings menu and uncheck mobile view to see if that will allow you to download the zip. Also the first link I posted is a more up to date zip than the one you flashed.
#Root-Hack_Mod*Always\
incarceration said:
When I look under "About phone" it says my software number is 2.17.
I've done the RADIO Only update, other than that I haven't done any other updates. I know there's the software update thread but I was hesitant to do it because I wasn't clear on what it was doing except for the RADIO ONLY update. I don't want to update my HBOOT to 1.5 lol
Click to expand...
Click to collapse
If you have s-off on 1.4 you can update to 1.5 without losing s-off. That's what i did, used htcdev method to unlock bootloader and retained s-off. I used revolution to get s-off originally.
And you probably need to flash all the 2.17 stuff i used a zip that had everything in it found here : http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Hope that helps
Updating with the update I linked seems to have worked!
Thanks guys for the help
Related
Hi guys, so yesterday I decided to take the plunge and unlock my evo 3d with htc's tool. It seemed to work as expected (s-on with unlocked banner). I was then able to flash cwm 4.0.1.4 and root using the su zip floating around on here.
My issue seems to be that aside from the nandroid backup I made all the roms I have tried break wifi giving the wifi error instead of on or off. I tried synergy rom, viper rom and viper rom with silverneedle. I also noticed when I was flashing in recovery it would say unable to mount sd-ext and it looked like under the settings> about phone> software information that the kernel had not changed.
I'm at a loss as to why, but I think it may be related to htc's unlock method, although I am fairly noob and may be totally wrong. Any help is appreciated.
Sent from my PG86100 using XDA App
Since you used the HTC method then you have the newest OTA updates and bootloader. Your banner should say S-OFF though if you had a typo above about that.
You cannot flash a new kernel yet with the new hboot. You need to stick with the stock one for now.
When flashing other ROMs are you doing a complete wipe first? If not, that might be your problem.
Go to the Development section. Many useful instructions and guides are there.
That's what I was afraid of, but that wasn't a typo. My bootloader says ****UNLOCKED**** with S-On. I was reading that this was what was to be expected with the htc unlock though.
Sent from my Shooter using XDA App
If it's still letting you use Super User and says you're rooted then it should be OK I guess. The main thing is when switching to a completely new ROM you should always do a full wipe - everything except sdcard.
There's a superwipe zip you can flash in recovery that will do all the necessary wipes for you.
I was wiping data/cache and dalvik cache. I'll take a look at the superwipe zip. I'm ok with stock rooted for now but it would be nice to use roms at some point.
Sent from my Shooter using XDA App
Yeah just wiping cache and dalvik isn't going to work. New ROM means backing up apps (if you want), then full wipe. That will wipe the system and data too (and I think android.secure and sd-ext).
Ok. Finally got everything to work. I used superwipe but I also had to use one of the synergy nightlies based on 2.3.4 to get my radios to work properly. Currently running synergy build 331 and it runs great. Thanks for the help
Sent from my PG86100 using XDA App
sceadwe said:
Ok. Finally got everything to work. I used superwipe but I also had to use one of the synergy nightlies based on 2.3.4 to get my radios to work properly. Currently running synergy build 331 and it runs great. Thanks for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I have the same problem:
wifi error
Kernel doesn't change
Also my Android version now shows 2.3.3
Can you please tell me how you got it fixed?
Sorry I'm a noob... Details would help. Thank you
if you upgraded to HBoot 1.5 and used HTC's unlocker you have to install a 2.3.4 ROM or the WiFi and possibly 4G radio will break. If you are interested in Synergy ROM try their RLS1 build or any build version 319 or newer
i cant post a url here cuz i am still a new user on the forums but go check out the official nightly folder linked in the following thread:
http://forum.xda-developers.com/showthread.php?t=1193948
I just flashed [ROM] (5/25) Nils' Business ICS 4.0.3 Sense 3.6 last night for my S-OFF ReZound. Everything went beautifully and the ROM looks great. The problem I think I have is whenever an app throws up a notification my phone reboots. I first noticed it whenever I sync'd my Google account and it threw up a notification about new gmail messages. So I stopped syncing Gmail. Then it happened whenever I tried to open Twitter/Facebook or when I adjusted the ringtone volume or my alarm went off.
Does anyone have an idea why these things would cause the phone to reboot? Are there any commonalities between these functions?
Weird. Not sure about that. The only rebooting I get on the ROM is when I use my Lock Screen App instead of using the power button. From what I understand though, that is a problem with ALL the ICS versions for Rezound. I can't wait until that is fixed...I hate trying to press that little power button through the small hole in the case I use.
Did you do a full wipe and then flash? Sounds like something residual from a previous ROM. If you did wipe and flash, did you restore anything in Titanium? It clearly states in the OP for that ROM not to do that.
yea i did a full wipe and flash twice. i havent installed or used Titanium to this point.
it first started happening when i attempted to sync my google account, which was about the 3rd thing i did after installing the ROM.
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're referring to the GB firmware patch, then I did do that during the ROM install process per the instructions. i can try doing that again though.
You are on gingerbread firmware correct?
I have read about the patch not working the first time so that could be the issue
Sent from my ADR6425LVW using Tapatalk 2
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
nalees said:
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
Click to expand...
Click to collapse
if you flashed the 3.14RUU, you shouldn't need the GB firmware patch since you are now on ICS.
I would reinstall the ROM and skip the patch.
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
nalees said:
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
Click to expand...
Click to collapse
When you went from gb and ran the ics ruu, did you run the ruu twice.? It only updates a few things the first time through. The second time it does all items on the list.
Sent from my Rezound
oh my, just read through Nil's instructions again and you're right, it does say to run it twice...
i only did the RUU once.
ok, so from here, I need to reflash the RUU one more time? and then reload Nil's ROM?
hmm, also noticed on step #10 i need to unlock the bootloader again? is this true even if i'm s-off?
I went from completely stock to S-OFF and running Nils' latest Business Sense 2 days ago. I have not had any of the problems you mentioned.
His instructions do no say to install the RUU twice. They say that it's a 2 pass affair to install it. If you went through the whole process to install it once, you don't need to do it again.
However, I agree with an earlier post. Installing a GB firmware patch after installing an ICS RUU is probably your problem. Re-doing the whole thing from Nils' instructions for "Latest Leak and Installation Instructions", and then just installing his v4.1 ROM is probably all you need to do to get straightened out.
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
nalees said:
hmm, also noticed on step #11 i need to unlock the bootloader again? is this true even if i'm s-off?
Click to expand...
Click to collapse
It says that in Step #10, I believe. And yes, you have to do that in order to install (or re-install, as the case may be) AR Recovery (Step #11).
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
con247 said:
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
Click to expand...
Click to collapse
I started on Monday with a bone stock Rezound. I unlocked, rooted, and did the wire trick for S-OFF.
Then I flashed the 3.14 RUU once, unlocked again, installed AR Recovery again, and then flashed Nils' v4.1 ROM (for S-OFF).
My phone seems to be working fine. Exchange mail (I don't use Gmail), contacts, calendar and tasks. Visual Voice Mail. Notifications. Text messaging. Facebook. WiFi Tether. Google Maps. Camera. Bluetooth handsfree. Everything seems to work fine. The only thing I haven't tested yet, that I mean to, is to force it to 3G only for data and test that I can talk and surf the Web at the same time.
Since I did not flash the RUU twice, what should I be looking for to not work right?
Do not HTC unlock after s-off.
Edit: saw you did.... Basically you will have unlocked or re locked. If you wanted the bootloader to appear stock you have to s-on and do the s-off process again. Then it would say locked. Not a big deal.... Unless you are paranoid and have to do a warranty swap.
Sent from my Rezound
ericsignals said:
Do not HTC unlock after s-off.
Sent from my Rezound
Click to expand...
Click to collapse
yea, i was reading this thread and that's why i thought that...
http://forum.xda-developers.com/showthread.php?t=1620211&page=6
i'll do some more reading before i proceed.
Just tested the SVDO.
Went into Phone Info and set my phone to CDMA Auto (PRL).
Turned off WiFi.
Confirmed status bar displayed 3G.
Called up my bank and let the automated menu thing talk over speakerphone.
Ran Speedtest on phone and it worked.
Went into Phone browser, did a Google search and got results.
Turned on WiFi Tether on my phone.
Connected my TouchPad (running ICS) to phone hotspot.
Ran Speedtest on TP. Got 1934kbps down and 1945kbps up.
I'd say simultaneous voice and 3G data work just fine with Nils' ROM, too...
so i redid everything tonight the proper way and its up and running perfectly! loving it
nalees said:
so i redid everything tonight the proper way and its up and running perfectly! loving it
Click to expand...
Click to collapse
And that releives me. Have fun
I need help badly.....I am using Evo 3d Gsm (Root,Unlock,S-off,Hboot 1.49.007) and this [ROM] CM 10 Gangnam Style. My 3g is not working if it is running for like 20 minutes even the 3g icon is still there. Also my phone some time getting very laggy and freeze...i have to lock the screen and turn it on to get this issue away....any1 can help me with this issue?? Many thanks....
hongsydney said:
I need help badly.....I am using Evo 3d Gsm (Root,Unlock,S-off,Hboot 1.49.007) and this [ROM] CM 10 Gangnam Style. My 3g is not working if it is running for like 20 minutes even the 3g icon is still there. Also my phone some time getting very laggy and freeze...i have to lock the screen and turn it on to get this issue away....any1 can help me with this issue?? Many thanks....
Click to expand...
Click to collapse
Data drops are a common issue on cm10 jb Roms, I would suggest using agrabren disarmed toaster version 67 , or helicopters 88 cm10 nightlies
Sent from my IdeaTabA2109A using Tapatalk HD
I'm using the same cm10 and it's ok.
Did you wipe all partitions first (except sd) and then install it?
Also you have to install the correct version of gapps. 20121011 i think it was. It's linked to from the op of the thread.
Also your touch screen issues with the Evo 3d could very likely be hardware related. I've had to have that fixed twice at the Sprint store. It's a known issue.
when rewinding video on IMDB says "can't play this video"
Thank mojo
mojomojo_man said:
I'm using the same cm10 and it's ok.
Did you wipe all partitions first (except sd) and then install it?
Also you have to install the correct version of gapps. 20121011 i think it was. It's linked to from the op of the thread.
Also your touch screen issues with the Evo 3d could very likely be hardware related. I've had to have that fixed twice at the Sprint store. It's a known issue.
Click to expand...
Click to collapse
Thank mojo for your reply....i did full wipe ( Wipe data/reset + Cach and davik + format partrition without sdcard) before install..About the laggy....it happens not only on my phone but on my friend phone that i try to install this rom on also...so i think this is not relating to hardware....i will try to reflash and choose the right Gapps to see if this fix the issue and report back..
No problem. Also you should be S-Off with any hboot except 1.58.
I did wire trick then flashed jbear 1.58 then downgraded to 1.50 jbear. Then did full wipe and flashed gangnam style cm10. My radio firmware was already up to date. Maybe you should first take the extra time to put it back to stock with ruu just to make sure your radios and everything are most recent? If you have the patience you could try to follow QADERSO (quick and dirty...) guide to returning to stock then doing root and s-off and jbear. Just add final step of downgrading to jbear 1.50 by downloading it to your sdcard and renaming it to PG86IMG.ZIP then going into bootloader once. Then you can wipe and install cm10. Also I use 4ext touch recovery and highly recommend it.
Doing all that should guarantee you are identical to me. There are still some issues with this ROM but not the serious ones you describe.
Problems I'm having are the camera resolution or ratio is weird (i get black bars above and below) and if i connect wifi with 4G on then the 4G goes into some kind of loop connecting then disconnecting then disable and enable adapter and repeat. CM10 power control in notification bar for 4g is kind of spotty too. I'll pay with it for a while longer before making a final decision but I think so far the pros outweigh the cons. I did find also that i was using tons more internal storage and ran out of space for my apps so i partitioned my sd card and have it a 3gb ext4 partition and installed Links2SD app and now have lots of space for apps. Maybe one of these days I'll write a guide for the whole process.
Found a bigger issue with this ROM and updating to today's release did not help. /data partition is filling up because wimax is running in debug mode or something. /data/wimax/logs directory is filling up quickly while wimax is on. I had 700mb from less than 24 hrs.
I cleaned them up manually but will need to schedule a batch job to delete it or figure out how to stop generating the logs...
mojomojo_man said:
Found a bigger issue with this ROM and updating to today's release did not help. /data partition is filling up because wimax is running in debug mode or something. /data/wimax/logs directory is filling up quickly while wimax is on. I had 700mb from less than 24 hrs.
I cleaned them up manually but will need to schedule a batch job to delete it or figure out how to stop generating the logs...
Click to expand...
Click to collapse
Known issue. Just "flash" the attached zip file from recovery which will delete/recreate that directory then mark it immutable so no more logs accumulate.
ramjet73
I had a couple of questions if anybody has had experience with such, first one...
Has anyone tried to use the Acid audio RLA5 sound mod and if so, I've heard that having a eq already in the ROM makes it
all goofy for install? Is this true and if so, has anyone else used this mod and what procedure did you do?
As for the second part, has anyone had any luck finding a full inverted gapps that everything will work? I thought I found one but it didn't have contacts inverted, then found another but it crashed google now. If anyone has had any luck could you drop me a link. ( all gapps including mms etc..)
On the 3rd part of the adventure of swapping out apks, I updated google ears via alert from playstore and it crashes something else.. LOL. Its just a never ending battle. But, through the day I found a piece here and there and now it all seems to be working and all inverted and that is after updating what play store wanted to.
Right now creating a flashable.zip that should work but not certain on the rules as to post. I already have a pre- written statement that announces that I take no credit in the creation and also name the Devs responsible and also will be linking their threads as well but not sure if that is enough. If anyone has any input that would be greatly appreciated.
Thanks,
Z.
thank Mojo
mojomojo_man said:
No problem. Also you should be S-Off with any hboot except 1.58.
I did wire trick then flashed jbear 1.58 then downgraded to 1.50 jbear. Then did full wipe and flashed gangnam style cm10. My radio firmware was already up to date. Maybe you should first take the extra time to put it back to stock with ruu just to make sure your radios and everything are most recent? If you have the patience you could try to follow QADERSO (quick and dirty...) guide to returning to stock then doing root and s-off and jbear. Just add final step of downgrading to jbear 1.50 by downloading it to your sdcard and renaming it to PG86IMG.ZIP then going into bootloader once. Then you can wipe and install cm10. Also I use 4ext touch recovery and highly recommend it.
Doing all that should guarantee you are identical to me. There are still some issues with this ROM but not the serious ones you describe.
Problems I'm having are the camera resolution or ratio is weird (i get black bars above and below) and if i connect wifi with 4G on then the 4G goes into some kind of loop connecting then disconnecting then disable and enable adapter and repeat. CM10 power control in notification bar for 4g is kind of spotty too. I'll pay with it for a while longer before making a final decision but I think so far the pros outweigh the cons. I did find also that i was using tons more internal storage and ran out of space for my apps so i partitioned my sd card and have it a 3gb ext4 partition and installed Links2SD app and now have lots of space for apps. Maybe one of these days I'll write a guide for the whole process.
Click to expand...
Click to collapse
thank Mojo again for a very clear instruction....I have a question:
1) Is it true that i get my radio update to version 11.77 (it is 10.xx at the moment) when i install this RUU file (RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe).
2)Will my Hboot change after this install??? and also my phone come back to S-on????
3)When i do this install with this file PG86IMG.zip from bootloader then it will get hboot change as far as i know right....???
IF my knowledge was correct, i will give it a try to install the RUU file to update my phone's radio back to 11.77 (it was 11.77 before i did the downgrade hboot to 1.49.007 from 1.53.xx) then install Gangnam Style rom to see if the 3g issue go away....
If i was wrong that when i install the RUU, my phone will be S-on again...im so lazy to try this because i will stick with Viper3d sense 4.1 then...
1 more thing mojo...i am using the latest disarm toaster rom (DisarmedToaster-0.2.9-67-shooteru)
ramjet73 said:
Known issue. Just "flash" the attached zip file from recovery which will delete/recreate that directory then mark it immutable so no more logs accumulate.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet. Actually I already switched to the AOKP release (Linaro build) which is very similar to the ROM mentioned in this topic and doesn't have the Wimax log issue but hopefully that zip is out there for others to find because I didn't see it in the dev thread for that ROM at least not at the time I mentioned it above anyway. There's a few small Q's I have about this AOKP ROM but I should start a new topic for those.
mojomojo_man said:
Thanks ramjet. Actually I already switched to the AOKP release (Linaro build) which is very similar to the ROM mentioned in this topic and doesn't have the Wimax log issue but hopefully that zip is out there for others to find because I didn't see it in the dev thread for that ROM at least not at the time I mentioned it above anyway. There's a few small Q's I have about this AOKP ROM but I should start a new topic for those.
Click to expand...
Click to collapse
If you are referring to mazda's AOKP ROM it does have the same problem with wimax logs accumulating and there is link to a post after the last question in the FAQ that has the same zip file I linked in this thread.
ramjet73
hongsydney said:
thank Mojo again for a very clear instruction....I have a question:
1) Is it true that i get my radio update to version 11.77 (it is 10.xx at the moment) when i install this RUU file (RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe).
2)Will my Hboot change after this install??? and also my phone come back to S-on????
3)When i do this install with this file PG86IMG.zip from bootloader then it will get hboot change as far as i know right....???
IF my knowledge was correct, i will give it a try to install the RUU file to update my phone's radio back to 11.77 (it was 11.77 before i did the downgrade hboot to 1.49.007 from 1.53.xx) then install Gangnam Style rom to see if the 3g issue go away....
If i was wrong that when i install the RUU, my phone will be S-on again...im so lazy to try this because i will stick with Viper3d sense 4.1 then...
1 more thing mojo...i am using the latest disarm toaster rom (DisarmedToaster-0.2.9-67-shooteru)
Click to expand...
Click to collapse
That RUU file is for Europe.... Are you in Europe? Is that a GSM phone? If so I'm afraid I can't advise about radio firmware versions. Firmware for radio is probably different for European users and the guide which I was referencing is Ramjet's guide found here: http://forum.xda-developers.com/showthread.php?t=1889438 but that guide is for Sprint or Virgin Mobile users (CDMA phones). Basically the guide is accurate I think for European user too but the RUU file should be different. Well, you should consult Ramjet on that as he wrote the guide and may know more. Also, you are correct that running the RUU will return the phone almost completely to stock. It replaces radio firmwares and HBOOT and will put you back to non-root. I just suggested it as a way to make sure you go completely back to stock and start from scratch so I can be sure you were on same versions of everything as me but if you are in Europe you cannot exactly follow it maybe. Anyway, I think you have explained all your issues though. By the sound of it you probably flashed USA (Sprint) radio firmware by accident when you downgraded your HBOOT. Next time you downgrade HBOOT you should make sure the file you are using is HBOOT only with NO radio firmwares in it.
So I think you have two options....
1.) To go back to stock using latest Europe RUU, root/S-OFF phone again (S-OFF might stay, I forget), put 4EXT back and then try to downgrade HBOOT to a compatible version again. This time you must downgrade without changing radios or if you can find a flashable zip with just your proper European 11.77 radios then you can flash just the radios back to 11.77 after downgrade. I don't know the version numbers for GSM phones for HBOOT or radios so I apologize if I am getting this wrong.
2.) Assuming your only problem is the 3g connection currently then maybe you can just find a flashable zip which will update only your radio firmware back to 11.77 without having to go completely back to stock. If everything else about the phone seems OK then this is definitely faster assuming you can find the right file.
Again, I know little about GSM phones and European radios so you may want to find a more knowledgeable person to help you. Definitely though if you flashed the wrong radios then you will lose your 3G connection! I have seen HBOOT's posted both with and without radio firmwares included so I think from now on you must be extra careful when flashing HBOOT to make sure you are not changing radios to USA radios and you should keep around a flashable zip with only your 11.77 radios in it so you can fix this as it may happen again.
Good luck!
If you read the developer's thread carefully you'll notice that he affirmed that data drops will occur.
ramjet73 said:
If you are referring to mazda's AOKP ROM it does have the same problem with wimax logs accumulating and there is link to a post after the last question in the FAQ that has the same zip file I linked in this thread.
ramjet73
Click to expand...
Click to collapse
Yes, Mazda's rom is the one I am using now. I wiped everything, then flashed 3.5 and then immediately did incremental to 3.5.2 then gapps of course and wiped dalvik and rebooted into rom. I checked and wimax logs were not accumulating like they had been. I just checked again and there are only some small "sequansd##.log" files in that directory but these files are tiny (about 9kb) each. I suppose it could become a problem after many months of use but when I was using the Gangnam Style CM10 rom mentioned in the title I filled the remainder of my /data partition in a single day with a ton of 500K files (forgot the name of the file) in addition to the sequansd files. So I guess these logs if not rotated could eventually become a problem but the severity of the issue is nowhere near on the same scale with a clean install Mazda's 3.5.2.
I just set the /data/wimax/logs folder permissions to 440 and deleted the sequansd log files so I think that will suffice? If not I'll flash the zip. I'm just being lazy.
BTW, thanks for your posts in Mazda's thread (using Power Toggles now and I love it) and your QADERSO guide. Both have been very helpful to me.
That ROM is known to have data drops on a mobile network. You can't do anything about it as the ROM is built that way. The only fix would be for the developer to fix it or for you to chanhe ROM.
Goodluck!
mojomojo_man said:
I just set the /data/wimax/logs folder permissions to 440 and deleted the sequansd log files so I think that will suffice? If not I'll flash the zip. I'm just being lazy.
Click to expand...
Click to collapse
Logs were still being written even when people changed permissions. The only way to stop the logs was to make the folder immutable. I flash the zip as part of my install.
mojomojo_man said:
That RUU file is for Europe.... Are you in Europe? Is that a GSM phone? If so I'm afraid I can't advise about radio firmware versions. Firmware for radio is probably different for European users and the guide which I was referencing is Ramjet's guide found here: http://forum.xda-developers.com/showthread.php?t=1889438 but that guide is for Sprint or Virgin Mobile users (CDMA phones). Basically the guide is accurate I think for European user too but the RUU file should be different. Well, you should consult Ramjet on that as he wrote the guide and may know more. Also, you are correct that running the RUU will return the phone almost completely to stock. It replaces radio firmwares and HBOOT and will put you back to non-root. I just suggested it as a way to make sure you go completely back to stock and start from scratch so I can be sure you were on same versions of everything as me but if you are in Europe you cannot exactly follow it maybe. Anyway, I think you have explained all your issues though. By the sound of it you probably flashed USA (Sprint) radio firmware by accident when you downgraded your HBOOT. Next time you downgrade HBOOT you should make sure the file you are using is HBOOT only with NO radio firmwares in it.
So I think you have two options....
1.) To go back to stock using latest Europe RUU, root/S-OFF phone again (S-OFF might stay, I forget), put 4EXT back and then try to downgrade HBOOT to a compatible version again. This time you must downgrade without changing radios or if you can find a flashable zip with just your proper European 11.77 radios then you can flash just the radios back to 11.77 after downgrade. I don't know the version numbers for GSM phones for HBOOT or radios so I apologize if I am getting this wrong.
2.) Assuming your only problem is the 3g connection currently then maybe you can just find a flashable zip which will update only your radio firmware back to 11.77 without having to go completely back to stock. If everything else about the phone seems OK then this is definitely faster assuming you can find the right file.
Again, I know little about GSM phones and European radios so you may want to find a more knowledgeable person to help you. Definitely though if you flashed the wrong radios then you will lose your 3G connection! I have seen HBOOT's posted both with and without radio firmwares included so I think from now on you must be extra careful when flashing HBOOT to make sure you are not changing radios to USA radios and you should keep around a flashable zip with only your 11.77 radios in it so you can fix this as it may happen again.
Good luck!
Click to expand...
Click to collapse
WOW.....i think i got the wrong Rom downgrading my Hboot to 1.49.007......My phone's radio was 11.77.3504.00U_11.25.3504.06 and Hboot=1.53.......After i tried to S-off and downgrade hboot to 1.49.007....my phone radio is 10.53.9020.00U_10.13.9020.08 at the moment and it is working fine with my rom Viper3d R310. Also i live in asia Vietnam......
Mojo....do you think i should get my radio back to 11.77 even my phone is working fine with this radio 10.53,??? i really dont know where can i look up the file for the radio only??/ and how to install it....anyone here can help me with the correct file for the radio???
Yup. You're right. Still accumulating. I'll flash the zip. Although it's probably just a debug setting somewhere that needs to be flipped off. Could be in kernel or in the module loading. Although I'm thinking in Linux terms. Not sure how much of that really translates to android and I'm not about to start mucking around compiling my own kernel.
mojomojo_man said:
Yup. You're right. Still accumulating. I'll flash the zip. Although it's probably just a debug setting somewhere that needs to be flipped off. Could be in kernel or in the module loading. Although I'm thinking in Linux terms. Not sure how much of that really translates to android and I'm not about to start mucking around compiling my own kernel.
Click to expand...
Click to collapse
This issue first surfaced in agrabren's disarmed toaster CM10 ROM and he didn't offer another solution, so I have to believe that any thing other than what has already been suggested would not be trivial.
ramjet73
I've been struggling with this for about a week and I am not able to figure this one out. I hope someone here can give me a hand.
I've unlocked my phone using HTCDEV and rooted using TWRP 2.4.3 gaining root and recovery access. All seemed to work well but every GOOGLE app crashes now on start up. I can't go to the market as it crashes "Unfortunately Google play store has stopped". It does this with all Gapps.
I've flashed the GAPPS through recovery since I can't access Play.Google. and it made no difference. I can't log in to Google accounts as soon as try it gives me "google account manager has stopped".
I've tried to RUU back to rom 3.16. but RUU fails to update the phone although the restoral screen shows the scrolling dots indicating it is updating, but it goes on forever. the bootloader shows "TAMPERED" "Unlocked" and this came after using FASTBOOT OEM LOCK command in an attempt to reflash the unit. I have tried to flash to other roms like CM10 but it only gets to the point of the spinning logo and just sits there and spins, etc. Other roms get stuck as well in the first boot up logo of the rom or give a black screen. I can use TWRP to restore the backup each time so the phone works seemingly ok except for anything with Gapps.
I assumed I can't not flash JB roms without S-off and I tried to use Dirty Racun to obtain S-off but I get errors with each step so gave up on that for now. I've resolved myself to sticking with the stock rooted rom but I can't do much without Google Voice which is my text and phone account.
Can anyone shed some light on this for me? I've searched the forums here and elsewhere for dozens of hours and have not been able to find a solution for this or any help that might help me "stumble" into a solution. I don't mind flashing another rom if I could get one to take hold just so I can get this unit working.
I think the TWRP recovery or a old verion of Superuser might have caused this glitch. I did the rooting and recovery using this guide here htcevohacks.com/htc-evo-4g-lte-root/how-to-root-htc-evo-4g-lte-unlock-bootloadertwrp-recovery and the provided TWRP would not accept any input so I replaced it with 2.4.3.0 and recovery then recovery seemed to work and backup/restore but still can't flash any roms successfully. I didn't notice Superuser v0.87 here as being old (my goof) and didn't get a more recent version until after the flashing was done. LIke I said, where I'm left at now is everything seems to work but anything having to do with Gapps just crashes on start.
Any help please?
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
thicklizard said:
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
dominicsdad said:
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
dominicsdad, I'm going to check out what was suggested about Mean Bean but I did try several JP type GB apps, etc. None of them would restore the function. THis has been so frustrating. I'm a guy that can folllow the posts and the guides I read, etc., but not having the core understanding or depth shows it's ugly face for a non-connected guy like me. WHy did you do an SD wipe? That's where I keep my backups which have been the only thing that has let me get back from a few botched rom attempts. I will try the goo manager if I can find a flashable version since I'm locked out otherwise with any kind of app install. I was surprised to see the EVO LTE didn't have a file manager as I was going to try and just install google voice which would at least allow me to use the phone.
THanks!
billaggie said:
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
Click to expand...
Click to collapse
Thicklizard,
Update, I installed Mean Bean and solved my problem. It gave me a scare thinking it would backfire with the 2 duplicate rom installs it requires but I had to put some faith in something working and it worked. Thank you for getting me on the right track!!!!!! Bill
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?