is any of you having a camera focus issue with the new update 12.5.3.0?
kureijisama9523 said:
is any of you having a camera focus issue with the new update 12.5.3.0?
Click to expand...
Click to collapse
me did you solve it ?
I think my issue with autofocus/ToF problem was from flashing persist.img with twrp and now i think i need to flash the persist with EDL.
Flashing several versions of roms with fastboot does nothing to get ToF corrected.
Can someone send me a working persist.img or will the persist.img found on stock roms work?
xwonic said:
I think my issue with autofocus/ToF problem was from flashing persist.img with twrp and now i think i need to flash the persist with EDL.
Flashing several versions of roms with fastboot does nothing to get ToF corrected.
Can someone send me a working persist.img or will the persist.img found on stock roms work?
Click to expand...
Click to collapse
what is the problem, you have ?
my camera never autofocus, i have blured image
Rovyo said:
what is the problem, you have ?
my camera never autofocus, i have blured image
Click to expand...
Click to collapse
its the same specially during night or dark room, i have to press on screen to focus
I see, so it's not same problem.
You have software issue.
not same as mine, as i never get focus even when i press screen or force manual focus.
its always blured one. didn't found a fix i may change camera to see if this will solve my
xwonic said:
its the same specially during night or dark room, i have to press on screen to focu
Click to expand...
Click to collapse
Related
I am using moto g3 x1550. A few months ago my scree was broken and make it replaced but it was not original. But it work perfect on L.P (5.0) based ROM but when I install M.M (6.0) based ROM touch does not work as from the starting from the language setup but only volume and power key are working and also display but not touch...
Plzzz help me up.
If your screen isnt original then chances are your device will be rejected to be serviced at moto center.
edit : http://forum.xda-developers.com/showpost.php?p=66002023&postcount=1262 try flashing these zip files and see if your touch screen is back.
Else you can try downgrading to lollipop or reflashing stock MM images and see if your touch screen is working. Use this linkhttp://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to flash stock images. Note: data loss might occur backup data that is important.
vimjam said:
If your screen isnt original then chances are your device will be rejected to be serviced at moto center.
edit : http://forum.xda-developers.com/showpost.php?p=66002023&postcount=1262 try flashing these zip files and see if your touch screen is back.
Else you can try downgrading to lollipop or reflashing stock MM images and see if your touch screen is working. Use this linkhttp://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to flash stock images. Note: data loss might occur backup data that is important.
Click to expand...
Click to collapse
Is it safe. I mean that my phone could get had brick or permanently touch not work after flashing that file.
Sorry for bad English?
Piyush Garg said:
Is it safe. I mean that my phone could get had brick or permanently touch not work after flashing that file.
Sorry for bad English
Click to expand...
Click to collapse
hmm this can also be a hardware problem as the touchscreen in not generic and we do not know how it will react to the drivers, so noting cannot be guaranteed. Your best bet is to take a leap of faith and flash the zip, if it fails you can always return to lollipop roms.
That flashable zip just replaces touch drivers not the entire rom. Besides that flashable zip was created by Alberto97 who brought us CM13 so i highly doubt that flashable zip will brick your phone.
But none the less if you truly want a fail safe procedure your best bet is moto service.
p.s no one at xda is responsible for anything happening to any device as this is a community not a paid service where we are responsible for our work.
vimjam said:
hmm this can also be a hardware problem as the touchscreen in not generic and we do not know how it will react to the drivers, so noting cannot be guaranteed. Your best bet is to take a leap of faith and flash the zip, if it fails you can always return to lollipop roms.
That flashable zip just replaces touch drivers not the entire rom. Besides that flashable zip was created by Alberto97 who brought us CM13 so i highly doubt that flashable zip will brick your phone.
But none the less if you truly want a fail safe procedure your best bet is moto service.
p.s no one at xda is responsible for anything happening to any device as this is a community not a paid service where we are responsible for our work.
Click to expand...
Click to collapse
Which one should be flashed.
Now I am using cm12.1 so can I flash these zip in it or first I flash cm13 and and flash these zip.
And if pH get brick then will it be hard brick or soft..
thanks :thumbup:
Piyush Garg said:
Which one should be flashed.
Now I am using cm12.1 so can I flash these zip in it or first I flash cm13 and and flash these zip.
And if pH get brick then will it be hard brick or soft..
thanks :thumbup:
Click to expand...
Click to collapse
if it gets bricked it will be soft brick , you can go to twrp wipe & flash cm again. these drivers are for cm13 so you need to flash after cm13 is flashed or along with cm13.
the first zip is to restore to older stable drivers , so flash this first . If the touch screen didn't improve flash the second one to restore to default drivers.
Im facing too.. Try BrokenOS.. No issues in that rom!
vimjam said:
if it gets bricked it will be soft brick , you can go to twrp wipe & flash cm again. these drivers are for cm13 so you need to flash after cm13 is flashed or along with cm13.
the first zip is to restore to older stable drivers , so flash this first . If the touch screen didn't improve flash the second one to restore to default drivers.
Click to expand...
Click to collapse
Same problem touch is not working
After flashing both file..of drivers
Piyush Garg said:
Same problem touch is not working
After flashing both file..of drivers
Click to expand...
Click to collapse
Touch issue is an hardware related problem. Motorola IT say me that IT is an hardware problem exasperated by MM update (and related synaptics drivers).
Imho it is due by bad grounded IC or by the glue used to bind the LCD at motherboard
IMP_IT said:
Touch issue is an hardware related problem. Motorola IT say me that IT is an hardware problem exasperated by MM update (and related synaptics drivers).
Imho it is due by bad grounded IC or by the glue used to bind the LCD at motherboard
Click to expand...
Click to collapse
Yes I had changed my whole screen and it is duplicate.
Is there is any way to solve this problem plzzz plzzz held..
Piyush Garg said:
Yes I had changed my whole screen and it is duplicate.
Is there is any way to solve this problem plzzz plzzz held..
Click to expand...
Click to collapse
yes. Try this
https://www.dropbox.com/s/jemv0yqjf9m25vm/IMG_20160319_154102989.jpg?dl=0
https://www.dropbox.com/s/dc2pgzrc2lcdnf8/IMG_20160319_154042223.jpg?dl=0
IMP_IT said:
yes. Try this
https://www.dropbox.com/s/jemv0yqjf9m25vm/IMG_20160319_154102989.jpg?dl=0
https://www.dropbox.com/s/dc2pgzrc2lcdnf8/IMG_20160319_154042223.jpg?dl=0
Click to expand...
Click to collapse
How to use this
Piyush Garg said:
Yes I had changed my whole screen and it is duplicate.
Is there is any way to solve this problem plzzz plzzz held..
Click to expand...
Click to collapse
Piyush Garg said:
How to use this
Click to expand...
Click to collapse
it's black humour but it also demonstrate that there is an hw problem. If you try to put an aluminium foil in back cover of your moto g the touch issue disappears completely. But it also may modify SAR values, reception etc...
But, I say try it so you can see that problem disappear.
IMP_IT said:
it's black humour but it also demonstrate that there is an hw problem. If you try to put an aluminium foil in back cover of your moto g the touch issue disappears completely. But it also may modify SAR values, reception etc...
But, I say try it so you can see that problem disappear.
Click to expand...
Click to collapse
My problem will disappear or my phone?
IMP_IT said:
it's black humour but it also demonstrate that there is an hw problem. If you try to put an aluminium foil in back cover of your moto g the touch issue disappears completely. But it also may modify SAR values, reception etc...
But, I say try it so you can see that problem disappear.
Click to expand...
Click to collapse
Is this really work..
Piyush Garg said:
Same problem touch is not working
After flashing both file..of drivers
Click to expand...
Click to collapse
Piyush Garg said:
Is this really work..
Click to expand...
Click to collapse
Yes it really work but it s not reccomanded
IMP_IT said:
Yes it really work but it s not reccomanded
Click to expand...
Click to collapse
Why??
Piyush Garg said:
Why??
Click to expand...
Click to collapse
Because can modify SAR values and the exposition of body to EM fields
IMP_IT said:
Because can modify SAR values and the exposition of body to EM fields
Click to expand...
Click to collapse
So what problem would I face
Have u tryed it or saw someone doing this
Piyush Garg said:
So what problem would I face
Have u tryed it or saw someone doing this
Click to expand...
Click to collapse
No problem. I tried this. I 'invented' this lol.
Try once it does not cause anithing except different irradiation by EM fields
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
i have the same problem, you fix it?
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
5[Strogino] said:
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
Click to expand...
Click to collapse
yeah, but we dont have the stock boot, we have tha us version c567 and its not online yet
Same problem
Abumarf said:
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
Click to expand...
Click to collapse
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
night_wind said:
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
Click to expand...
Click to collapse
I'm not sure as to what region I flashed but I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing. This is most likely what causes the Fingerprint sensor to no longer work. All we can do is wait for Huawei to release the complete C567 update so we can revert to complete stock.
Abumarf said:
I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing.
Click to expand...
Click to collapse
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
night_wind said:
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
Click to expand...
Click to collapse
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Abumarf said:
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Click to expand...
Click to collapse
I've just ran into this same issue, you think someone could just upload the missing files?
posydon1 said:
I've just ran into this same issue, you think someone could just upload the missing files?
Click to expand...
Click to collapse
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Abumarf said:
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Click to expand...
Click to collapse
That's exactly how I ended up here lol. His method works great but some file are still missing.
posydon1 said:
That's exactly how I ended up here lol. His method works great but some file are still missing.
Click to expand...
Click to collapse
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Abumarf said:
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Click to expand...
Click to collapse
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
night_wind said:
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
Click to expand...
Click to collapse
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Abumarf said:
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Click to expand...
Click to collapse
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
night_wind said:
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
Click to expand...
Click to collapse
I also did just that but just fixed the problem with the Huawei apps and system update by changing a few file names. Works like a charm now. Will wait till Monday and attempt to flash the B167 update. But as of now, I'm fully root, decrypted, and enjoying life!
I bought OPO recently which was in hard bricked stage. Ever since i unbricked it there is no option of front camera in any of the applications. I tried N number of roms but did't help. Only once i had the option to use front camera, that to only for few minutes.
Then the same issue, can any one please help to fix this thing. I have also attached screenshots for reference.
Thanks.
Have you tried to flash the very original stock KitKat roms?
The one that requires you to "flash-all" via cmd and locks the bootloader and all..
GuitarGuy96 said:
Have you tried to flash the very original stock KitKat roms?
The one that requires you to "flash-all" via cmd and locks the bootloader and all..
Click to expand...
Click to collapse
I have tried, but i hope i have not tried rom which locks the bootloader. If possible can you please provide the link for the same.
Applying now...
Xda need an update too lol
Are touch screen issues present on the latest October build when using TWRP? I know hyp and rpm were updated last month, just curious if that touch issues remains on this newer build in TWRP?
Does magisk work after this Update?
Sorry guys can't answer ur questions cause I'm on stock locked bootloader not planning on modifying my phone.
All i can say for now that the phone feel faster and scrolling is better.
Did you ever have bluetooth issues and if so, did the patch happen to address the issue?
Alexis96312 said:
Does magisk work after this Update?
Click to expand...
Click to collapse
Yes, no issues with Magisk. But, I came from a clean fastboot flash and redid twrp and Magisk.
Topdroid01 said:
Did you ever have bluetooth issues and if so, did the patch happen to address the issue?
Click to expand...
Click to collapse
I would lose connection to my car after a few minutes but other devices worked fine. With the October update I connected to my car no problem and it held for well over an hour a reconnected just fine after getting out and back in. So I would say yes, the patched helped my Bluetooth issues.
how do you apply the normal image through the other or through twrp or through what? Sorry
Enviado desde mi PH-1 mediante Tapatalk
Notch settings are back under developer settings
garywojdan81 said:
Notch settings are back under developer settings
Click to expand...
Click to collapse
How to use full screen with Youtube? I see no difference on different options.
mcdull said:
How to use full screen with Youtube? I see no difference on different options.
Click to expand...
Click to collapse
pinch zoom out
I don't know how this feature worked in Oreo because I bought the phone when Pie was released. But on Pie and Firefox I don't get any difference with the notch settings.
Edit: Same for Chrome.
Pinch to zoom
resaik said:
Pinch to zoom
Click to expand...
Click to collapse
Maybe I'm blind and just don't see it, but what shall happen? Notch area has same color than the app, that's all what I notice. I believed e. g. the box where to enter the URL will be "behind" the notch or similar?
Edit: Maps works as my expectation: additional screen where the map is shown.
mcdull said:
How to use full screen with Youtube? I see no difference on different options.
Click to expand...
Click to collapse
That's a separate thing with the YouTube app. Just expand the screen by stretching it with multitouch during video play.
I'm rooted with Magisk but keep saying "Stock Backup does not exist". How can I fix this??
Yup, "Use Notch" doesn't work like it did on Oreo, and now I cant go back to Oreo from Pie. I fastboot flash Orea and after booting to the setup screen touch is unresponsive. UGH..
elinca247 said:
Yup, "Use Notch" doesn't work like it did on Oreo, and now I cant go back to Oreo from Pie. I fastboot flash Orea and after booting to the setup screen touch is unresponsive. UGH..
Click to expand...
Click to collapse
You have to unlock critical partitions then reflash the fastboot files. The critical partitions house the touchscreen firmware.
Alexis96312 said:
I'm rooted with Magisk but keep saying "Stock Backup does not exist". How can I fix this??
Click to expand...
Click to collapse
just flash back to stock and reapply twrp and magisk. remember to use the twrp-sept.img as temp image.
Fastboot command
Ascertion said:
You have to unlock critical partitions then reflash the fastboot files. The critical partitions house the touchscreen firmware.
Click to expand...
Click to collapse
Can you please provide the fastboot command to unlock the critical partions?
disregard found command. thanks for the reply.
My camera glitches when recording, or when using any app that uses camera.
https://www.youtube.com/watch?v=8hIzof5EkMg
Can I switch rom from MIUI global 12.0.3 (QJGEUXM) to QJGMIXM? Apparently the camera doesn't glitches on that rom
If so can anyone please guide me on the steps I should take?
Bozdo said:
My camera glitches when recording, or when using any app that uses camera.
https://www.youtube.com/watch?v=8hIzof5EkMg
Can I switch rom from MIUI global 12.0.3 (QJGEUXM) to QJGMIXM? Apparently the camera doesn't glitches on that rom
If so can anyone please guide me on the steps I should take?
Click to expand...
Click to collapse
Yes, you can. Download fastboot ROM for Global QJGMIXM and flash it using MiFlash tool (unlocked bootloader need it).
Alin45 said:
Yes, you can. Download fastboot ROM for Global QJGMIXM and flash it using MiFlash tool (unlocked bootloader need it).
Click to expand...
Click to collapse
Thanks man
I hope this will fix my camera issue. If I change the rom will I have problems with the warranty in case I want it sent back to the seller?I imagine that switching back to the original is doable?
Bozdo said:
Thanks man
I hope this will fix my camera issue. If I change the rom will I have problems with the warranty in case I want it sent back to the seller?I imagine that switching back to the original is doable?
Click to expand...
Click to collapse
I don't think will affect warranty....and yeah, you can switch between different region ROMs, no problem.
Just dont forget you cant lock bootloader on a different rom because you Will brick the phone
And also backup your persist.img. Fastbooting around version is not recommended as it doesn't flash persist.img which is different between China/global/eu roms.
Apparently I need to root the phone in order to get the persist.img
And this is the method I found:
From computer:
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
Any of you unlocked their phone fast without having to wait 168 hours? XiaoMiTool V2 seems to unlock it fast but should I trust in Pajeet?
Camera still glitches even on QJGMIXM
I think you camera module problem. Not from software.