Related
Hi all,
I got a Nexus 4 from Ebay. Cellphone is in flawless condition, it probably has less than a couple of months of use. Unfortunately, I am not able to pick up a signal in any way. I just get a constant "No Service" message, and occasionally it will jump to "Emergency Calls Only".
Testing menu says Signal Strenght is 0 dBm 99 asu, no neighboring cells and location is unknown.
I've tried changing the prefered network to WCDMA only (as suggested in other threads), also tried with the other available settings with no luck. Tried playing around with the Change Bands setting as well but it makes no difference
Tried with a few different sim cards as well but that didn't work either, just got signal momentarily and but it would go on and off.
Cellphone came with 4.2.2 and I upgraded to 4.3 as requested by the system. Same issue.
Tried basebands 48 and 84.
Tried CM 10.2.
Replaced SIM card with a brand new one.
Cellphone doesn't appear to be blacklisted either.
Not sure what to do next. I'll try to get in contact with the seller but I don't expect much from him or eBay. Maybe I can sell off the device very cheap for spare parts, or send it for repair somewhere? Leave it as a dev device (which would virtually indistinguishable from a N5 that I plan to get anyway), Anyone else has any other suggestions or ideas?
Try to install a factory stock image: http://forum.xda-developers.com/showthread.php?t=2010312
If you pay with PayPal you get buyer protection so you can try to get your money back.
Could be a hardware or antenna issue.
To me it seems like its been blocked for certain reasons. Either it was reported stolen or the person who sold it to you didn't pay his/her bill for which the carrier blocked it. In that case you can't do much about it.
I would contact the seller right away. If you get no response contact paypal and eBay.
Sent from my Nexus 4 using Tapatalk 4
This problem is occurring for a lot of Nexus 4 users, including me. Its some sort of pandemic. Here’s what you can do to atleast restore service to your phone : flash the factory 4.3 image to your phone, again. However, try flashing a radio that is 54 or older with it. Make sure you wipe the cache and flash all the partitions, system, boot, bootloader and the old radio. This will bring back service to your phone (did for me), however you will be left with no in call audio and your phone wont connect to the internet through the mobile network, only wifi. After doing this, you will see your baseband and IMEI in the phone.
You can use this as some sort of “test” to verify if your phone really isn’t stolen. What is the ultimate resolution to this problem ? I really don’t know yet. I’ve been breaking my head over this for the past 4 days now. Maybe I’m going to try out the unbrick method mentioned over here to see if that helps.
As an update I am getting intermittent signal in some areas, but it's really spotty and only lasts a little while : (
I'll be giving different basebands a try tomorrow but I don't think it'll help much. I'll also try the full factory flash posted above.
Same problem here, had the phone for about 2-3 months, bought it off Kijiji, I tried flashing 4.2.2, went back to 4.3, flashed every baseband and still no success. The SIM works perfectly in another N4, tried a few other sim in mine and still the same results. Any other ways somebody got this fixed ?
QuebecFanat1c said:
Same problem here, had the phone for about 2-3 months, bought it off Kijiji, I tried flashing 4.2.2, went back to 4.3, flashed every baseband and still no success. The SIM works perfectly in another N4, tried a few other sim in mine and still the same results. Any other ways somebody got this fixed ?
Click to expand...
Click to collapse
I'm talking to the seller, see if the phone is still under warranty. My other options would be to change the antenna myself (see if it works), or resell it at loss for spare parts, or wait to see what eBay says.
Just to give you guys some hope, that this is not just a problem faced by second hand phones - My phone is bought directly from the Play store - I contacted Google service a few days back and they asked me to return the phone for a replacement. Only problem is I have to ship this back to the US (where I purchased from), since they dont provide replacement service outside the country of purchase. I'm in India now.
I've tried absolutely everything myself. Flashed many many radios, 4.3, 4.2.2, I'm only able to get it to the point where there is network coverage, I can make and receive calls but there is no in call audio, nor is there any mobile internet connectivity (Only through wifi).
Something tells me this is a problem with the latest OTA update that caused this issue - I was completely stock and everything was working properly, when this problem appeared one fine day - It started with me not able to connect to the mobile internet network for a few days, and then one fine morning, BAM. No service. It was only after this that I started flashing and re-installing stuff on my phone, desperately trying everything to get the phone back to normal again.
I think the last OTA update somehow "bricked" the radio (dont know if something like this is possible, just a noob guess). My only hope is the 4.4 update has some fix for this, else I'm going to try the unbrick method mentioned on these forums to see if that works. Only then will I take the pain to send this back to the US.
What's the unbrick method you are planning to follow?
I was considering using the unbrick method listed here : http://forum.xda-developers.com/showthread.php?t=2347060
Although I'm not completely sure it will work. Do you or anyone else have any suggestions for this ? I'm hoping 4.4 gets released ASAP, I'll download and root that as quickly as I can, hopefully Google has some resolution to this stupid problem
i have exactly the same problem
i have exactly the same problem. i bought my phone at US from Google play.
the phone worked fine for two month and then i got - No Service, and its swipe in a sec to emergency call only.
i try to replaced some sim cards, and factory reset with no success.
i also read a bug report that opened in Google : 58317
they told that there is a problem with the radio interface and radio driver at the 4.3 update, and they will fix it in 4.4 kitkat version.
i hope that 4.4 will fix this terrible problem, if not the phone is totally a door blocker..
Did anyone ever find a solution for this issue?
My friend has this problem with his Nexus 4.
I've searched A LOT and to this day (half a year later) haven't been able to find someone who reports this problem was solved.
I've also tried every suggestion I could find: flashed every stock image available, tried every combination of stock/custom ROM/recovery/radio, even tried the unbrick method mentioned above.
Nothing helps. I always get the same symptoms:
- Radios 54 and below - no in call audio.
- Radios 83 and above - Baseband unknown, IMEI / IMEI SV unknown, no cellular reception.
Also, RMA is not an option because the people at the store (a) don't know how to fix it and (b) claim the warranty doesn't cover this issue so they won't replace the device.
Any suggestions? I'm willing to try anything...
Maybe its a simple hardware failure like a loosely connected antenna? It doesn't really seem to be connected to any specific software setup
Something that happens to me rarely: when I'm in an area with very low/no reception sometimes the phone won't reconnect itself again and just stay on no reception until I reboot. Only happens like one or two times a month though.
Sent from my Nexus 4 using xda app-developers app
Thanks, but I really don't think it could be an antenna issue.
I can see how a malfunctioning antenna could cause cellular reception problems, but it shouldn't affect IMEI or Baseband version readings. Those things have nothing to do with the antenna.
Also, the fact that the symptoms change with different radio firmwares says there's a big chance this is a software issue after all.
I just can't figure out what the cause is and how to eliminate it.
Flash any full factory image. If the problem persists after you can be pretty sure it's hardware. No signal for most of the time and occasionally picking it up could be something as simple as the antenna being unplugged, which can sometimes happen after a drop, or a forgetful repair.
NoobNexus said:
I was considering using the unbrick method listed here : http://forum.xda-developers.com/showthread.php?t=2347060
Although I'm not completely sure it will work. Do you or anyone else have any suggestions for this ? I'm hoping 4.4 gets released ASAP, I'll download and root that as quickly as I can, hopefully Google has some resolution to this stupid problem
Click to expand...
Click to collapse
Guys... mine is signalless too... any progress on this? :crying:
michalhainc said:
Guys... mine is signalless too... any progress on this? :crying:
Click to expand...
Click to collapse
Could be a broken or badly connected antenna. They are very fragile. Have a look at how to replace the antenna maybe?
Sent from my Nexus 4 using Tapatalk
sp99 said:
Could be a broken or badly connected antenna. They are very fragile. Have a look at how to replace the antenna maybe?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
yup I am waiting for the ordered tools to break into it and look around...
michalhainc said:
yup I am waiting for the ordered tools to break into it and look around...
Click to expand...
Click to collapse
I've opened up lots of my old phones (not my nexus 4 yet) and its normally easy to find and change as it's separate from the motherboard and looks basically like a piece of plastic!
Sent from my Nexus 4 using Tapatalk
I have the same problem no connection but the phone recognize the sim and the number of the phone. I've tryed to return to stock using a factory firmware but I'm not able to fix the problem... (this morning is working fine and my phone never fell down or something like that)
If I open btw the case and try to remove and reinsert correctly the antenna the phone will recognize the signal?
I've looked everywhere but haven't found a proper solution. I have an international D802 which after a lot of effort I was able to flash to KK but the touchscreen no longer functions properly - eg pressing one area would register one or more touches in anther area making it impossible to use the phone. If anyone has any idea to fix this please let me know. I have tried various roms including going back to a JB rom and the problem persists.
Thank you.
taikonaut said:
I've looked everywhere but haven't found a proper solution. I have an international D802 which after a lot of effort I was able to flash to KK but the touchscreen no longer functions properly - eg pressing one area would register one or more touches in anther area making it impossible to use the phone. If anyone has any idea to fix this please let me know. I have tried various roms including going back to a JB rom and the problem persists.
Thank you.
Click to expand...
Click to collapse
Even i am having the same exact problem which you have, i searched and didn't get any solutions yet.
Hi, I had an issue like this when I flashed the wrong tot file. It went away upon using the right one. whatever method you used, did you make sure to use the right files?
sjk971005 said:
Hi, I had an issue like this when I flashed the wrong tot file. It went away upon using the right one. whatever method you used, did you make sure to use the right files?
Click to expand...
Click to collapse
i flashed using KDZ files, i flashed right file, still having those problems
taikonaut said:
I've looked everywhere but haven't found a proper solution. I have an international D802 which after a lot of effort I was able to flash to KK but the touchscreen no longer functions properly - eg pressing one area would register one or more touches in anther area making it impossible to use the phone. If anyone has any idea to fix this please let me know. I have tried various roms including going back to a JB rom and the problem persists.
Thank you.
Click to expand...
Click to collapse
Anything worked for you?
I think we have following options:
1. Use mouse via USB otg to get to debugging mode to turn on adb than flash recovery and rom
2. Use mouse via USB otg to update the touchscreen driver via the hidden menu
3. Warranty
Can you get your device in adb mode?
Just managed to install recovery using autorec and lots of patience however touchscreen issues persist even in recovery (the touches are not accurate in recovery) so i think i will need to flash kernel as i think thats where the touchscreen drivers are.
Managed to flash CloudyG3. Still no good. The thing is that the touch is broken in CWM which means that its not the ROM, it's something else. I don't really understand the technical aspects but flashing Cloudy also flashes the kernel. Almost given up on this, too much time sunk.
taikonaut said:
Managed to flash CloudyG3. Still no good. The thing is that the touch is broken in CWM which means that its not the ROM, it's something else. I don't really understand the technical aspects but flashing Cloudy also flashes the kernel. Almost given up on this, too much time sunk.
Click to expand...
Click to collapse
I also had same issue and I flashed alot of different .KDZ and other custom ROMs too but the problem was always there.. so I went to the repair shop and he said that its a problem of eMMC chip so that needs to be fixed.. I have given the phone to him to fix it ...
taikonaut said:
Managed to flash CloudyG3. Still no good. The thing is that the touch is broken in CWM which means that its not the ROM, it's something else. I don't really understand the technical aspects but flashing Cloudy also flashes the kernel. Almost given up on this, too much time sunk.
Click to expand...
Click to collapse
Had taken it to LG service center, they said there is problem with touch screen and have to repair it
navispidey said:
Had taken it to LG service center, they said there is problem with touch screen and have to repair it
Click to expand...
Click to collapse
I have just got a call from the guy and he said that touch needs to be repaired I am really regretting changing the ROM on that phone
Mr.KiLLeR said:
I have just got a call from the guy and he said that touch needs to be repaired I am really regretting changing the ROM on that phone
Click to expand...
Click to collapse
did you given it to lg service center or local service shops?
navispidey said:
did you given it to lg service center or local service shops?
Click to expand...
Click to collapse
Local service shop
Sent from my LG-D802 using Tapatalk
Mr.KiLLeR said:
Local service shop
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Then even i will look here to get it repair in local service shops since i don't have a warranty
Did you guys try updating the touchscreen firmware via the hidden menu? This is so frustrating, I've rooted/romed at least 5 phones/tablets and this is the first time Ive bricked something.
taikonaut said:
Did you guys try updating the touchscreen firmware via the hidden menu? This is so frustrating, I've rooted/romed at least 5 phones/tablets and this is the first time Ive bricked something.
Click to expand...
Click to collapse
I am trying to go to the hidden menu and its not working at all .. So I will just have the touch replaced
I am not entirely convinced its the screen to be honest. I feel like replacing the screen does nothing about the software which control its behaviour. Just my 2c - if you want to go ahead with it perhaps get them to take responsibility - e.g., I replace the screen on your advice and if it doesn't fix the problem I shouldn't have to pay for the screen otherwise you might be throwing your money at a problem which we dont necessarily know the cause of.
Edit: Get a lgd panel not a jdi.
taikonaut said:
I am not entirely convinced its the screen to be honest. I feel like replacing the screen does nothing about the software which control its behaviour. Just my 2c - if you want to go ahead with it perhaps get them to take responsibility - e.g., I replace the screen on your advice and if it doesn't fix the problem I shouldn't have to pay for the screen otherwise you might be throwing your money at a problem which we dont necessarily know the cause of.
Edit: Get a lgd panel not a jdi.
Click to expand...
Click to collapse
Ofcourse, if the guy is saying that after replacing the touch , it will be fixed and you pay 5000PKR then obviously i will check the phone before buying it otherwise i will not pay.. Simple
Digitiser or actual screen?
taikonaut said:
Digitiser or actual screen?
Click to expand...
Click to collapse
No idea about that .. he said to replace the touch
Hello everyone! So my problem aroused a few days ago when I noticed my phone would randomly reboot and get stuck on the boot screen. I would have to mess around and finally only to get a few minutes of usage. I had King Rom installed which I believe was the issue. Fortunately, while trying to use Odin to recovery to stock, it shuts off in the middle of recovery mode. Now I am getting the screen that says: an error has occurred while updating the device software. please use the emergency recovery function in the smart switch pc software. I have been up all night trying to fix this with no results. I am so upset because I rely on my phone for my job as I am a delivery driver. I can't afford a new phone right now and I don't know what to do. It seems like I am pretty much SOL. I am hoping someone will be able to help me! Thanks so much
Somehow I was actually able to restore it to stock successfully in Odin. But before it will finish the initiation process it reboots over and over and the issue persists. Could there be another factor as to why this has happened?
slimspittle said:
Somehow I was actually able to restore it to stock successfully in Odin. But before it will finish the initiation process it reboots over and over and the issue persists. Could there be another factor as to why this has happened?
Click to expand...
Click to collapse
Well, if you're unlucky it might as well be a hardware related failure.
If you look through XDA, there are more and more people having the boot loop problem right now (me included).
Especially after the latest December FW update.
I would try to do a emergency restore through SmartSwitch, then factory reset.
That's the last thing I tried, although it didn't help me in the end and now my mobile is back at Samsung for repair.
If it still bootloops after these steps I think you're out of luck and have to contact a Samsung repair center.
slimspittle said:
aroused
Click to expand...
Click to collapse
Arose is the word i think you were looking for!!
MisterKanister said:
Well, if you're unlucky it might as well be a hardware related failure.
If you look through XDA, there are more and more people having the boot loop problem right now (me included).
Especially after the latest December FW update.
I would try to do a emergency restore through SmartSwitch, then factory reset.
That's the last thing I tried, although it didn't help me in the end and now my mobile is back at Samsung for repair.
If it still bootloops after these steps I think you're out of luck and have to contact a Samsung repair center.
Click to expand...
Click to collapse
Well my phone is the International from Kenya and I'm not sure if Samsung will honor the warranty. I am able to get to the point where you add your Google account. From that point, it gets stuck at ''just a sec''. From that point, it starts to freeze. I guess somehow the phone is still messed up. Think I should try flashing it again?
Do you have TWRP or any custom recovery, does it freeze when your in that menu? Do you have an external SD inside?
dude9946 said:
Do you have TWRP or any custom recovery, does it freeze when your in that menu? Do you have an external SD inside?
Click to expand...
Click to collapse
No I do not anymore and it freezes when the firmware has loaded and it says optimizing apps. And yes I do have a an SD Card
Long shot... have you tired booting up the phone without the card in? It's really sounding like a hardware problem, maybe GPU if it gets triggered reliably...
dude9946 said:
Long shot... have you tired booting up the phone without the card in? It's really sounding like a hardware problem, maybe GPU if it gets triggered reliably...
Click to expand...
Click to collapse
So this time I actually retried Odin with stock restored from a different website. Then bypassed adding a google account. From that point, I no longer got to the ''just a sec'' screen. I was actually able to fully set up the device. I am assuming it will still have issues occasionally. We will see though. I am very lucky because I go to work in a few hours and would miss out on so much tips! Thanks everyone for your support! If the phone still has problems after a restore how do you get a hold of Samsung if its an International phone. Do you have to send it back to the country of origin?
Samsung may decide that you need to contact the country of origin, I know for example Sony stopped supporting international phones in their repair centers last year... While you have the phone up and running try to get some diagnostic info on why its happening.
dude9946 said:
Samsung may decide that you need to contact the country of origin, I know for example Sony stopped supporting international phones in their repair centers last year... While you have the phone up and running try to get some diagnostic info on why its happening.
Click to expand...
Click to collapse
How would I go about doing that?
slimspittle said:
How would I go about doing that?
Click to expand...
Click to collapse
you could get CPU-Z from the app store and take screenshots.
Although i dont thing that would help, just call the samsung support line and select to go to phones and explain whats happening. you wont have to send the phone back to the country of origin.
Cyber5hark said:
you could get CPU-Z from the app store and take screenshots.
Although i dont thing that would help, just call the samsung support line and select to go to phones and explain whats happening. you wont have to send the phone back to the country of origin.
Click to expand...
Click to collapse
I agree you should call Samsung, However you might* still need to send it back to its Origin... It's totally up to Samsung's current policy on supporting international phones. Due to cost, a lot of repair centers really only keep parts/new phones for the ones locally available. However, It's also possible that they are able to contact their international warehouse for parts... So who knows ¯\_(ツ)_/¯ Keep us updated though, other users in your situation would love to know what happens!
dude9946 said:
I agree you should call Samsung, However you might* still need to send it back to its Origin... It's totally up to Samsung's current policy on supporting international phones. Due to cost, a lot of repair centers really only keep parts/new phones for the ones locally available. However, It's also possible that they are able to contact their international warehouse for parts... So who knows ¯\_(ツ)_/¯ Keep us updated though, other users in your situation would love to know what happens!
Click to expand...
Click to collapse
Okay so now it is stuck in a bootloop even after restoring to Odin again. I will try to get a hold of Samsung to see what they say. If not, I paid for my phone with my Wells Fargo Credit card and they have insurance. May get a replacement through them if Samsung won't help
So I just called them and they said to go into my local Samsung store within Best Buy to have them reflash the firmware lol. Going to take it their now to see what happens. Wish me luck
slimspittle said:
So I just called them and they said to go into my local Samsung store within Best Buy to have them reflash the firmware lol. Going to take it their now to see what happens. Wish me luck
Click to expand...
Click to collapse
Ha! did you tell them you already tried... good luck, keep us updated!
@slimspittle dont let us down, we need an update!
Okay so to send it in to Samsung(No charge for software issue as they said) they want a receipt with the IMEI on it. I bought the phone from Amazon and their is no IMEI on the receipt.
Hello everyone,
I've been experience a very ugly issue with my S7 Edge.
SCENARIO 1: When the sensor works (meaning when I can see in the screen what the camera "sees") and I try to take a picture, the camera throws an error message saying "Unknown error occurred", and then the phone reboots:
SCENARIO 2: In other occasions, the camera starts with a complete black screen and immediately throws this error:
One of the two scenarios above always happen, which basically means I'm never able to take a picture.
What I've tried so far:
1) Upgrade from Marshmallow to Nougat.
2) Reset settings.
3) Full phone reset (cache + data).
4) Phone reset from recovery mode (cache + data).
5) The issue are present in safe mode as well.
6) I tried downloading other camera apps. Errors again.
7) Tried changing the storage location from SD to Device. Didn't work.
8) Video recording works!!!!!
Is it a hardware problem in your opinion? How can a software issue still stay after a hard reset? I'm not sure because in SCENARIO 1 I can see that the sensor works, plus video recording works!
Any help is greatly appreciated!
FIXED by using ODIN and flashing Nougat with the CSC file
Maybe try flashing full stock rom through odin or smart switch since there might be a problem to the system files itself.
In my opinion though, this seem like a hardware problem.
Sent from my SM-G935F using Tapatalk
The problem re-appeared.
I also think it's a hardware problem. I'm just gonna send it back to Samsung.
IssamGS2 said:
The problem re-appeared.
I also think it's a hardware problem. I'm just gonna send it back to Samsung.
Click to expand...
Click to collapse
I've been having the exact same issue for months now. On 6.0, 6.0.1 and 7.0 as well.
Please let me know what Samsung tells you. The problem for me is that I bought the phone from amazon (8 months ago) and live in Argentina.
One thing I can't understand is that camera worked fine for the first couple of months. Also find really strange the fact that I'm able to take pictures with flash ON. Have you tried it?
ignaciogh said:
I've been having the exact same issue for months now. On 6.0, 6.0.1 and 7.0 as well.
Please let me know what Samsung tells you. The problem for me is that I bought the phone from amazon (8 months ago) and live in Argentina.
One thing I can't understand is that camera worked fine for the first couple of months. Also find really strange the fact that I'm able to take pictures with flash ON. Have you tried it?
Click to expand...
Click to collapse
I tried some days ago with the flash ON, and it didn't work (if I remember correctly). I didn't waste too much time, and as soon as I found out about the issue I sent it to Samsung for repair.
I have it back since today afternoon, and what I read from the attached papers is that there was a malfunctioning piece which they replaced. The list of operations Samsung did is:
- Boardswaping
- Software update (I doubt about this one as my phone was already updated)
I really think you should contact Samsung directly, and not Amazon. Here in Europe they have a good repair program: after max. 3 business days you get your phone back (and they will do the pick-up, and delivery). Maybe it's the same in Argentina.
Good luck!
IssamGS2 said:
I tried some days ago with the flash ON, and it didn't work (if I remember correctly). I didn't waste too much time, and as soon as I found out about the issue I sent it to Samsung for repair.
I have it back since today afternoon, and what I read from the attached papers is that there was a malfunctioning piece which they replaced. The list of operations Samsung did is:
- Boardswaping
- Software update (I doubt about this one as my phone was already updated)
I really think you should contact Samsung directly, and not Amazon. Here in Europe they have a good repair program: after max. 3 business days you get your phone back (and they will do the pick-up, and delivery). Maybe it's the same in Argentina.
Good luck!
Click to expand...
Click to collapse
Thanks for the info!
Do you know which board did they swap? The main board? :S
Argentina doens't handle international devices. I'd have to take the phone to de US .
I'll try to get it repaired here anyways.
Thanks again por the info.
ignaciogh said:
Thanks for the info!
Do you know which board did they swap? The main board? :S
Argentina doens't handle international devices. I'd have to take the phone to de US .
I'll try to get it repaired here anyways.
Thanks again por the info.
Click to expand...
Click to collapse
I'm sorry, I don't have that info. They did not specify.
So I have a china mode IN2020 that was working great.
I am in the US.
After One Plus sent down an upgrade to Andriod 11 I started had issues with the phone.
The text messages took forever to load and trying to send them was a waste of time. I changed the text message program and solved that issue.
Then the phone starts doing weird things, I would go to dial and it would just right back to the phone screen, programs crashed, etc.
The last problem was the phone now is useless the speaker (does not matter if I use the speakerphone, earpiece or Bluetooth) Is DEAD during a call. the person on the other end of the call hears me fine but, I hear nothing.
One plus says it is because of the motherboard not working with the US upgrade.
They want to charge me $350 to replace it with a US version.
I have since flashed it back to Andriod 10 and again it works perfectly.
I have also tried TWRP to flash to a custom ROM but the phone will NOT flash.
I get errors like wrong Andriod version or a check sum error occured.
Any help or suggestions...
thanks!!
If / when you upgrade to 11 I would highly recommend a factory wipe afterwards..
Jumping between bases causes issues and a wipe fixes them, at least in my case.
It's like jumping between ROMs, always best to have a fresh start.. 10-11 isn't any different, it's possible a mod may have caused it.
So if you had viper running on 10 then you updated to 11 and didn't disable it it could have borked it, or there could have been left over remnants of it left behind..
Again a wipe would help here
I was/am running stock ROM.
and thanks but I did do a factory reset.
dladz said:
If / when you upgrade to 11 I would highly recommend a factory wipe afterwards..
Jumping between bases causes issues and a wipe fixes them, at least in my case.
It's like jumping between ROMs, always best to have a fresh start.. 10-11 isn't any different, it's possible a mod may have caused it.
So if you had viper running on 10 then you updated to 11 and didn't disable it it could have borked it, or there could have been left over remnants of it left behind..
Again a wipe would help here
Click to expand...
Click to collapse
Sirtronicsskg said:
I was/am running stock ROM.
and thanks but I did do a factory reset.
Click to expand...
Click to collapse
How did you update the phone? Via system?
Grab oxygen updater and get it from there.
No reason why it shouldn't work
the phone updated automatically (via One Plus)
but after that did not work i downgraded it to 10 and then tried it again with the same result.
My understanding is the phone has a different motherboard, it is an IN2020.
They say it runs a different os...
dladz said:
How did you update the phone? Via system?
Grab oxygen updater and get it from there.
No reason why it shouldn't work
Click to expand...
Click to collapse
Sirtronicsskg said:
the phone updated automatically (via One Plus)
but after that did not work i downgraded it to 10 and then tried it again with the same result.
My understanding is the phone has a different motherboard, it is an IN2020.
They say it runs a different os...
Click to expand...
Click to collapse
The board strictly speaking shouldn't mean you don't get audio? That's just wrong..
Personally I haven't used the Chinese version of the 1+8pro but if an update is available then it should accept it correctly.
I agree, BUT they told me to send it it for a repair and if they replace the motherboard it will cost me $350.When i said the update should work no matter where i am the answer i received was if you are in the US and get that update it can cause issues.
dladz said:
The board strictly speaking shouldn't mean you don't get audio? That's just wrong..
Personally I haven't used the Chinese version of the 1+8pro but if an update is available then it should accept it correctly.
Click to expand...
Click to collapse
I don't think there's anything wrong with the update itself, I highly doubt it, but you can try downloading the update from Oxygen Updater and install it again, make sure you factory reset right after finishing.
If it doesn't work, then I think it might be something with your hardware, couldn't be something else I suppose
Ys I did that also and same result.
It this phone goes to Andriod 11 it has the speaker issue, No matter how it gets there..
TickedBid said:
I don't think there's anything wrong with the update itself, I highly doubt it, but you can try downloading the update from Oxygen Updater and install it again, make sure you factory reset right after finishing.
If it doesn't work, then I think it might be something with your hardware, couldn't be something else I suppose
Click to expand...
Click to collapse
Sirtronicsskg said:
I agree, BUT they told me to send it it for a repair and if they replace the motherboard it will cost me $350.When i said the update should work no matter where i am the answer i received was if you are in the US and get that update it can cause issues.
Click to expand...
Click to collapse
They're wrong, just putting that out there.
So what are you meant to do?
Are they suggesting if you were in the devices homeland then it would work?
If so just use a VPN, install it and prove them wrong because they're chatting bubbles.
They ought to just fix it.
I already had this "fight with them"
got this today
Greeting from OnePlus.
This email is regarding your repair request RMA# OP202012290204583075 for OnePlus 8 Pro.
I see that you have created a repair request for the OnePlus 8 Pro device due to the earphone malfunction. We certainly understand the need and importance of having the device working in an optimal condition. We are here to assist you.
We would like to keep you informed that we will be able to repair all components apart from the motherboard. After inspection, if we find it to be an issue with the motherboard we will be unable to proceed further with the repair as it is a Chinese version and due to region difference and unavailability of the motherboard, the device will be sent back without repair.
Also, we are glad to inform you that we have approved your repair request. If you would like to continue with the above repair options you can follow the shipping instructions and send the device for repair. If not, you can revert us so that we can get the repair request canceled.
this is BS!!!
dladz said:
They're wrong, just putting that out there.
So what are you meant to do?
Are they suggesting if you were in the devices homeland then it would work?
If so just use a VPN, install it and prove them wrong because they're chatting bubbles.
They ought to just fix it.
Click to expand...
Click to collapse
Sirtronicsskg said:
I already had this "fight with them"
got this today
Greeting from OnePlus.
This email is regarding your repair request RMA# OP202012290204583075 for OnePlus 8 Pro.
I see that you have created a repair request for the OnePlus 8 Pro device due to the earphone malfunction. We certainly understand the need and importance of having the device working in an optimal condition. We are here to assist you.
We would like to keep you informed that we will be able to repair all components apart from the motherboard. After inspection, if we find it to be an issue with the motherboard we will be unable to proceed further with the repair as it is a Chinese version and due to region difference and unavailability of the motherboard, the device will be sent back without repair.
Also, we are glad to inform you that we have approved your repair request. If you would like to continue with the above repair options you can follow the shipping instructions and send the device for repair. If not, you can revert us so that we can get the repair request canceled.
this is BS!!!
Click to expand...
Click to collapse
Tbh pal they wouldn't have Chinese boards there.
I honestly cannot see them doing any ad-hoc soldering, so if taking it apart and putting it back together doesn't fix it or changing the earpiece and speaker modules then they'll send it back.
Give it a shot there not much you can do.
How come you bought a Chinese version? Cost?
I'm not going to send it in because it is a motherboard component issue that happened only with Andriod 11, so why waste my time and be without a phone.
I honestly got it as a gift and did not know it was the in2020.
dladz said:
Tbh pal they wouldn't have Chinese boards there.
I honestly cannot see them doing any ad-hoc soldering, so if taking it apart and putting it back together doesn't fix it or changing the earpiece and speaker modules then they'll send it back.
Give it a shot there not much you can do.
How come you bought a Chinese version? Cost?
Click to expand...
Click to collapse
Sirtronicsskg said:
So I have a china mode IN2020 that was working great.
I am in the US.
After One Plus sent down an upgrade to Andriod 11 I started had issues with the phone.
The text messages took forever to load and trying to send them was a waste of time. I changed the text message program and solved that issue.
Then the phone starts doing weird things, I would go to dial and it would just right back to the phone screen, programs crashed, etc.
The last problem was the phone now is useless the speaker (does not matter if I use the speakerphone, earpiece or Bluetooth) Is DEAD during a call. the person on the other end of the call hears me fine but, I hear nothing.
One plus says it is because of the motherboard not working with the US upgrade.
They want to charge me $350 to replace it with a US version.
I have since flashed it back to Andriod 10 and again it works perfectly.
I have also tried TWRP to flash to a custom ROM but the phone will NOT flash.
I get errors like wrong Andriod version or a check sum error occured.
Any help or suggestions...
thanks!!
Click to expand...
Click to collapse
I am having this same issue with the IN2020 version.
What files are you using to go back to Android 10?