Develop Bugs

HELP! Installed rom and now earphone doesn't work (or any other roms installed either

I'm not sure what happened but this morning I installed Codename Android's rom since everyone's been speaking so highly of it. I immediately got reboots right after starting. The screen would freeze and then the phone would reboot. I figured there was something wrong so I formatted data/factory reset, formatted cache and even formatted /system and installed it again. No reboots but the earpiece would not work on phone calls (speaker phone does). I also noticed that the screen doesn't turn off when I hold the phone to my face (so the proximity sensor seems to be messed up too). So I installed another rom: Redemption Rom. Same problem. I installed GummyNex, same problem.
I even unrooted and relocked the bootloader and EVEN THEN the earpiece did not work.
I feel like this is a software issue because it happened after installing a rom AND the proximity sensor doesn't work which seems strange for both that and the earpiece to stop working at the same time...
Is there something else that I haven't tried yet? Any suggestions??
I've only had the phone for a couple days so it could easily be a hardware issue I suppose, but I wanted to check if anyone had anything like this happen to them.*
Thanks guys!

Codename Android....if everyone's so highly speaking of it how come I haven't heard of it?
- Which version of the phone you have? CDMA? I'm assuming?
- What kernel?

Codename Android is one of the most popular roms on Rootzwiki

HeliosAI said:
Codename Android is one of the most popular rom on Rootzwiki
Click to expand...
Click to collapse
This is XDA, not Rootzwiki. I googled it. Answer the rest of the questions.
Have you tried flashing another ROM? Flashing stock images provided by Google?

CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?

I tried a few other roms and the issue was still there as well.

HeliosAI said:
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
Click to expand...
Click to collapse
And you've checked the obvious that the headphones work on another device correct? Tried another headphone on the phone?
If you fully wiped the phone and tried it with another ROM then it's most likely a hardware problem. And maybe it was a coinicidence that it broke right when you flashed the ROM.
Go into your about phone and tell me what it says for "kernel version"

Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.

HeliosAI said:
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
Click to expand...
Click to collapse
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.

zephiK said:
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
Click to expand...
Click to collapse
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1

HeliosAI said:
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
Click to expand...
Click to collapse
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.

zephiK said:
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
Click to expand...
Click to collapse
Yeah very weird. Thanks again man, really appreciate it.

HeliosAI said:
Yeah very weird. Thanks again man, really appreciate it.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck with your new replacement when you get it though.

[Q] primoc cdma kernel crash (all kernels)

RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?

wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app

cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.

wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.

patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info

When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain

aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.

wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.

patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!

I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?

MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.

Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?

i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...

jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...

More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?

Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!

madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?

I'm so close to downgrading....

Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.

Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.

Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...

If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.

mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!

cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.

g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:

cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.

g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.

jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium

Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1

Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks

abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".

[Q] Frequent Mobile Data Drops on CM11 Nightly (Especially After Ending Phone Calls)

I have been using Cyanogenmod 11 Nightlies for my device for about as long as they have been out, so I know it is still a work in progress, and most of the issues I have faced have gone away as newer nightly builds have been released, so I have not reported any issues as of yet.
Within the last month or so, I have noticed a new issue. The mobile data has been randomly cutting out, allowing only emergency phone calls. It only goes out for about a minute or two, but it is still a huge inconvenience. It seems to happen randomly, except after I finish a phone call -- it almost always cuts out immediately after (very frustrating for when calls are dropped, because I need to wait a minute or two before I can call back).
Has anyone else experienced this or know of a fix? I just tried re-flashing the latest radio and that did not seem to help. I have also tried full system/data wipes as well and none of the Nightly builds for the last month or so have been able to fix it.
Thanks, everyone.

You need to flash any touchwiz rom in order reset your nvram.

Corvetrims77 said:
You need to flash any touchwiz rom in order reset your nvram.
Click to expand...
Click to collapse
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.

pravus87 said:
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
Click to expand...
Click to collapse
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).

Corvetrims77 said:
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Click to expand...
Click to collapse
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.

pravus87 said:
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
Click to expand...
Click to collapse
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.

Corvetrims77 said:
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.

pravus87 said:
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
Click to expand...
Click to collapse
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.

mreadshaw said:
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
Click to expand...
Click to collapse
I actually did not use Odin at all. I was able to find a thread that posted a 4.1.1 stock .zip, a .zip to keep root, and a .zip to keep custom recovery. (I have tried searching for the thread to share with you but am unable to find it). I was definitely over-thinking it. Just install the .zips from TWRP or CWM as you would any other custom ROM -- just make sure you do not have the 4.3 bootloader installed. That's it.
Sorry for the delayed response!

Android OS is sucking up all my mobile data!

Got to work this morning to find out I had no mobile data left (attached image). I thought, how strange, yesterday I'd had about ~1GB usage out of my 4GB available, I of course immediately when and looked to see what had used it all and Android OS was at the top with 2.13GB (WTF?).
This also isn't the first time this has happened, I had the same last month. Can someone please explain what is going on because I know for damn sure I've not used all that, I only browsed a few web pages this morning.
Sent from my Pixel XL using Tapatalk

Stop automatic backup

thenessus said:
Stop automatic backup
Click to expand...
Click to collapse
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Sent from my Pixel XL using Tapatalk

pairedprototype said:
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Click to expand...
Click to collapse
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.

Use Data Saver in settings, works a treat

TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.

Just switch to the unlimited data plan..problem solved

TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
alluringreality said:
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Click to expand...
Click to collapse
You are indeed correct, I am due an update, however, I'm not rooted currently although, my bootloader is unlocked as I've been assisting with getting Magisk working on stock for Pixel devices.
And what kind of idiot developer/team thought downloading OS updates over mobile data without question was okay!? I've now got to go for 2 weeks without, I'm royally p*ssed about it. Guess I'd better flash the new update then while I have a (non-cellular) internet connection.
I remember when Google targeted power users with Nexus devices, I guess this is not entirely true for Pixel devices. Big boys like to do what they want, even if that means staying on a particular version of Android because we might be testing things... I'd rather not have OS updates forced down my throat, it's the same thing that bugs me with Windows 10.

lucky_strike33 said:
Just switch to the unlimited data plan..problem solved
Click to expand...
Click to collapse
If you're willing to pay the extra, sure thing!

You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data

lucky_strike33 said:
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
Click to expand...
Click to collapse
That's what I usually do! Just not had the time to do it recently.

this is caused by update downloading and failing over and over. I went into the dev options and turned off the auto update but it did not work. I had to update the phone manually and now its fine. I think after rooting the phone and going back to stock rom this happens.

IDK man, I was rooted and was pulling like 10gb+. Flashed stock via adb and I think it's still doing it. Project fi.

This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.

FrostyOrDie said:
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
Click to expand...
Click to collapse
When you returned to stock did you get to the latest version?

TonikJDK said:
When you returned to stock did you get to the latest version?
Click to expand...
Click to collapse
No. This all happened since returning to stock. Today I sideloaded the August update with adb and my phone says it's on the current version finally. It seems the support people at project fi are clueless for the most part. You have to do everything yourself but they will at least credit your account for the data used by Android os if you call them and tell them what's up. They want screen shots of the data usage. So save one before you go messing with stuff