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.

Samsung OTA stuck on reboot

I got the update message (41.2) MB.
It is being downloaded and verifies.
I then select to restart & install.
The phone starts booting, but stays on the Google logo for a very long time (more than half an hour).
To try the update again I have to take the battery out, restart the phone (which shows 4.0.2), clear Google Services Framework and check for update.
The updates download etc. etc.
My phone is not rooted and it had no problem in the past updating OTA to 4.0.2
Thanks

So you are trying to update "YAKJUXW" 4.0.2 to 4.0.4?
hmm.. have you flashed any custom kernel or another radio baseband and are you using custom Clockworkmod..?
try to make backup of the 4.0.2 if possible (move to somewhere PC, hardware,..) and then make factory reset and try then update it to 4.0.4

manumanfred said:
So you are trying to update "YAKJUXW" 4.0.2 to 4.0.4?
Click to expand...
Click to collapse
Yes
manumanfred said:
hmm.. have you flashed any custom kernel or another radio baseband and are you using custom Clockworkmod..?
Click to expand...
Click to collapse
No. Nothing like this.
I will try the factory reset if I can't fix it without it.
Thanks

OferR said:
Yes
No. Nothing like this.
I will try the factory reset if I can't fix it without it.
Thanks
Click to expand...
Click to collapse
Okay!

Any resolution?
manumanfred said:
Okay!
Click to expand...
Click to collapse
I've been experiencing same. Bought GalNex from (apparently) Poland before Play store. It is yakjuxw. Past two weeks it's tried to update itself 3 times and just sits at (white) Google on black screen for a very long time.
I actually have to remove battery to recover. Then all is well, but no firmware update and if i follow reddit.com's -> ysk_how_to_get_the_404_ota_quicker to "force" the update, same result.
Did your factory reset solve the problem?
oh4real

No resolution
Sorry, I did nothing so far. I'm still on 4.0.2.
When I get the time, I'm likely to move on to a rooted yakju.
If you do manage to resolve it, please tell us.
Thanks

Help! Nexus Cant Connect to Wifi after I used the 7.4 toolkit to root it

I had it rooted using the 7.4 toolkit with an OTA update of JellyBean.
Edit: I did not flash anything yet...stock 4.1.1

Should I flash a ROM over it in recovery? such as AKOSP? Please Help I'm really stuck -.-

luminiz said:
I had it rooted using the 7.4 toolkit with an OTA update of JellyBean.
Edit: I did not flash anything yet...stock 4.1.1
Click to expand...
Click to collapse
Not enough detail. What options did you choose for the device in the toolkit? Did you choose the correct one?
Rooting doesn't modify your ROM settings, so flashing another ROM probably will not make a difference.

netbuzz said:
Not enough detail. What options did you choose for the device in the toolkit? Did you choose the correct one?
Rooting doesn't modify your ROM settings, so flashing another ROM probably will not make a difference.
Click to expand...
Click to collapse
Thank you for your reply! Yes I followed every direction until it was fully unlocked and rooted with CWM installed...not sure why wifi suddenly stopped.

luminiz said:
Thank you for your reply! Yes I followed every direction until it was fully unlocked and rooted with CWM installed...not sure why wifi suddenly stopped.
Click to expand...
Click to collapse
Did unlocking the bootloader erase your phone to factory settings? If so, you had to setup your wifi from beginning, i.e. enter wifi password?
Is the wifi antenna turning on?

netbuzz said:
Did unlocking the bootloader erase your phone to factory settings? If so, you had to setup your wifi from beginning, i.e. enter wifi password?
Is the wifi antenna turning on?
Click to expand...
Click to collapse
Thank you for your fast reply. Yes i erased everything through the beginning process. I skipped the wifi setup to enable usb debugging I believe. And the wifi attenna is not turnning on. I did leave the usb cable plugged in throughout the process of the Toolkit...not sure if that makes a difference...bc it says to take it out at some point.
Edit: the Wifi is on when I click on it...but when i try to connect to a network...it either doesnt do anything and stays there or keeps on saying connecting until it says disconnected

