Related
I was running a stock ROM, rooted, with the original radios. All was operating properly.
Flashed the leaked radio update. Everything still okay.
Flashed Das BAMF 1.6. It boots up fine (and looks gorgeous, btw), but my SIM card is not recognized at all. Symptoms:
When making a call, I see text in the upper-right corner saying: "SIM Card not found. Please \n the phone."
Settings > Call > Voicemail Service... tapping on this dropdown results in "Voicemail number change unsuccessful. Please contact your carrier if this..."
I tried turning the phone off, booting it once without the SIM card, then rebooting with it back in place. That didn't help.
Out of frustration, I restored my tbolt to the backup I made before attempting das BAMF. Magically, my SIM card is recognized and everything back to normal. ...I tried das bamf one more time, only to have the same crappy results... FYI, I was sure to wipe data/cache/dalvik before flashing the rom in recovery.
HELP!
EDIT: I've also just noticed that despite this being das bamf 1.6 remix, I don't see the 4-in-1 restart menu, nor a 6-bar signal indicator. I'm absolutely positive that I downloaded 1.6 remix... Am I in the twilight zone?
did you wipe data before installing the ROM?
nevermind i missed it. i dont know then sorry.
try redownloading and check md5
I verified the md5 before flashing.
i actually received the same errors but it did not impede functions of the phone. My data has been dropping, but that is not because of the ROM, it has been doing it since the 4G outage.
EDIT: Actuallly my voicemail says:
"We have a problem
Your voicemail settings could not be loaded. Please try again."
Never seen that before.
The more I look into it, I'm missing things that are pictured in the 1.6 Remix screenshots... all of this has me very confused. I'm going back to the stock ROM until someone else finds and resolves the SIM card issue.
I am experiencing the same issues here. I see 'no Sim Card Detected' at the top, I have none of the Reboot Options, no 6 bar signal, etc.
Seems to be kind of a big issue and yet noone has really offered solutions. I have done the full wipe aswell.
Thank you for everyone's time involved with making such a Great ROM....Plus this Community of Users is awesome...Take that IPhone!
Did you happen to download 1.6.1 or 1.6.2 and install just those first? Those two are just patches that required 1.6 as a base.
So, you would have to flash 1.6, then 1.6.1 or 1.6.2 over it as a patch - you can't just flash 1.6.1 or 1.6.2 by themselves. With 1.6.3, I think they went back to a full rom release.
Install via cwr, not Rom manager.
Sent from my ADR6400L using XDA App
I had the same problem with the SD card running Bamf Remix. What solved it for me was formatting the SD card. Obviously backup the SD card on your computer first.
Download 1.6.3 and do a flash. It's a complete download too, id give that a go. I didn't run into any of those problems. Are you flashing through rom manager or cwm?
Sent from my ADR6400L using XDA App
Dont manually mount data. For some reason when i did that the same exact this happened to me. No 6 bar signal and no 4 in 1 reboot menu.
Sent from my ADR6400L using XDA App
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
I ended up wiping everything and installing 1.6.3 and that fixed everything. Thank You all Gentlemen for helping!
You guys are genius!
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Kodiax said:
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Click to expand...
Click to collapse
For the Call Recorder, it sounds like you're running a custom kernel. Most kernels don't support the things that Call Recorder needs. For the reboots, well, can't help you there.
mcore09 said:
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
Click to expand...
Click to collapse
Other than wiping twice (???), what you said you did should be standard procedure. Flashing via ROM Manager and Kernel Manager are no-no's unless you get lucky. In an ideal world, they work. And in many cases, they do work. However, in many cases, they cause nasty issues. For example, if you flash some kernels via Kernel Manager, the device drivers don't get flashed properly and you have some pretty nasty problems. And when you flash via ROM Manager, well, you learned what happens. From now on, only flash via CWM and CWM only.
Thank you for your responses. I am only using the 4.4.7 kernel. Which come s with dad band 1.6.3. I think that it is this new kernel (4.4.7). I never had these issues with 1.6.2.
Sent from my ADR6400L using XDA Premium App
Try down grading your kernel to a slightly older version.
Sent from my ADR6400L using XDA App
I reflashed my kernel to the same 4.4.7 but downloaded the kernel from his standalone post regarding kernels. My call rcorder is working now. Hasn't restarted since then either. Crossing my fingers ...
Sent from my ADR6400L using XDA Premium App
Well it restarted randomly while I had it connected to my Laptop and set to charge. I was in the middle of a Call with someone.
Very interesting why its Randomly rebooting. Could be the new radio. May be that why verizon held out on releasing it yet.
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance
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?