Hey folks,
I recently noticed that I get no sound at all through the earpiece of my phone whilst in a call. The only way around this seems to be to enable loudspeaker, which works, but is far from ideal.
The issue I am faced with is that my bootloader is unlocked, and since I applied the OTA 4.4.4 firmware, I cannot re-lock the bootloader until a full 4.4.4 image is available (when attempting, I get a failed verification of the system image).
Has anyone else experienced this issue and found a way to get the earpiece working again? Alternatively, has anyone taken a device back to Tesco with this problem, having an unlocked bootloader, and gotten a replacement/repair?
Thanks in advance.
da2tha3 said:
Hey folks,
I recently noticed that I get no sound at all through the earpiece of my phone whilst in a call. The only way around this seems to be to enable loudspeaker, which works, but is far from ideal.
The issue I am faced with is that my bootloader is unlocked, and since I applied the OTA 4.4.4 firmware, I cannot re-lock the bootloader until a full 4.4.4 image is available (when attempting, I get a failed verification of the system image).
Has anyone else experienced this issue and found a way to get the earpiece working again? Alternatively, has anyone taken a device back to Tesco with this problem, having an unlocked bootloader, and gotten a replacement/repair?
Thanks in advance.
Click to expand...
Click to collapse
Does it work if you downgrade to 4.4.2 ?
Although this is very much sounding like a earpiece fault, happens on the Moto G.
Nope, same issue after downgrade. Just need to get it back into a position where I can get it serviced, really.
Related
Hi guys wanting to update my rooted nvidia shield to version 82, i used the Ramshield v1.1 method to return to stock recovery and rom, however the bootloader still states that it is unlocked.
Now updates all work fine and there are no problems however its just personally bugging me how i change this back to locked.
I've googled, looked all over xda and other forums (Not in any great detail so no shouting at me if I've missed it )
Any help on the matter is appreciated.
blonqe said:
Hi guys wanting to update my rooted nvidia shield to version 82, i used the Ramshield v1.1 method to return to stock recovery and rom, however the bootloader still states that it is unlocked.
Now updates all work fine and there are no problems however its just personally bugging me how i change this back to locked.
I've googled, looked all over xda and other forums (Not in any great detail so no shouting at me if I've missed it )
Any help on the matter is appreciated.
Click to expand...
Click to collapse
Fastboot oem lock if you have the proper stuff installed or you can use my shield setup if you want. However it serves absolutely no purpose, it does not reset the warranty flag.
first of all, i have searched a lot about the issue i am having, i have not found a single one as mine.
XT1033 with locked bootloader
It started with 5.0.2 ota update, the update file was downloaded and flashing was smoothly done, after the final restart it stuck in a boot loop (on the moto logo white coloured). i straight away went to service center and they told me that my motherboard was the issue, needs to be changed for almost the cost of the phone itself.
then i thought of trying somethings from here (xda), found [5.0.2][Restore to Stock][XT1033] Asia Retail [Dual Sim][4.4.2/4.4.2][LockBootloader] i tried flashing stock firmware from this thread not flashing the "mfastboot.exe oem lock begin" and "mfastboot.exe oem lock" part. And the phone started!!!! i was laughing about the motherboard thing
Used it for about 15 days with no bug, no issues, no random reboots, the again one day it simply went into bootloop again, i was sure that there was a hardware issue, but then again i went through the same procedure and it was again working, this same process has happened for about 4-5 times on the last month.
i would like to know:
1. Is it a hardware issue? (service center people will surely make me buy a new motherboard)
2. Is it some kind of issue with the lollipop, downgrading to kitkat will help?
3. any permanent solution (or will i have to format the phone every 10 days?)
any help is very much appreciated.
kaliyaakakallu1 said:
first of all, i have searched a lot about the issue i am having, i have not found a single one as mine.
XT1033 with locked bootloader
It started with 5.0.2 ota update, the update file was downloaded and flashing was smoothly done, after the final restart it stuck in a boot loop (on the moto logo white coloured). i straight away went to service center and they told me that my motherboard was the issue, needs to be changed for almost the cost of the phone itself.
then i thought of trying somethings from here (xda), found [5.0.2][Restore to Stock][XT1033] Asia Retail [Dual Sim][4.4.2/4.4.2][LockBootloader] i tried flashing stock firmware from this thread not flashing the "mfastboot.exe oem lock begin" and "mfastboot.exe oem lock" part. And the phone started!!!! i was laughing about the motherboard thing
Used it for about 15 days with no bug, no issues, no random reboots, the again one day it simply went into bootloop again, i was sure that there was a hardware issue, but then again i went through the same procedure and it was again working, this same process has happened for about 4-5 times on the last month.
i would like to know:
1. Is it a hardware issue? (service center people will surely make me buy a new motherboard)
2. Is it some kind of issue with the lollipop, downgrading to kitkat will help?
3. any permanent solution (or will i have to format the phone every 10 days?)
any help is very much appreciated.
Click to expand...
Click to collapse
Replacing the motherboard is a very bad idea as you can buy a new phone from that money
You can try unlocking the bootloader and flashing a custom ROM
PS- After unlocking BL You can take a backup is your data partition with a custom recovery and then no worries of data loss
So this is not a hardware issue??
kaliyaakakallu1 said:
So this is not a hardware issue??
Click to expand...
Click to collapse
I can't tell you that now because it may be after all a hardware issue
Now
Is your phone in warranty?
Do you have any problem in unlocking the bootloader?
sjandroiddeveloper said:
I can't tell you that now because it may be after all a hardware issue
Now
Is your phone in warranty?
Do you have any problem in unlocking the bootloader?
Click to expand...
Click to collapse
no, the phone is not in warranty.
And about unlocking the boot loader, one option for me was to get a new moto g 2014 with exchange offer on flipkart (i am from india and flipkart is reducing about Rs 3000 for this phone). So i am not sure that if i unlock the boot loader will they accept it??
is there a way to relock it and make it stock?
kaliyaakakallu1 said:
no, the phone is not in warranty.
And about unlocking the boot loader, one option for me was to get a new moto g 2014 with exchange offer on flipkart (i am from india and flipkart is reducing about Rs 3000 for this phone). So i am not sure that if i unlock the boot loader will they accept it??
is there a way to relock it and make it stock?
Click to expand...
Click to collapse
Yes you can lock the bootloader again but that's I think not gonna help because when you unlock your device you need to get the unlock code from Motorola only, so they after all know that you unlocked it once
And buying a second gen moto g is not a good deal at current time as the internals are almost same on both devices and besides you are getting only Rs 3000 off that's not a big amount on money considering that you may still be able to save your device
sjandroiddeveloper said:
Yes you can lock the bootloader again but that's I think not gonna help because when you unlock your device you need to get the unlock code from Motorola only, so they after all know that you unlocked it once
And buying a second gen moto g is not a good deal at current time as the internals are almost same on both devices and besides you are getting only Rs 3000 off that's not a big amount on money considering that you may still be able to save your device
Click to expand...
Click to collapse
thanks for the suggestion.
as soon as i get home, i will look into unlocking bootloader and installing some custom rom, can you recommend any particular rom that you are using, need it as a daily driver (stable one) .
kaliyaakakallu1 said:
thanks for the suggestion.
as soon as i get home, i will look into unlocking bootloader and installing some custom rom, can you recommend any particular rom that you are using, need it as a daily driver (stable one) .
Click to expand...
Click to collapse
And please think before talking any step
I said "you may be able to save your device" and not "you will surely be able to save your device"
Don't blame me if custom ROMs are not able to solve your problem
These things don't always have a desired output
Now if you are ready for some customs things my suggestions to you
* Use either philz touch latest or TWRP from xda ( and not from TWRP's official site)
* For ROMs , if you still want to stick with Motorola's stock ROM you can try custom recovery flashable zip made by @lost101
He made both normal variants and optimised ones
*Or if you wanna use custom ROMs try CM 12.1 latest nightly
*Read properly how to flash everything
*If while flashing anything you see any error in logs report back ( it may be able to tell if there's a hardware fault)
Dear all,
I'm experiencing the infamous screen flickering after I downgraded from 5.0.2 to 4.4.4. Phone (Moto G XT1032) is working fine and the flickering goes away after switching the screen off and on again.
However, after a thorough search through these forums with no answer to my question, I was wondering whether anyone came up yet with a more permanent solution to tackle this problem?
I read it has something to do with the bootloader. While downgrading, I didn't flash the 4.4.4 bootloader (as told) because it could cause a hard brick of my phone. So my second question is; can anyone explain to me why the phone probably hard bricks when you try to downgrade the bootloader? Is there no workaround for this?
Thanks in advance!
Anyone?
I could flash the 4.4.4 bootloader fine when I downgraded. I believe it is required to receive the OTA update (could be wrong). The flickering is most likely caused by the 5.0.2 bootloader. So if you do want to try downgrading it that'll likely fix the problem
Hello! I'm new here and actually the main purpose of my registration on this wonderful website is the amount of helpful and skillful people I saw in various threads I read before, giving me hope for the solution of my problem.
As stated in the title, I'm currently unable to get OTA updates on my phone.
Some time ago I unlocked the bootloader (so my bl is unlocked now) in order to have my Z5 rooted. Apparently something went awfully wrong while flashing the TWRP or perhaps I was just awfully stupid and missed a step... Anyways I ended up without any OS and started searching on the web for some solutions.
I came across FlashTool and XperiFirm, then downloaded and flashed the (at the time) latest firmware, which is the one i currently have (Service Menu shows "GENERIC_32.2.A.0.224"). So now my phone seems perfectly fine: stock rom, no custom recovery (as far as I know), no root privileges. The only problem it shows is the fingerprint hardware that stops working every once in a while; something a simple reboot fixes.
But I have been unable to update since then, with my "software update" tab showing no available updates (nor could I get one via Sony PC Companion, furthermore getting errors while trying fo repair software) while under "diagnostics" it clearly says "new software available".
I just want to get everything back as it was before, and to get my OTA updates to work; I'm not interested in custom ROMs or custom recoveries or SU.
I apologize in advance in case an identical thread had already been opened and closed; I hope you guys can help me solve this mess I did.
Thanks a lot
I found out my problem is connected with the DRM Keys loss caused by unlocking the bootloader. I'll try this out: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
scacio said:
I found out my problem is connected with the DRM Keys loss caused by unlocking the bootloader. I'll try this out: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
Once you have unlocked the Bootloader ota updates don't work EVER only manually flashing the ftf via flashtool will get you updated. If you unlocked the Bootloader without backing up the drm/ta keys then re-lock the Bootloader ota updates will Not work. If you unlock the Bootloader and then re-lock with previously backed up drm/ta keys ota updates WILL work.
The drm fix does NOT replace the missing drm/ta keys it merely tricks the device into thinking that those required for x-reality, low light conditions, and noise reduction in the camera are there to reactivate those features.
Also DO NOT try to use a other Xperia devices drm/ta keys on your own unless you want a permanent paperweight.
Sent from my Xperia XA using XDA Labs
Ah, so I should have backed those up before unlocking the bootloader. It seems I'll have to spend a few minutes on flashtool every once in a while to get updates, nevermind.
Anyway is it worth it to try this DRM fix? I did not notice any changes to the quality of the camera.
And another noob question: if I flash this "modified kernel" will my device be wiped? Or I just flash it, reboot the phone and enjoy DRM features?
Just a quick update to let you know, I have installed the drm fix and rooted, the funny thing is that now I receive ota updates.. But of course I'm unable to install them. Not that I want them anyway, so no problem. I have reconsidered the potentiality of a rooted device and started to appreciate the benefits; thanks for the help
Hello everyone ..
I have oneplus 8 with unlocked bootloader and rooted all was good but after relock bootloader and back to stok the fingerprint doesn't work , i get massage Enrollment was not completed, i tried flash rom again and unlocked bootloader but still not working i don't have any idea for this issue, please can you help me to solution this issue ? :crying:
same problem , up.
I've read the 25 or so pages from here as I'm in the same boat. It looks like a return to OnePlus for repair is the only solution https://forum.xda-developers.com/oneplus-8-pro/help/enrollment-problem-wont-register-t4089787
Hi,
I had the same problem with the fingerprint sensor.
As I received the phone I decided to unlock the bootloader. But as i realized that it'll take a while until TWRP provide a stable recovery, I decided to roll back.
Nothing what i tried (factory reset, etc.) brought the fingerprint sensor back. The OnePlus support couldn't (or didn't want to) help in this regards too.
Since I bought the phone via Amazon (de) I sent it back. I got my money back and bought a new one.
Cheers!
Up up up up
This bug should have never made it past quality control .
If OnePlus even have quality control.
And now you guys get to see first hand how completely **** their customer service is
No solution as yet. I am in the same boat.
Isn't this solved by flashing your (hopefully) backed up persist.img via fastboot?