Bump. Please HELP. I CANT EVEN CALL MY MOM...i forgot her phone number -,-

Bump 2. Help! I tried everything...Please anyone?

Maybe you need the jellybean WiFi fix. There have been complaints of lost or weak WiFi.
Sent from my Galaxy Nexus using xda app-developers app

If you're having problems with 4.1, why don't you try downgrading? Download something like AOKP milestone based on 4.0.1 and see if the issue disappears. Don't forget to do a full wipe (dalvik as well) in CWM.

well i do feel like having trouble with wifi after updated to 4.1.1 ... it loses signals completely where other devices say "fair signal" .. thats kinda bad about JB update .. i think it must've got to do something with the baseband version .. my original 4.0.4 had something else and now in JB its different ..
i remember about my previous HTC .. when it comes to bad performance of signals, wifi .. etc .... the Radio must be re flashed. ..
if anybody knows anything .. please guide us ...
oops .. i found another forum for radio problems .. lets see if i can find my solution here http://forum.xda-developers.com/showthread.php?t=1405345 ..

V0odo0 said:
well i do feel like having trouble with wifi after updated to 4.1.1 ... it loses signals completely where other devices say "fair signal" .. thats kinda bad about JB update .. i think it must've got to do something with the baseband version .. my original 4.0.4 had something else and now in JB its different ..
i remember about my previous HTC .. when it comes to bad performance of signals, wifi .. etc .... the Radio must be re flashed. ..
if anybody knows anything .. please guide us ...
oops .. i found another forum for radio problems .. lets see if i can find my solution here http://forum.xda-developers.com/showthread.php?t=1405345 ..
Click to expand...
Click to collapse
Thanks for the heads up. Do you know which one is for the USA gsm version can't seem to find it
Sent from my Galaxy Nexus using xda app-developers app

[Q] Problem with updating to 4.2

Hello there, I have a problem.
I have Samsung Galaxy Nexus, Takju, build JZO54K, version 4.1.2
I'm in Slovakia, O2 provider (don't know if that helps)
Today(November 19) I've got notification that I can update to 4.2 (same thing happened four days ago(November 15)), so I started updating.
I saw the icon of Android guy, with some blue wires or something. Than the icon changed, the Android guy was lying and there was red triangle with exclamation mark in it.
Did it happen to anyone else? Is there some problem with my phone or should I just wait and the update will eventually arrive?
Sorry for my english, and thank you for your help

problem updating to 4.2
Are you rooted?

JamesPumaEnjoi said:
Are you rooted?
Click to expand...
Click to collapse
No. I would like to be updated automatically, I don't want to make it manually if I don't have to. Because I would screw it up.

4.2 Update issue
It could be that the phone isnt accepting the phone over the OTA (OVER THE AIR) ive seen this issue before on android phone usually if it wont take it OTA the only other way flash it manually . you dont necessary have to root phone you can always look for the OTA UNROOTED Image which you can flash through fastboot

Froz3nsolid said:
It could be that the phone isnt accepting the phone over the OTA (OVER THE AIR) ive seen this issue before on android phone usually if it wont take it OTA the only other way flash it manually . you dont necessary have to root phone you can always look for the OTA UNROOTED Image which you can flash through fastboot
Click to expand...
Click to collapse
Thank you very much
Edit:
But, can it be this problem even thou I previously did have OTA update to 4.1.2 and there was no problem at all?

4.2 update issue
could be, im really not sure that is odd that the phone did the 4.1.2 but not 4.2
i have another question when he accepted the update where you on mobile network or wifi

Froz3nsolid said:
could be, im really not sure that is odd that the phone did the 4.1.2 but not 4.2
i have another question when he accepted the update where you on mobile network or wifi
Click to expand...
Click to collapse
When the notification about update came up I was on mobile network, but I was low on battery, so I waited till I get home. Then I did it on charger and home wifi network

