Hello everyone
I would like to ask. So i have Mi 6 128GB variant and right now I'm having problem with the (i think) microphone. So the problem is when i place a call, the other side can't hear me, also when i try to record something the voice result will be so small, and i have to speak from a very close distance. And when using ok google i also have to speak from a very close distance. It seems the problem is not in the hardware. I bought it about a month ago, and when i just bought it i tried to flash to unofficial LOS ROM, the first one that appeared is the calling problem. So i tried to flash different kind of custom ROM, mostly LOS (because there are several version from different developer) and AOSP Extended. All is same, the microphone seems not functioning properly. And at one point i try to go back to MIUI 8.2.2.0. At that time i notice the phone displaying the message that the IMEI is lost. So i tried different kind of way to restore the IMEI mostly through flashing qcn. Right now the IMEI is back, but it's not my original IMEI, when i restore my original IMEI, the MEID is different from the original one, because i use qcn fthat i obtained from web, so maybe the MEID from the original qcn still intact. So right now i tried to flash the unedited qcn to see whether the problem is solved. But it's still same.
Any help will be really appreciated
Hi ,i have this problem with the mic also the solution is to install a new rom with full format ,and NOT active the google assistant,thats what make the problem for me.
good luck
hac12 said:
Hi ,i have this problem with the mic also the solution is to install a new rom with full format ,and NOT active the google assistant,thats what make the problem for me.
good luck
Click to expand...
Click to collapse
Hi bro, by full format do u mean the "format data" option in TWRP?
fuqiangyang said:
Hi bro, by full format do u mean the "format data" option in TWRP?
Click to expand...
Click to collapse
hi, yes thats right,
sorry for the late answer
hac12 said:
hi, yes thats right,
sorry for the late answer
Click to expand...
Click to collapse
Thanks bro, but i just realized that the real problem is the sticker that covering the mic holes! So there was a kind of warranty sticker that is stick to the phone and covered almost all the mic holes, and when i removed it the mic is going back to normal...I never thought the is the issue, lol
Should i delete this thread?
Related
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
Hi, apparently some genius developing CWM decided it would be fun to allow the factory partition to be formatted with the newest versions of CWM (I'm on 6.0.4.6). Well guess what, I managed to format it on my GNex (it's quite easy to do actually).
Anyways, I've lost my IMEI data and unable to access mobile network (data connectivity is fine, however, surprisingly). Somebody please help me restore my IMEI because I don't have a nandroid backup either.
Thanks a lot!
Deleted, did a search on IMEI and found a bunch of threads. Reading them now...
pherder said:
Deleted, did a search on IMEI and found a bunch of threads. Reading them now...
Click to expand...
Click to collapse
Paul how did you manage to mess up your phone? Was it the same way I did? The thing is, all is not lost, I'm absolutely certain of that. It's not a brick until it absolutely and completely refuses to power up...
@osm0sis, can you please help me out here? I know there was even an IMEI changing tool but most probably considered illegal or something by the "powers that be" and hence removed most likely. I just need my original phone IMEI back, that's all. Thanks a lot!
rahimali said:
Paul how did you manage to mess up your phone? Was it the same way I did? The thing is, all is not lost, I'm absolutely certain of that. It's not a brick until it absolutely and completely refuses to power up...
@osm0sis, can you please help me out here? I know there was even an IMEI changing tool but most probably considered illegal or something by the "powers that be" and hence removed most likely. I just need my original phone IMEI back, that's all. Thanks a lot!
Click to expand...
Click to collapse
I think I screwed up and flashed my phone with the wrong image (LTE instead of CDMA) that wiped the factory info and all the attempts I have tried do not do anything to get the phone back. I have a nice tablet that just upgraded to 4.3 via WiFi since it isn't on the Verizon network.
Paul
pherder said:
I think I screwed up and flashed my phone with the wrong image (LTE instead of CDMA) that wiped the factory info and all the attempts I have tried do not do anything to get the phone back. I have a nice tablet that just upgraded to 4.3 via WiFi since it isn't on the Verizon network.
Paul
Click to expand...
Click to collapse
My maguro CWM thread has all the info you need explained several times. Check it out.
osm0sis said:
My maguro CWM thread has all the info you need explained several times. Check it out.
Click to expand...
Click to collapse
i have gone through your cwm thread. it's suggested taking it to a shop and getting it fixed with spt box or something. unfortunately, i can't do that because nobody in my location has anything even remotely similar to one of those. apart from that, i've done everything i could think of, flashed radios, flashed stock samsung rom, flashed google factory images. what else would you suggest?
i don't have a prior nandroid either
Resolved
Problem solved. Took it to repair shop and got it fixed. Everyone that helped or tried to help, thanks a lot! Mods please close thread, thanks!
I was thinking more along the lines of restoring a backup and grabbing what you need to fix Factory from Radio, which was detailed a couple of times.
Glad you got it fixed, nonetheless. :good:
rahimali said:
Problem solved. Took it to repair shop and got it fixed. Everyone that helped or tried to help, thanks a lot! Mods please close thread, thanks!
Click to expand...
Click to collapse
Did you ask them how they fixed it?? we need to know so we can help others..:--))
osm0sis said:
I was thinking more along the lines of restoring a backup and grabbing what you need to fix Factory from Radio, which was detailed a couple of times.
Glad you got it fixed, nonetheless. :good:
Click to expand...
Click to collapse
i didn't have a nandroid, nothing in factory since i had wiped it accidentally via the new cwm's new ""feature". i didn't like twrp until now but i ain't budging from it now that cwm has screwed me up so bad!
buhohitr said:
Did you ask them how they fixed it?? we need to know so we can help others..:--))
Click to expand...
Click to collapse
the guy connected it to a couple of external devices which in turn were connected to his pc, i guess one of them was something along the lines of an spt box, the other thing looked like a miniature spaceship, so maybe ET was involved in fixing it as well...
Not CWM's fault, though I definitely understand your sentiment. But "with great power.."
I make damn sure I know what I'm pressing Yes on when I'm wiping.
osm0sis said:
Not CWM's fault, though I definitely understand your sentiment. But "with great power.."
I make damn sure I know what I'm pressing Yes on when I'm wiping.
Click to expand...
Click to collapse
with great power comes great tragedy
anyways, I was just browsing through my phone with root explorer and with twrp's file manager and surprisingly there's no efs folder there! is that normal?
i've taken a twrp nandroid backup to include efs as well but i'm thinking to take a raw backup as well as described here. i've also copied the /factory and /data/radio folders.
i was wondering whether flashing a stock samsung ROM might result in the creation of the efs folder? on yakju 4.2.2 stock google image right now...
Nah efs is the partition but it's mounted to /factory :good:
osm0sis said:
Nah efs is the partition but it's mounted to /factory :good:
Click to expand...
Click to collapse
That's great thanks!., I'll clean flash 4.3 yakju in a day or two and see if the IMEI sticks after the wipes. Unfortunately, I wasn't able to backup using EFS Commander or the terminal/shell commands (got error both ways) so I'm hoping the TWRP backup (without MD5) and manual file copy should be sufficient insurance...
I recently bought an Optimus G (Korean Model F180L) and followed this guide : (symbianize) /showthread.php?t=1103182 * to convert it to the E975.
I used the NEU/EUROPE OPEN kdz file, and everything is working perfectly, except ONE thing; when I try to call someone, there is no ringing sound. Then when they answer, I can't hear them.
Is this a software fault? I really don't know much about this type of stuff, what should my next course of action be? Any advice would be gratefully received!
*sorry, it won't let me post the full link due to low post count
I like dags said:
I recently bought an Optimus G (Korean Model F180L) and followed this guide : (symbianize) /showthread.php?t=1103182 * to convert it to the E975.
I used the NEU/EUROPE OPEN kdz file, and everything is working perfectly, except ONE thing; when I try to call someone, there is no ringing sound. Then when they answer, I can't hear them.
Is this a software fault? I really don't know much about this type of stuff, what should my next course of action be? Any advice would be gratefully received!
*sorry, it won't let me post the full link due to low post count
Click to expand...
Click to collapse
Are you sure that your variant is f180L? and you flash correct baseband successfully?
sunyakram said:
Are you sure that your variant is f180L? and you flash correct baseband successfully?
Click to expand...
Click to collapse
Yep, definitely F180L. And I'm pretty sure the baseband flashed properly. I have signal with my network, and can make and connect calls. They can hear me speaking too, but I can only hear them if they're on loudspeaker :S
Sorry to repost, but I really need some help! Does anyone have any suggestions of things I could try at all?
Is it likely that the firmware would cause this problem? Or is it probably a hardware issue?
If anyone has any idea pleeeeeeease let me know
I like dags said:
Sorry to repost, but I really need some help! Does anyone have any suggestions of things I could try at all?
Is it likely that the firmware would cause this problem? Or is it probably a hardware issue?
If anyone has any idea pleeeeeeease let me know
Click to expand...
Click to collapse
flash a rom and check again,
sunyakram said:
flash a rom and check again,
Click to expand...
Click to collapse
Aaaaah! I tried to flash a CyanogenMod rom using a guide on True Android, and got to the part where I had to flash ClockworkMod Recovery. Having installed it, the phone no longer starts up! It just keeps saying 'Secure booting Error! Cause: boot certification verify'
I googled that phrase and came up with some other people having similar problems, but there seems to be a million different proposed solutions and I haven't a clue where to start.
I had no idea this would be so difficult!
Terry try another one, stock based, savvy rom v4 or 5x ,
Put rom in ur internal memory, goto recovery,do a full wipe, flash rom , reboot.
sunyakram said:
Terry try another one, stock based, savvy rom v4 or 5x ,
Put rom in ur internal memory, goto recovery,do a full wipe, flash rom , reboot.
Click to expand...
Click to collapse
Thank you for your help, but I can't do what you suggested. It's permanently stuck on the 'Secure booting Error' screen, even when I pressed the volume + power buttons to try a hard reset, the same problem occurs.
So think about kdz again
sunyakram said:
So think about kdz again
Click to expand...
Click to collapse
Ok, so I managed to get CM 11 working. The problem persists, so I'm assuming the ear speaker is faulty.
Thanks again for your help, please excuse my utter incompetence
I like dags said:
Ok, so I managed to get CM 11 working. The problem persists, so I'm assuming the ear speaker is faulty.
Thanks again for your help, please excuse my utter incompetence
Click to expand...
Click to collapse
how its faulty right after flash?
sunyakram said:
how its faulty right after flash?
Click to expand...
Click to collapse
Do you mean what's wrong with it?
There's no sound through the ear speaker when calling people. The only way to hear what they say is with headphones or loudspeaker.
I like dags said:
Do you mean what's wrong with it?
There's no sound through the ear speaker when calling people. The only way to hear what they say is with headphones or loudspeaker.
Click to expand...
Click to collapse
no i mean your ear speaker is working fine before flashing,and right after flashing new firmware it stop working so i think its not about hardware failure.
Hello XDA, this is my first post, this comunity is awesome and helped me a lot for a couple of years now.
there always seems to be a solution to everything!
but now i realy ****ed up. i accidentaly checked the wrong thing on the so called "smart phone flash tool"
i klicked firmware upgrade instead of download only.
is there any way so rescue my phone? thank you very much in advance! :crying:
here is a screenshot: (i cant paste link because i am new):crying:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
charliepie said:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
Click to expand...
Click to collapse
there probably is SOME way to fix it, i am sure, but the phone does not even boot into recovery.
Mediatek phones are hard to brick, haha
It is PROBABLY going to give a headache in order to find the needed files, flash the stuff again and etc using the proper way, but PROBABLY your phone will relive again. Try rooting and installing Eragon after a full wipe, if that option is available.
You may look here:
Bricked P8000
This may help.
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
abubakar486 said:
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
Click to expand...
Click to collapse
hi, thank you; but my phone does not even boot. it gets recognized by the pc though
New problem
OKAY now i got everything working so far. but there is a new real big problem. it has some kind of imei error so it doesnt let me use data on the way
how can this be fixed? i mean, i have the correct imei s right here whith me.
thank you in advance.
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
FIXED
charliepie said:
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
Click to expand...
Click to collapse
Hey! i fixed it. again fith XDAs help
http://forum.xda-developers.com/canvas-a1/general/fix-imei-perfect-fix-android-imei-t2943567
solution 2 worked for me.
Also i have a new problem. when connecting my bluetooth speaker it says...well maybe this belongs to another forum :good:
Hello guys!!I have installed chinese twrp and unfortunately, I have wiped efs partition done without knowing me, now there was no signal at all,i have installed stock rom for "N" number of times but still then no sign of signal.IMEI showing 00.kindly help me guys
vishaldroid said:
Hello guys!!I have installed chinese twrp and unfortunately, I have wiped efs partition done without knowing me, now there was no signal at all,i have installed stock rom for "N" number of times but still then no sign of signal.IMEI showing 00.kindly help me guys
Click to expand...
Click to collapse
rip
yikes..
There's a lot of warnings throughout the forum to not use the Chinese TWRP, even Alberto said so in his Unofficial TWRP thread, you can't blame anyone but yourself.
vishaldroid said:
Hello guys!!I have installed chinese twrp and unfortunately, I have wiped efs partition done without knowing me, now there was no signal at all,i have installed stock rom for "N" number of times but still then no sign of signal.IMEI showing 00.kindly help me guys
Click to expand...
Click to collapse
New mother board is the only thing that's going to get it back life. Please do not pm I can not help you
efs
efs is working fine but problem is with cellular network.im sorry to bother you flashalltime
vishaldroid said:
efs is working fine but problem is with cellular network.im sorry to bother you flashalltime
Click to expand...
Click to collapse
If your IMEI is wiped there is nothing you can do.
vishaldroid said:
efs is working fine but problem is with cellular network.im sorry to bother you flashalltime
Click to expand...
Click to collapse
Check you sim card, apn's as well, if you can see your IMEI.
efs
yeah, i did but still showing imei 00 and hoping some developer would fix this issue.There are lots of people who are facing this problem.If some developer should see into this matter would be great