Hi guys,
I recently bought the nexus 4 (4.2.2 , Baseband : .48) but like some others i am having problems with phone calls. I can receive and make them but cannot hear anything when i do (a dial or voices). Skype,Viber etc works no problem so it is just GSM calls. My sim card works in other phones perfectly. Other peoples sim cards do not work in my phone, so it is not my sim or carrier and must be the phone.
So now i want to downgrade to 4.2.1 in the hope it will fix whatever the problem is. I was hoping someone could help me with the most basic straight forward solution. I have nothing on the phone as it is brand new, so backing up data doesn't matter. All i want to do is put 4.2.1 on it.
I have a mac.
Thanks in advance
Before downgrading go to settings > Apps > All > Phone > clear cache and clear data. See if that fixes it.
Sent from my Nexus 4 using Tapatalk 4 Beta
shakey789 said:
Hi guys,
I recently bought the nexus 4 (4.2.2 , Baseband : .48) but like some others i am having problems with phone calls. I can receive and make them but cannot hear anything when i do (a dial or voices). Skype,Viber etc works no problem so it is just GSM calls. My sim card works in other phones perfectly. Other peoples sim cards do not work in my phone, so it is not my sim or carrier and must be the phone.
So now i want to downgrade to 4.2.1 in the hope it will fix whatever the problem is. I was hoping someone could help me with the most basic straight forward solution. I have nothing on the phone as it is brand new, so backing up data doesn't matter. All i want to do is put 4.2.1 on it.
I have a mac.
Thanks in advance
Click to expand...
Click to collapse
Nothing will help either change the phone or try other carriers.
I have been facing this problem and tried everything, sadly i am in india and bought the phone from US.
You can give a try to .33 radio and there is a fix in original android development forum by name Fix for no in call audio.
That didnt work for me, try if it works for you and also let me know as well.
Sent from my Nexus 4 using xda app-developers app
Download the .48 baseband and flash it via recovery. Your in call audio should definitely return.
http://forum.xda-developers.com/showthread.php?t=2087227
Sent from my Nexus 4 using Tapatalk 2
Void warranty?
scream4cheese said:
Download the .48 baseband and flash it via recovery. Your in call audio should definitely return.
http://forum.xda-developers.com/showthread.php?t=2087227
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all the replies... If i flash the baseband only will it void the warranty . There is alot of talk about 4.3 been released soon so i am tempted to wait for it either...
shakey789 said:
Thanks for all the replies... If i flash the baseband only will it void the warranty . There is alot of talk about 4.3 been released soon so i am tempted to wait for it either...
Click to expand...
Click to collapse
You already unlocked the boot loader and installed a recovery..so therefore your phone has already voided the warranty. lol.
You need the .48 baseband nevertheless. That baseband comes with the 4.2.2 update.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
You already unlocked the boot loader and installed a recovery..so therefore your phone has already voided the warranty. lol.
You need the .48 baseband nevertheless. That baseband comes with the 4.2.2 update.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I haven't done anything to my phone yet.
shakey789 said:
I haven't done anything to my phone yet.
Click to expand...
Click to collapse
Oh my bad. Lol
Sent from my Nexus 4 using Tapatalk 2
Warranty isn't voided. Does it say its voided when you unlock the bootloader? Yeah. but in reality, it really isn't.
If anything, you can always fastboot flash back to stock and relock the bootloader.
If you were on a HTC device and you unlocked your bootloader via HTCDev..... then yes your bootloader voided your warranty but since this is a Nexus device. There is no way for them to know that you did lock your bootloader.
I honestly think its a software problem and has nothing to do with the phone itself.
zephiK said:
Warranty isn't voided. Does it say its voided when you unlock the bootloader? Yeah. but in reality, it really isn't.
If anything, you can always fastboot flash back to stock and relock the bootloader.
If you were on a HTC device and you unlocked your bootloader via HTCDev..... then yes your bootloader voided your warranty but since this is a Nexus device. There is no way for them to know that you did lock your bootloader.
I honestly think its a software problem and has nothing to do with the phone itself.
Click to expand...
Click to collapse
I tried flashing the .48 and .33 radios... Neither done anything
shakey789 said:
I tried flashing the .48 and .33 radios... Neither done anything
Click to expand...
Click to collapse
Try. 54
Sent from my Nexus 4 using xda premium
randomnoob83 said:
Try. 54
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Just tried .54 . No good either. This is so frustrating. I've tried flashing the system and boot img now too I live in Ireland and bought the phone from America so returning isn't an option anymore either
EDIT ** Just done adb sideload and put 4.2.2 back on to my nexus in a hope that might fix it but it didnt.
Related
Hello
I need to return my nexus s to Samsung care since speaker is not working ..its rooted and I have miui rom currently
Plz tell me what all things I should before giving
Thank you
ancilary said:
Hello
I need to return my nexus s to Samsung care since speaker is not working ..its rooted and I have miui rom currently
Plz tell me what all things I should before giving
Thank you
Click to expand...
Click to collapse
Nope, you're pretty screwed. When unlocking the bootloader, the phone tells you that your warranty is now void.
The nexus S has a oem bootloader unlock. In other words, samsung will not hold the fact that bootloader is unlocked against you. You do need to get rid of miui and get back to stock. There is a thread showing how to do this and provides the files you need. I'll see if I can find it for you.
Sent from my Nexus S 4G
khartaras said:
Nope, you're pretty screwed. When unlocking the bootloader, the phone tells you that your warranty is now void.
Click to expand...
Click to collapse
dude shut up if u dont know what your talking about ..
go back to stock,stock recovery isnt even neccessary to be honest i know alot of people in the customer care for samsung and google they dont even check they issue command via bootloader, lastly you go into fastboot mode and issue command fastboot oem lock
mak213 said:
dude shut up if u dont know what your talking about ..
go back to stock,stock recovery isnt even neccessary to be honest i know alot of people in the customer care for samsung and google they dont even check they issue command via bootloader, lastly you go into fastboot mode and issue command fastboot oem lock
Click to expand...
Click to collapse
I said that because I was screwed over by Samsung.
I just use cwm to flash the latest ota rom then locked the bootloader and reboot.
no issues from samsung regarding voided warranty. Perhaps you had sent it in with the bootloader unlocked?
Just use rom managers stock 2.3.3 and flash it... then lock bootloader by the instructions provided a post up
Just a heads up... same thing happened to a guy and he sent it in.for a speaker that wasn't working ... he waited over a month to get his phone back rather then them sending him a new one or refurbished
Sent from my Nexus S using xda premium
khartaras said:
Nope, you're pretty screwed. When unlocking the bootloader, the phone tells you that your warranty is now void.
Click to expand...
Click to collapse
lol. are you trolling?
just flash the original system images found in the development forum, i think they are a sticky
good luck! make sure the bootloader says locked, and there is no super user app and no custom recovery!!!
I used Stock Odin image that will restore everything rom, recovery...ect then just lock bootloader. Funny thing is i sent mine back all stock and bootloader locked few months ago and got back with bootloader unlocked.
Sent from my Google Nexus S using xda premium
demo23019 said:
I used Stock Odin image that will restore everything rom, recovery...ect then just lock bootloader. Funny thing is i sent mine back all stock and bootloader locked few months ago and got back with bootloader unlocked.
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
LMAO it was probably cyanogen himself, they did hire him you know
I just picked up an s4 from att today. Ive been playing with it for about an hour and I definitely want to root the phone and remove all of the bloatware. Ive read online that there is no way to fully remove all traces of rooting this phone when needed for warranty reasons. Ive also read that att will still honor the warranty even if the phone is rooted. Does anyone have any info on this? Im experiencing a little lag here and there with the phone and am honestly not as jazzed about it as I thought I would be. If I root the phone will I still be able to switch for another phone if I choose to within 14 days and will att honor my warranty if I keep the phone and something goes wrong with it? Im in the US.
Well I had the s4 from release day,and have both root and a custom ROM.a couple weeks ago my WiFi decided it didn't wanna live no more so I flashed stock ROM through Odin and WiFi was still not working so I took my phone into the warranty center he flashed stock ROM again and it still didn't work so he just swapped it out for a new phone right there....
Long story short just unroot and flash stock ROM and you should be good to go
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
ignaciocazares said:
Well I had the s4 from release day,and have both root and a custom ROM.a couple weeks ago my WiFi decided it didn't wanna live no more so I flashed stock ROM through Odin and WiFi was still not working so I took my phone into the warranty center he flashed stock ROM again and it still didn't work so he just swapped it out for a new phone right there....
Long story short just unroot and flash stock ROM and you should be good to go
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
That can only be done if the phone hasn't been updated to mf3. There is no flashable firmware for that one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Yes forgot to mention that .also for anybody with mf3 firmware try to get a warranty exchange if you don't mind getting back a refurbished device and there's a possibility you will get a non mf3 phone
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
ignaciocazares said:
Yes forgot to mention that .also for anybody with mf3 firmware try to get a warranty exchange if you don't mind getting back a refurbished device and there's a possibility you will get a non mf3 phone
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I have heard that some members received replacements w MF3 so it is pretty much luck of the draw.
Sent from my SAMSUNG-SGH-I337 using Forum Runner
norcal61 said:
... Ive also read that att will still honor the warranty even if the phone is rooted. Does anyone have any info on this?
Click to expand...
Click to collapse
I asked ATT customer service if rooting voided the warranty. I was told rooting does not void the warranty unless rooting caused the damage. The example the rep gave me was: If you root and phone overheats as a result of rooting, then they wouldn't cover that.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Thanks for all of the replies! They're very helpful. How can I tell if my s4 has the mf3 firmware and what exactly is the difference between mf3 and the other?
Just wanted to add that the last three digits for my baseband are mdl so im assuming I dont have the mf3 software as of yet. I have a software update available. Should I update or just root the phone as it is now?
norcal61 said:
Just wanted to add that the last three digits for my baseband are mdl so im assuming I dont have the mf3 software as of yet. I have a software update available. Should I update or just root the phone as it is now?
Click to expand...
Click to collapse
Do not update, root and rename the files associated with updating.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
norcal61 said:
Just wanted to add that the last three digits for my baseband are mdl so im assuming I dont have the mf3 software as of yet. I have a software update available. Should I update or just root the phone as it is now?
Click to expand...
Click to collapse
If you want to be able to root AND flash ROMs, do not update to MF3. There is no method for loading a custom recovery for phones that have updated to MF3.
There is a thread in the General section about rooting an MF3 phone, but at this point you won't be able to flash a ROM.
HiTideBlastoise said:
Do not update, root and rename the files associated with updating.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Thank you, forgive my ignorance but could you tell me exactly which files I need to rename and what I should rename them to?
norcal61 said:
Thank you, forgive my ignorance but could you tell me exactly which files I need to rename and what I should rename them to?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2268946
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I cracked my screen and the replacement S4 came with MF3.
Sent from my GT-P5110 using XDA Premium HD app
is flashing official rom from sammobile.com will brick my mobile???
or create IMEI problem.
As i rooted my current official firmware. i want to go back to stock. but i took backup of my efs folder but i haven't found any nv_data file on it.
Please advise is official rom will to create IMEI probem.
Depends on which phone and firmware u got
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Demented22 said:
Depends on which phone and firmware u got
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
i bought my mobile from France so i download this rom
I9505XXUBMEA_I9505OXXBMF1_XEF MAIN
which i download from sammobile.com
Ohhh gotcha
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
I was actually wondering... If I'm network locked and I flashed a new stock ROM, would it remove the network lock? I don't think it will, but just want to confirm and to know the rationale behind all of it. I was thinking of rooting my S4 to get it to downgrade and have the network lock removed, but don't know about all these things. A lot of threads mention rooting for custom firmwares but not rooting in order to remove network lock afterwards.
Sent from my GT-I9505 using Tapatalk 4
ladyhaly said:
I was actually wondering... If I'm network locked and I flashed a new stock ROM, would it remove the network lock? I don't think it will, but just want to confirm and to know the rationale behind all of it. I was thinking of rooting my S4 to get it to downgrade and have the network lock removed, but don't know about all these things. A lot of threads mention rooting for custom firmwares but not rooting in order to remove network lock afterwards.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Flashing any rom will not remove the network lock... but it can brick ur phone if u flashed a rom that is not intended for ur phone, if u want to get it unlocked ur best option for that is call ur current carrier to get the unlock code, it could cost u for the code but thats about the only way besides rooting and trying to unlock it that way after root.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
I've unlocked my phone using an unlock code with one of those websites. It's a success. No problems. The problems I encountered recently had to do with the defective battery that came with my S4. What I'm curious to know now is if I can flash a ROM from my country where I got my phone... Just to make it like an unbranded phone. This is because when I boot up my phone, I see my carrier's logo and one of the wallpapers they replaced with their carrier logo as well. It's pretty annoying... So I wonder if I can flash a non-carrier unbranded ROM from my country to my phone. And do ai need to root to do so?
Sent from my GT-I9505 using Tapatalk
So I did the root keeper wrong and updated, losing root. Anyone else in this club with me? It's only been a few hours and I already miss it.
Atleast I have better pictures though....
Sent from my XT1058 using xda app-developers app
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Abyssul said:
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Click to expand...
Click to collapse
This process is just flashing the firmware through rsdlite which won't happen because it's a downgrade. I tried.
Sent from my XT1058 using xda app-developers app
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
freak4dell said:
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
Click to expand...
Click to collapse
just tried, did not work. fails at the boot.img
Abyssul said:
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
Click to expand...
Click to collapse
first things I tried and doesn't work
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Some of us didn't want root in the first place! #TeamStockMotoX :silly:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Because some of us can't unlock our bootloader.
eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Just remember that Retail AT&T and Verizon and MotoMaker AT&T variants aren't able to have their boot loaders unlocked
Sent from my XT1058 using Tapatalk 4
Lost root don't care. Motorola got this phone right. I'm good with stock.
rivlez said:
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
emerica243 said:
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
Click to expand...
Click to collapse
My wifi was messed up in any mode. It wouldn't turn on for some reason. I restored the 17.51 firmware after the botched update messed up my wifi and it worked fine and I actually ended up doing it 2 times since a titanium backup messed up my phone. I was definitely on the 17.54 update. It definitely let me downgrade. How would you like me to prove it to you?
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
sravanz said:
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
Click to expand...
Click to collapse
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Rask40 said:
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Click to expand...
Click to collapse
Me too. My wifi is FUBARED in recovery. It's because we don't have the new kernel and to be technical were using the old system/recovery in our "recovery mode" I think that's why it's working in the regular mode and not recovery mode..... Or that's what I understand. Though I'm probably wrong.
When I upgraded I got a failed upgrade after final boot. Although it still says the newest version. I'm tempted to RSD back like some others have just to try but I don't want a paper weight.
Sent from non rooted motoX :'(
gunnyman said:
Lost root don't care. Motorola got this phone right. I'm good with stock.
Click to expand...
Click to collapse
While I'm kind of excited to see SafeStrap out, and updated (fixes phone/data, etc...), I'm still hoping some attempt is in the works for unlock on at&t.
Regardless, there aren't any custom roms to really flash anyways.
Had I an unlocked bootloader, I'd have a custom kernel in the works, and maybe some custom roms with some TeamAcid love.
Come see, come saw... Patience wins all.
hey fellow members,
k, so I've been having this issue where there's no signal and the baseband is unknown. This has been happening ever since I flashed KitKat and usually after I reboot the phone, the signal/baseband would pop up after about an hour or if I'm travelling around town.
When I did receive signal, there was no audio during calls so I decided to flash the kitkat factory image hoping it would solve all these issues but now the signal never shows up and the baseband is still unknown. Then I flashed jellybean 4.2 factory image and the problem doesn't exist, I receive signal immediately and audio during call worked so I ruled out a possible hardware issue.
I've also read through the other dozen of threads with similar problems but none of those solutions seem to solve the issue.
I have no clue what's going on and any help would be great
nav200 said:
hey fellow members,
k, so I've been having this issue where there's no signal and the baseband is unknown. This has been happening ever since I flashed KitKat and usually after I reboot the phone, the signal/baseband would pop up after about an hour or if I'm travelling around town.
When I did receive signal, there was no audio during calls so I decided to flash the kitkat factory image hoping it would solve all these issues but now the signal never shows up and the baseband is still unknown. Then I flashed jellybean 4.2 factory image and the problem doesn't exist, I receive signal immediately and audio during call worked so I ruled out a possible hardware issue.
I've also read through the other dozen of threads with similar problems but none of those solutions seem to solve the issue.
I have no clue what's going on and any help would be great
Click to expand...
Click to collapse
Sounds like a radio issue. Try flashing the latest radio, which is .98 I do believe.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Sounds like a radio issue. Try flashing the latest radio, which is .98 I do believe.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I've done that already but still nothing
k so I got signal finally after a day of waiting but there's no sound during calls again. Any ideas?
anyone? I've been searching for a solution but haven't got anything.
Does your phone have a valid imei? I'm just guessing here as I've seen posts from N4 owners that lost their imei during a flash or update process.
audit13 said:
Does your phone have a valid imei? I'm just guessing here as I've seen posts from N4 owners that lost their imei during a flash or update process.
Click to expand...
Click to collapse
Ya I'm pretty sure I have a valid imei, how do you check that?
nav200 said:
Ya I'm pretty sure I have a valid imei, how do you check that?
Click to expand...
Click to collapse
Dial *#06# on your keypad.
audit13 said:
Dial *#06# on your keypad.
Click to expand...
Click to collapse
tried it and has a valid imei so that's not the issue
nav200 said:
tried it and has a valid imei so that's not the issue
Click to expand...
Click to collapse
Well, there goes my theory. Are you running the .98 radio?
audit13 said:
Well, there goes my theory. Are you running the .98 radio?
Click to expand...
Click to collapse
yup and the latest bootloader but no luck at all.
nav200 said:
yup and the latest bootloader but no luck at all.
Click to expand...
Click to collapse
Very strange. Maybe flash back to completely stock 4.4.2 or flash a custom rom that includes the latest radio and bootloader?
audit13 said:
Very strange. Maybe flash back to completely stock 4.4.2 or flash a custom rom that includes the latest radio and bootloader?
Click to expand...
Click to collapse
lol I've been doing that for the past 3 days but haven't had success. I'm running out of options
It should be hardware problem
wq2020wdm said:
It should be hardware problem
Click to expand...
Click to collapse
no it's not a hardware problem. It was working fine when i was on 4.2 and 4.3
nav200 said:
no it's not a hardware problem. It was working fine when i was on 4.2 and 4.3
Click to expand...
Click to collapse
So why not (for the meantime) go back to 4.3 or 4.2? Get it to work, then let us know the radio it is using and go from there.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
So why not (for the meantime) go back to 4.3 or 4.2? Get it to work, then let us know the radio it is using and go from there.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
k so now when i go back to 4.2 the in call audio doesn't work
nav200 said:
k so now when i go back to 4.2 the in call audio doesn't work
Click to expand...
Click to collapse
are you fully stock or a custom rom?
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
are you fully stock or a custom rom?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
fully stock. Maybe I need to flash a radio on 4.2?
nav200 said:
fully stock. Maybe I need to flash a radio on 4.2?
Click to expand...
Click to collapse
Yep.
Sent from my Nexus 7 (2013)