laker_faker said:
When the notification about update came up I was on mobile network, but I was low on battery, so I waited till I get home. Then I did it on charger and home wifi network
Click to expand...
Click to collapse
were you completely stock? root doesnt matter but you have to be stock, no custom kernels or mods.. and you cant have cwm either

k786 said:
were you completely stock? root doesnt matter but you have to be stock, no custom kernels or mods.. and you cant have cwm either
Click to expand...
Click to collapse
yeah, completely stock, don't know what cwm is sorry:/ But as I sad, previous OTA went through without any problem, so it can't be it, can it?

laker_faker said:
yeah, completely stock, don't know what cwm is sorry:/ But as I sad, previous OTA went through without any problem, so it can't be it, can it?
Click to expand...
Click to collapse
thats weird.. if you are stock the ota should be applied without any issues

k786 said:
thats weird.. if you are stock the ota should be applied without any issues
Click to expand...
Click to collapse
Well yeah, but it's not

Yea got ahead give it a good charger and hook it up to wifi and see if that does the trick , when i got the prompt on my Nexus 7 i was connect to wifi and it went through fine
Sent from my Galaxy Nexus using xda app-developers app

Froz3nsolid said:
Yea got ahead give it a good charger and hook it up to wifi and see if that does the trick , when i got the prompt on my Nexus 7 i was connect to wifi and it went through fine
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But I did exactly that
I was hoping that more people would have the same problem so I can find a solution, but if it's just me, than there is not much hope.

Also i would check ur baseband(radio) to see of its up too date the lastest i believe is XXLF1
Sent from my Galaxy Nexus using xda app-developers app

k786 said:
thats weird.. if you are stock the ota should be applied without any issues
Click to expand...
Click to collapse
laker_faker said:
yeah, completely stock, don't know what cwm is sorry:/ But as I sad, previous OTA went through without any problem, so it can't be it, can it?
Click to expand...
Click to collapse
Try this.....boot the phone and go to settings >>>apps>>>all>>>>Google frameworks service>>>>>clear the cache AND THEN the data in that order....when you go back to check on the update it'll say last checked 12/31/69 you want to see that and then search for the update....that clears framework and helps pull the update to your device....I've used this method and it worked for me with ICS after 3-4 tries give it a go and let us know what happens

JamesPumaEnjoi said:
Try this.....boot the phone and go to settings >>>apps>>>all>>>>Google frameworks service>>>>>clear the cache AND THEN the data in that order....when you go back to check on the update it'll say last checked 12/31/69 you want to see that and then search for the update....that clears framework and helps pull the update to your device....I've used this method and it worked for me with ICS after 3-4 tries give it a go and let us know what happens
Click to expand...
Click to collapse
I did that and the same thing happened again. The problem is not in that I don't see the updated, problem is that it won't install. Updating starts and about halfway through the red triangle appears and I'm screwed.
I'm really depressed now

Froz3nsolid said:
Also i would check ur baseband(radio) to see of its up too date the lastest i believe is XXLF1
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have I9250XXLA2 good sir
I see that that's way too old, but how do I update it please?

LF1 is the bb version for 4.1.2;
'fastboot flash radio bbversion.img'
http://forum.xda-developers.com/showthread.php?t=1812959
Sent from my i9250

laker_faker said:
I did that and the same thing happened again. The problem is not in that I don't see the updated, problem is that it won't install. Updating starts and about halfway through the red triangle appears and I'm screwed.
I'm really depressed now
Click to expand...
Click to collapse
How's it going did anything work?

JamesPumaEnjoi said:
How's it going did anything work?
Click to expand...
Click to collapse
I didn't do anything yet. I want to try the radio update, but I'm too afraid I'll screw it up so I do nothing :<

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".