[B]droid bionic ota ics not getting notifications, hanging badly slowly deterorating . i am willing and wanting to root or reset safely please help traveling for Christmas and need it to work please[/B]
I am having the same issue. The first time it happened, I lost all audio - music, ringtones, phone calls had no sound from me nor from the other party. Phone was extremely laggy and would freeze up then eventually reboot. I was lucky if I could get 5 minutes of use. Sometimes it would happen immediately after reboot. I did a FDR after ICS update and installed all my apps fresh. Many apps "unfortunately, stop" and I cannot get them to work without another uninstall/reinstall. Fortunately, I had a nandroid backup right after the fdr and reinstallation of all my apps. Restoring back to that point has helped tremendously with everything but the audio issue. My music audio still goes out every day or two, but, can be fixed with a reboot now.
Not sure, but it sounds like the hardware is at fault. If an FXZ won't fix it than, I am sorry to say, your phone's dying and no amount of software will fix it.
Just remember, only the ICS specific FXZ file will work for an ICS phone. Any others will be disastrous.
reflash reflash reflash. fxz i always start from scratch, why beat around the bush
I tried to fxz back to stock using HOB in order to upgrade to ics and it kept failing on the final reboot. I was finally able to update by installing the update from .zip file in recovery mode. I read the HOB instructions numerous times before and after and if I was doing something wrong, I cannot determine what it could have been. There is another thread of someone having the same issue after fxz'ing successfully with other devices, so, sounds like some devices may be problematic.
If an audio driver was corrupted. Would a FDR followed by restoring a nandroid backup potentially fix the problem, or, would the corrupted driver be in the backup file?
Well I bit the bullet and did a nandroid backup, then performed a FDR, then restored the backup (yes, the one I was using while having issues). I have had no sound hangs (used to be daily) or any other issues for 4 days now. Also, battery life seems significantly better, especially when idle. My battery was draining like crazy before. Might be worth a try and you have nothing to lose but a few minutes of your time. I didn't do fxz because I couldn't get my phone to fxz successfully when I wanted to do the ics update.
Related
I have not received a text for about 3 days. It started when my sister asked why I hadn't responded to hers. I figured it was just a hiccup on the network. I was able to send her a text fine and make and receive calls fine, but no texts come in. I'm running on CM6.1 and hadn't had any problems with it. I tried uninstalling recent applications, and I even did a factory wipe and re-install of my ROM and mods, as well as all of my apps and I'm still not having any luck. I haven't yet called Sprint, as I'm afraid that they won't know anything or will give me grief for using a non-stock software (perhaps they won't even know); or maybe I'll just stop into the store sometime soon.
Anyway, I've read a few things about this, such as people removing apps and it alleviating the problem. I figured it was just a space issue, like once the phone dips under a certain amount of on-board storage it doesn't download them. I had a similar problem where it wouldn't sync e-mails until I got 2.2 firmware and did App2SD. But my storage isn't really low enough for that to make sense. I tried re-installing the radio that I use to no avail... I just really can't figure this out.
If anyone could give me a leg up on this problem, I'd be really grateful.
Thanks,
Mike
What rom are you running? Is your prl up to date? Current is 60674. Nand, flash a Sense rom, send and receive a few texts, update your profile and prl, then nand restore back to your rom. People have had success with that.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
I'm running the latest Cyanogenmod that is listed for my phone, which is 6.1.0, released about 2 weeks before I started experiencing the problem. I have the PRL file and have it on my SD card. Is there any way to do this without flashing to a different ROM?
I had the same problem. Downloaded Fresh ROM. Did a nandroid, flashed Fresh, updated prl, opened maps for a good GPS lock for safe measure, then just restored my nandroid of Cyanogen. Worked flawlessly, and took 20 minutes. Definately the best fix, and the nandroid restores everything to to the way it was, so it's no headache at all.
I'm downloading the stock RUU and I have Fresh downloaded. Nandroid keeps getting stuck on data... about to just go for it.
Don't flash the stock RUU or you'll have to re root.
Well that's not too hard. But what sucks is when Fresh Sense keeps crashing... then when you go to restore, you get an MD5 mismatch... Yeah, it won't restore my backup because it didn't complete and got stuck. Looks like I'm wiping and re-flashing CM6.... again.
Well, somehow I had a working backup from yesterday, the 24th, at some point. It won't be exactly where I left it... but it'll be close. Hopefully I got all the updates I needed via Fresh. Fingers crossed.
The way I got it to work was to flash a Sense ROM. As soon as the ROM loaded, all the texts came in. Also while on Sense, update your PRL.
Sent from my HERO200 using XDA App
i used this shipped rom when i got my n1 6 months ago,
Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
i received all the updates, it was working fine.
the other day, i decided to use the same passimg.zip file,
when phone read the sd card, i accidently selected recovery, it started to do recovery process, middle off the process i freaked out because that was not i wanted to do so i turned off the phone and install passimg.zip
i install all the programs i use and received all the updates,
now n1 sound level goes very low even it shows sound level is max,
its impossible to hear when it rings or playing music.
when i turn off and on the phone i get the sound back, after some time sound level goes very very low even sound level in max. so i turn off and on again and i get sond back,
i dont have any problem during calls i can hear,
right now
version 2.3.6
build number GRK39F
how can i fix this?
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
i downloaded same passimg file and installed it to my nexus one, same proprem continuous.
when i turn off and on, everthing normal.
any ideas?
Dude Random21 said:
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
Click to expand...
Click to collapse
"full wipe" means, using passimg file and install it again?
Full wipe means to do a factory reset, usually from recovery.
i figured it out. i dont know why but the problem was a program called voipraider,
i uninstalled it, problem solved, thanks for your replies...
Ok well I'm glad you got it resolved
I have this same problem. I don't have the app mentioned above installed, so I'm hoping someone can chime in with another app that may cause this issue? I've done a full factory reset, reinstalled everything (MIUI rom.) Rebooting the phone doesn't always fix the problem.. sometimes rebooting a few times will bring the sound back to normal, yet randomly all sound on the phone is barely audible at max settings. If a normal reboot doesn't work, normally wiping dalvik will fix it. Would this mean the problem lies in one of my apps somewhere? Any advice?
Are you using DarkTremor's a2sd? If so, it is a well-known problem. And wiping dalvik or just the regular cache will reset it. Due to this reason (and a few other minor ones), I switched to S2E for my app2sdext purposes, but I am not sure how well it works with MIUI (it was designed to work with CM7).
@bassmadrigal
Thanks. As I think about it, DTs a2sd is the only common thing I had in my testing. Even switching between ROMs, I kept flashing DT. Since I always have issues with MIUI's stock A2SD (based of DT).. I went back to CM7. I looked into S2E and will take that route.
I hope this fixes it.. the sound was frustrating when my alarm is going off in the AM and it's not making a peep. I'll post back in a few days in hopes that it's ceased to be a problem.
Thanks again for hopefully solving my major nuisance.
Hello all,
I've been running Eclipse 2.2 on 902 for some time and I've stubbornly refused to switch away from using bootstrap for all my backup needs, however, after reading enough about it I decided to give safestrap a try. I've had a little trouble with the process however and was looking for a little clarity...
My understanding with safestrap was that in addition to giving me a safe (technically unsafe) 2nd partition/access to recovery in case I messed something up, that it would also pretty easily transfer data, apps, etc from one partition to the next, making flashing roms (and I thought updating) much easier and quicker without needing to backup individual portions of my system, Is this correct or am I mistaken?
Onward to what I did (my goal is to update to 905 and install eclipse 3.0) - Installed safestrap, backed up safe and unsafe side. I then went to unsafe and used bootstrap to restore to IMMEDIATELY after I applied the 902 update (had backed it up previously). This backup was literally a stock Bionic which I had updated from 886 all the way to 902, rooted, then installed bootstrap to backup. I then updated this to 905 with no issue, and of course backed it up... From here, my understanding was that I could simply swap over to safe side, then install the eclipse 3.0 through finding a zip in recovery - Recovery would not do this for me. It gave me an error similar to "cannot apply eclipse3.0.zip (bad)"
I tried to push the ROM both without making any changes (just switching from unsafe to safe and immediately trying to apply the zip) and when that didn't work I wiped data, formatted system, and wiped cache/dalvik and got the same error. (the net result through all of this was making my safe side non-responsive, and me ending up restoring safe side system to the initial backup I had made about 30 minutes prior).
Is this working as intended? Should I look at safestrap as purely an extra failsafe to keep me from bricking my phone and not an easier method to flash/update? If I have to expect that I need to go to safe, follow the same path to apply the update as I did on unsafe, then flash 3.0 and restore with titaniumbackup, sms/call log backup, etc, I will, but I just wanted to make sure I'm not misunderstanding something with safestrap that may allow me to make this whole process easier - I'd be much more interested in trying out a variety of ROMs if the restoring of my data wasn't such a hassle when I did it.
Sorry for the long post - I'm long winded and also wanted to get all of the information out there for anyone who may answer.
Thanks in advance!
-Jamie
Guess I was too wordy and nobody wants to read it (or posted in the wrong spot maybe) -
tldr:
Is there a way to use safestrap as having a way to easily transfer data etc from one rom/update to the next? or should I be using it solely to have an extra backup to prevent me from bricking my phone, and just do the longer more arduous methods of restoring data and settings after a rom swap/update?
I'm no expert but I have successfully used Safestrap, installed eclipse 3.0 as well as tried other roms and themes, and have other Android experience as well. Sounded like you may have used bootstrap and Safestrap at the same time. Am I wrong? If not, from my understanding that is a no no. Uninstall bootstrap completely and use Safestrap only. I also upgraded my "unsafe" system to .905 via OTA before attempting 3.0. My first experience with Safestrap, however, was not entirely positive either. I think my download was corrupt because it stopped working correctly. I downloaded again and haven't had any problems since. I followed this guide http://forum.xda-developers.com/showthread.php?t=1455888 and it worked. He's not really all that clear at times. It's also not necessary to factory reset after flashing a new rom. Always do it, but it can be done before too. I always do it before and have no problems. Also if you decide to apply a theme make sure you boot up the new ROM before flashing the theme. This guide was not entirely clear on that and it got stuck in a wicked boot loop that ended with me on stock and Safestrap gone. Keep trying. Hope some of this helped. I'm wordy too
Sent from my Galaxy Nexus using xda app-developers app
Btw, to answer your first question, the best way I've found to transfer user apps from ROM to ROM is with titanium backup. Other data will still be on your sd cards and accessible to the new ROM. I never use titanium to restore system settings and most system apps though. Things tend to get messed up if you try to do this from one rom to another. System apps can be converted to user apps with titanium which is cool then backed up and restored to new ROM. And never restore Google play app with titanium. Some go so far as to say don't restore apps with data but I haven't had any trouble except with core google apps like play, gmail, voice. Usually flash gapps if I have to and restore other core Google apps directly from play store. Sometimes titanium "hangs" on some apps. Not to much trouble with it lately maybe it's fixed used to be a PIA though.Sorry there's still plenty of setup involved any time you want to "dial in" a new ROM.
Sent from my Galaxy Nexus using xda app-developers app
Thanks G-diddy,
To clarify, I knew bootstrap and safestrap didn't play well together. That being said, I did NOT use safestrap to try and restore to a bootstrap backup. I installed safestrap, then swapped to my UNSAFE side, then restored to a previous bootstrap backup (using bootstrap), then OTAd to .905. I then backed up this fresh near stock but rooted .905 with safestrap (thus should never have to use bootstrap ever again). I then tried to swap over to safe and push eclipse 3.0 but had no success... At present my phone has near stock but rooted .905 on my unsafe side, and the same .902 with 2.2 eclipse on my safe side that I've been running for months...
I guess I have no choice but to restore my present safe side to the old bootstrap backup, then manually ota, then install the rom, I just thought that Safestrap would make all of this process easier - in as much as since my unsafe side is successfully updated, I was hoping my safe side would be too, making the process somewhat simpler. Sounds like I'm wrong in this assumption though, unless someone else can say otherwise?
Thanks for the tip on Titanium Backup too, although I've been using the premium version of that for months now, ever since I decided I was going to turn my phone into a toy
Like the title says, I decided to try a full mf9 flash, root, recovery then hotspot flash. Before the extras, I did a full factory reset. I did move everything over to the SD card before and run titanium and backup within apps and nandroid before wiping everything. Like someone said earlier, they thought it was better to do a full flash than do an earlier one and update to it. Granted it's almost 5am and network traffic is probably at a minimum but I'm getting excellent performance so far. The true test will be in the afternoon when the network is busy.
oscarthegrouch said:
Like the title says, I decided to try a full mf9 flash, root, recovery then hotspot flash. Before the extras, I did a full factory reset. I did move everything over to the SD card before and run titanium and backup within apps and nandroid before wiping everything. Like someone said earlier, they thought it was better to do a full flash than do an earlier one and update to it. Granted it's almost 5am and network traffic is probably at a minimum but I'm getting excellent performance so far. The true test will be in the afternoon when the network is busy.
Click to expand...
Click to collapse
I have noticed marked improvements as well too. I did a full wipe and a clean install. Seems like the 4G is able to connect a lot better. Not having as many dropped calls either with the mf9 update. Took a couple try's to get root to stick, but that has something to do with Sprint attempting to keep the phone locked...
So far, the phone feels a little more responsive, with less lag. I don't know if it is a placebo effect, but things seem better, so far, when doing a full install than going the upgrade route. I just about have everything, settings wise, set to the way I like it and have all the programs installed I had previously on the upgrade install. I just restored titanium backups of the majority of the apps+data so putting everything back was much easier than downloading everything over again from play.
If you're bored, like stock mf9, but went the upgrade zip way, backup everything and try the full PC Odin flash. Maybe you'll like it.
oscarthegrouch said:
So far, the phone feels a little more responsive, with less lag. I don't know if it is a placebo effect, but things seem better, so far, when doing a full install than going the upgrade route. I just about have everything, settings wise, set to the way I like it and have all the programs installed I had previously on the upgrade install. I just restored titanium backups of the majority of the apps+data so putting everything back was much easier than downloading everything over again from play.
If you're bored, like stock mf9, but went the upgrade zip way, backup everything and try the full PC Odin flash. Maybe you'll like it.
Click to expand...
Click to collapse
It's not placebo, it's real. . My MF9 experience after starting fresh has been markedly better.
I'm guilty of doing this every time I flash a new rom. I don't know, but I fear the dirty flashes lol. Bricking isn't even a problem. I guess I like to do it right the first time & have a lesser chance of running into any issues or user errors. With mf9, it's just another routine maintenance for my S4
Had trouble flashing with CWM, had to use Odin.
Sent from my SPH-L720 using xda premium
I don't know if I'm missing some vital step but I've successfully bricked my phone consistently when manually updating my CM12.1 nightly.
I try to update to the latest nightly once a week, and for the past couple weeks it ends up bricking the device, causing me to go through unbricking procedure and return to stock, then root and all that other fun ****. That being said I have the whole unbricking down to a science, but that doesn't change the fact that it is getting more and more annoying each and every time I have to do this.
It's not that the ROM I'm flashing is bad, It works perfectly fine if I do a clean flash, but when it comes down to updating it completely ****s the phone. To make it worse, thanks to my phones locked bootloader my recovery method is using safestrap, which of course gets wiped when the phone fails the update, leaving me with fastboot as my lord and savior.
I simply don't understand the issue, I'm willing to adapt to doing a clean flash every time I have to update, but I'd at the very least like to know why the hell it does this, to me it makes little to no sense.
I'm using a stock kernel, and no weird init.d scripts that could cause it to boot funny.
On another note, slightly irrelevant, but if someone could tell me how (if possible at all) I could skip the foreplay of flashing back to stock and just flash a ROM through fastboot, it'd be greatly appreciated.
Are you using some kind of built-in update mechanism in CM 12.1 or just flashing the updates through safestrap? If it is the former, maybe it is messing with the safestrap files in some way, maybe even removing them; they do reside in the /system partition, after all. If you are running it on one of the numbered slots, maybe it is mounting the actual /system partition during some part of the update process and doing something it shouldn't on this phone.
Maybe you should create a rom slot and use it for cm. That way your phone won't be bricked...only that rom slot might get messed up if at all.
I guess safestrap is getting messed up and therefore you have to go back to stock. How are you flashing cm nightly? Are you using install option in safestrap or some other way?