So, over the weekend, my friend's Nexus has started having odd audio issues. He's been using a Paranoidandroid Jellybean ROM and was working fine for the past few weeks. What happens is that whenever an apps needs to play audio through the speaker (YouTube, Google Play Music, Navigation, changing a ringtone) or when the volume is adjusted, the phone locks up then reboots. We have tried wiping the cache, dalvik cache, fixing permissions, reflashing the rom and flashing different roms, flashing roms without flashing the GApps in afterwards, and using a nandroid recovery. All of these proved fruitless as the problem persists through every flash, wipe, and recovery. In addition to the audio problems, the custom alarms that my friend made are now missing and the /data folder is completely empty. I looked in my /data folder on my SGH-T989 just to confirm that the folder is supposed to have data. My question is: is this a hardware issue, a software issue or both? If hardware he can just replace the phone, but if software, he would like to be able to fix it. We have not attempted to flash a stock rom or ODIN the phone back to stock but we do plan to try that.
If you did not do a full wipe before changing from a rom to PA or any other ROM this can cause a lot of unwanted problems. By doing a full wipe, your problem would be solved. If not it's a hardware issue.
Flashing back to stock ROM isn't really a full wipe. If you are afraid of losing data root the phone and titanium backup
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Understandable
JamesInsights said:
If you did not do a full wipe before changing from a rom to PA or any other ROM this can cause a lot of unwanted problems. By doing a full wipe, your problem would be solved. If not it's a hardware issue.
Flashing back to stock ROM isn't really a full wipe. If you are afraid of losing data root the phone and titanium backup
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Click to expand...
Click to collapse
While that does make sense, this is how it was explained to me. (I may have forgotten to mention this in the OP) This problem did not start after flashing a new ROM but after 2 weeks of use. When we tried to fix the issue, we did do a full wipe (Wipe data, cache, dalvik cache) and reflashed the rom. But what makes this issue more unusual is that when we used the nandroid that he has, the problem persisted and that nandroid was one that had no issues. The /Data folder is also unusual because even after the reflash and nandroid recovery, that folder remains empty. Are these two issues related or is this coincidence that they are happening at the same time? Also, is there any more info that is needed that will aid in trying to fix this problem?
A similar thing started happening to me whenever I'd use the phone (make or receive a call).
I flashed a different kernel and that fixed it for me.
Sent from my Galaxy Nexus using xda app-developers app
That's pretty weird. The data thing could be causing it. Did he download any app that could cause that folder to be affected? You should try full wipe so you can get that folder back. Does the nandroid still have the data?
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Things we've tried
We have tried multiple kernels and different ROMs as well. Every time the problem continues. As for the /data folder, a clean wipe with a fresh ROM flash and nandroids result in that folder remaining empty. At this point, he's going to restore the phone to stock and send it to Verizon to get a new one. I'm starting to think that it's a hardware issue that is causing the phone to reboot when the rear speaker is used but as for the data, I can't think of anything except for maybe something in an app (as was suggested by JamesInsights) or a file on his SD card that corrupted something (although, I doubt that seeing as SU would kick in if a file was asking for SU permissions and getting a virus on a Linux based device is difficult).
Added: I would like to provide a logcat but I don't have the phone near me and I haven't learned to do that yet.
Related
Hey ,
I wouldn't consider myself a "noob" when it comes to flashing and the rooting of android but I seem to have encountered a issue a can't resolve.
A few days ago i flashed the cm9 rom , decided i didn't like it and re-stored back back to AOKP. After restoring franco's kernal was then gone. So i went and wiped the phone and re-flashed the rom and kernal. After re-booting the phone gets stuck on a bootloop and will not boot up from anything except my backups in clockwork. I have wiped the phone , cache and delvik.
Any other idea's what to do to fix this?
Thanks chaps,
J
Format system in recovery. It's under mounts and storage. Along with data and cache.
Obviously then flash a ROM of your choice.
Sent from my Galaxy Nexus using XDA App
And not restoring system data from a different rom on top of another also prevents conflicts.
I had flashed Warm TwoPointThree. Didn't really like it so I restored to my nandroid back up. Now the phone randomly crashes for no apparent reason. It is sitting next to me on my desk and just now it crashed, wasn't even touching it. Secondary to the crashes is that after it happen and I try to report the phone is registering no charge and then immediately shuts down till I put it on a charger, regardless of actual battery charge.
Edit
More info. It has never crashed while on the charger. Don't know if that is relevant.
Did you wipe properly prior to restoring your nandroid? Also, what recovery are you using? If it's not Amon-ra, you need to get it! Make sure when doing a nandroid restore you have the appropriate items checked for restore (Assuming you did this when making the nandroid to begin with). Usually Boot, System, Data, and SD ext if partitioned.
Im using Amon-ra and I have an unpartitioned SD card. What do you mean by wipe? I'm a new to the entire rooting thing.
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
dieselford said:
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can I use the wipe feature in Amon-ra to do this?
Yes. That is the way to do it.
Sent from my PC36100 using xda premium
Try fix permissions, I think RA has it under other, or if u have Rom manager there is an option to fix permissions
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
SabaBoBaba said:
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
Click to expand...
Click to collapse
Yes that's it.
Well the crashes have started again. They seem to start slow, one crash then like 3 days later another and then just increase in frequency, today it crashed 5 times before noon. I'm at the point that I think perhaps I need to wipe and not attempt to do a restore. My concern is will I lose my root if I do that?
Will I lose root if I do wipe with out restoring afterward?
SabaBoBaba said:
Will I lose root if I do wipe with out restoring afterward?
Click to expand...
Click to collapse
If you wipe without restoring, you won't have a ROM on your device. You'll have to flash one, and as long as it's a custom or rooted stock ROM, you'll be fine.
Well I did a factory reset tonight so we'll see how that goes. Thanks to those people who contributed.
Well I did the factory reset and this morning it crashed again. I'm at a loss. All this started after I installed the Warm 2.3 ROM and then restored back to a backup to get the stock ROM back. Any thoughts on what to try now?
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
SabaBoBaba said:
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
Click to expand...
Click to collapse
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Captain_Throwback said:
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Click to expand...
Click to collapse
Well Im going to flash this http://forum.xda-developers.com/showthread.php?t=1455340&highlight=stock+rom and see if that works. Thanks for the assist.
After wiping last night and loading the rooted version of the latest stock ROM it crashed again today. Next idea?
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Grizraz said:
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Click to expand...
Click to collapse
Ill give that a shot. I hope I can fix what ever I did to foul this thing up.
Just from searching the forums I really dont understand this edify thing. Can you help be get some clarity on it?
Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk
Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.
I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2
Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.
Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2
So I've been flashing a couple of different roms this week like Carbon (based on AOSP), PACMAN (Don't know what it's based on), Rootbox (based on AOKP) and Slimbean (AOSP) the method I've been using to flash is wiping data/factory reset, wiping cache/dalvic cache, flashing ROM & gapps, flashing NexusLouder mod, flashing custom kernel, advance restoring data only then rebooting. I think this could be the cause of the boot loops. Or... it could be the function implemented in Carbon which doesn't require you to constantly flash gapps anymore since it backs everything in /system/apps. Anyone know what the cause of the boot loops are for sure?
Extra details - I started using this method ever since I was on AOKP which was my first custom rom. Then a few months ago, I moved to Rootbox, then Carbon, then I tried out PACMAN for a while then reverted back and just today I went back to Rootbox for a while, then I tried out SlimBean and ever since today, I've been getting random bootloops when I restart my phone. It doesn't happen every time I reboot my phone but when it does, clearing the cache solves the problem temporarly and I also had to do a full restore of my nandroid a couple of times today.
Also, I use this method because I have over 75 songs on my playlist which I spent hours creating and I don't want to start all over again. I also don't want to set all my rom settings again either.
Reduce any OC
Undo any Voltage mods
Disable any apps that alter how the system behaves
Disable all apps and enable one by one until you have an issue
You get the idea.
Definitely want to avoid restoring data from another rom and flashing audio mod. If after flashing a new rom you still get the random reboot then you can narrow down the problem.
Sent from my Galaxy Nexus
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
I always do that :thumbup:
Sent from my Galaxy Nexus using xda premium
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
Thanks for the tip
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Weird, never seen that before. Tell us what recovery you have and exactly what you are wiping. Can't think of anything else at the moment I'm sure others will chime in.
Sounds to me like you're not wiping /data. This is where your apps and setting are stored and unless you factory reset using stock recovery, deliberately wipe/format /data, or flash a Rom that wipes it for you, all your apps and settings will remain.
Seems like normal behavior to me.
Sent from my SGH-T999L using xda premium
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
kruse1944 said:
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Click to expand...
Click to collapse
Tapatalk.
mt3g said:
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
Click to expand...
Click to collapse
Got it that's why. I was sure wiping system would wipe data too. But do you think its dangerous to not wipe data? Because actually my ROM is rocking right now without issues? Should I reflash it for safety?
It just depends....
It's always best to start clean, especially if you were having problems. But if you want to keep data intact, you should be ok as long as you don't go to an entirely different rom, base, or build.
If you are updating to a newer version of the same build, you're fine. Also if updating to a newer build/version you should be ok, but may have a few hiccups.
However, anytime you go backwards (4.2.2 to 4.1.2) you should wipe it all. The same is true if you are moving to a different base, such as CM to TW. Keeping your internal sdcard data is usually ok, but sometimes it can cause some issues.
Sent from my SGH-T999L using xda premium