yashsingh1/xdaforums huggingface dataset:
[Lenovo Yoga Tab 3 Plus Questions & Answers] Salurala:
Hi,

I have two questions concerning the Lenovo Yoga Tab 3 Plus and would be very happy about any answers.

I bought the Lenovo Yoga Tab 3 Plus a few days ago and got it delivered from Amazon. After a few days I noticed there is a white noise / hissing coming from the speaker in some recording (most prominently, voice recordings) if the volume is set very low.

Through my researches, I came across the LineageOS ROM and found a note in this post which seems to adress exactly the probem I experience.

Now my two questions are:

1. Is this a problem with all devices or just some? From the existence of a software fix, I would conclude all. This is important to me, because then there is no point at all in sending it back to Amazon for a new device. I still have some doubts due to the fact that a lenovo supporter told me via telephone that it must be a single case however contradicting many voices on the internet and the existence of the previous linked note in the patch notes (and he didn't seemed that convincing to me).

2. Is the problem completely, 100% fixed with this ROM in all devices?

Thank you very much in advance.
[Lenovo Yoga Tab 3 Plus Questions & Answers] muscleolove:
Hi, I can't say for Lineage 'cause I haven't installed it yet, but this is a well known issue among users of the Yoga Tab 3 Plus (myself included). Don't bother trying to change your tablet.

I am pretty convinced this is a software issue and am hoping it is fixed in Lineage.
[Lenovo Yoga Tab 3 Plus Questions & Answers] jonboi:
I have this issue too. I just learned to live with it, however, if you turn off Dolby Atmos, the noise is reduced.
[Lenovo Yoga Tab 3 Plus Questions & Answers] alamo76:
As far as I can tell, it's the Atmos processing boosting the audio signal. Like [MENTION=2771789]jonboi[/MENTION] mentioned, turn it off (or you can also tweak the peaks in the equalizer, if you want to leave it on).
[Lenovo Yoga Tab 3 Plus Questions & Answers] BigBrotherMotown:
I had the same hissing noise...after some tinkering I discovered that it is coming from the DOLBY ATMOS app. I would only hear the noise when I had Dolby turned On And it would immediately STOP when I turned it off.
[Lenovo Yoga Tab 3 Plus Questions & Answers] BigBrotherMotown:
Actually I found the SPECIFIC SOURCE.

In the Dolby Atmos settings there is a switch for "volume leveler"... For some reason having this ON causes a tremendous amount of HISS.... Turn it OFF and the hissing disappears!
[Moto X4 Questions & Answers] taloras:
Hi friends,

I have a new Moto X4 1900-1 that I picked up several weeks ago (standard unlocked version, not Amazon), been working beautifully. Stock aside from magisk flashed/bootloader unlocked, still on stock ROM w/stock recovery.

Been having unrelated hardware trouble with it lately, and was trying to restore it to factory settings prior to sending it in for warranty work...but I fear I've bricked it somehow.

Steps taken:

USB debugging disabled in dev settings

OEM unlock disabled in dev settings

Developer options switched off in dev settings

Magisk completely uninstalled within app

Device rebooted via magisk uninstall

On device reboot, I've got the dreaded "Your device is corrupt. It can't be trusted and will not boot." screen, as if the system is still somehow modified. So, I'm now in a state where the bootloader is locked, but the phone won't boot, not even to recovery.

On trying to boot it to TWRP from fastboot, I get the same "Device is corrupt" screen, and if I try to flash partitions (boot, recovery), I get a "(bootloader) flash permission denied" message. I'm unable to unlock the bootloader again via fastboot oem unlock (unlock code) or fastboot flashing unlock, both of which give me this message: "(bootloader) Check 'OEM unlocking' in Android Settings > Developer Options".

I really did like this phone when it was working, which was for all of a couple weeks. I backed up what I needed before starting all of this, so I don't care about data loss, just want to restore it to factory fresh.
[Moto X4 Questions & Answers] bcrichster:
fastboot flash your factory FW
[Moto X4 Questions & Answers] taloras:
That's a negative, ghost rider.

https://xdaforums.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 on following this guide, downloading/extracting the stock image and using the included batch file to flash all, every partition tried returns the following error in Fastboot:

sending 'x'

writing (x)

(bootloader) flash permission denied

FAILED (remote failure)
[Moto X4 Questions & Answers] bcrichster:
Try without Window's batch file thing..?? The new FW may have files of a different name that the cmds may need adjusting for..
[Moto X4 Questions & Answers] taloras:
No joy. The batch file starts with "fastboot flash partition gpt.bin" (which works), but the next one, "fastboot flash bootloader bootloader.img" fails thusly:

target reported max download size of 536870912 bytes

sending 'bootloader' (9520 KB)...

OKAY [ 0.218s]

writing 'bootloader'...

(bootloader) Validating 'bootloader.default.xml'

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) flash permission denied

(bootloader) Cancelling 'bootloader.default.xml'

FAILED (remote failure)

finished. total time: 0.272s
[Moto X4 Questions & Answers] bcrichster:
Can you post a screenshot of the file listing of extracted FW? I'd like to do a file-name comparison, maybe helpful
[Moto X4 Questions & Answers] taloras:
Firmware download: PAYTON_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Files:

boot.img

bootloader.img

BTFM.bin

dspso.bin

flashfile.xml

fsg.mbn

gpt.bin

logo.bin

NON-HLOS.bin

oem.img

PAYTON_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt

regulatory_info_default.png

servicefile.xml

slcf_rev_d_default_v1.0.nvm

system.img_sparsechunk.0

system.img_sparsechunk.1

system.img_sparsechunk.2

system.img_sparsechunk.3

system.img_sparsechunk.4

system.img_sparsechunk.5

system.img_sparsechunk.6

system.img_sparsechunk.7

system_other.img
[Moto X4 Questions & Answers] bcrichster:
Strange.. I usually just use Linux & add "sudo" to the beginning of flash cmd for perms issues. They may have changed something else, somewhere
[Moto X4 Questions & Answers] taloras:
Let me try this from Linux, then. Though, this does seem to be a permissions issue being squawked back at me from Fastboot and not from Windows...
[Moto X4 Questions & Answers] taloras:
Definitely not a Windows problem.

[IMG="ubuntu fastboot"]https://lh3.googleusercontent.com/vq-W_uqszl2XETlEFLbOLmqhcIX2qIkSGzCOt7orTVLmH1YtvcDExJyXUUs6WHRdjnmQwR6QPYBYMPzJLbwBn_5flQMgWSbvI8fyqo-OWI9YqxdZF4mFqpxpsyvRnabUue99WIXxSvmVmFKJb-c9r5GEYm69v4xI5vSQ7b8ICd76zfw_iXK37OMAzjT15BiLXl5n96vpuou57k4fXGMixxZ6KzEiQnNnSdxSzIxbJdFBl85LdjaHvML7PoY_dugQTzaBbAWikRLGL2E6pQXamqh1KrKNvhvKSqof04cfCJFLaF_aiAo6BcFXmkV_5Oumfv994TEAdd4LnHJPwxmAp7H6o1P29GwCaN1A3k2R65u6admuJKoAzpY2Pu-e19fLzpzYjkh60LZN3U2h31SZODzGBzzIz056xL-okGM9K1nhuoXFLhNo75BjlQggCZzH-JmpoJzhlOWLI_RLYh6ocBoF70W1JzkNDZpBqxG_Kwl8i26C73iymvqO-EICRhagXyxJLuk74creNPYa65spV4Qq-QEILkwJTmcdaAysuwDXm5cWbwX_uOyZuJUQB-nJfw3ds27IjPgH3Ixu8yKNi55203KDnt2VuYvhA1CVTr10PbS1p5QLTQDTTOTyqjbkQ394LLaNKKvvnGu6BqYvBJRThOMQuLSNCqvSSClsjkaTS1bU3lozyBQEH9lYX3bDOGDNnIZuVwAP-kFDYhA=w734-h650-no[/IMG]
[Moto X4 Questions & Answers] bcrichster:
Any possibility there isn't a bootloader partition or maybe it has different name..??
[Moto X4 Questions & Answers] cango123:
Do you remember your latest installed rom? The bootloader you want to flash has to be newer or at least the same, furthermore you can try it on a older machine with USB 2.0 ports, I had the same problem with "permission denied" on USB 3.0/3.1 ports and new mainboards
[Moto X4 Questions & Answers] taloras:
How can I check for partitions from Fastboot? As I can't even boot to recovery, I'm limited in what I can do to fastboot commands, which unfortunately doesn't include any adb shell use.
[Moto X4 Questions & Answers] cango123:
Firmwares can be found here (but unfortunately I can't find a 28.46-21-15 build):

https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/

https://androidfilehost.com/?w=files&flid=229118&sort_by=date&sort_dir=DESC (official motorola account)

Use these commands:

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot erase modemst1

fastboot erase modemst2

fastboot flash bluetooth BTFM.bin

fastboot flash dsp dspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash system_b system_other.img

fastboot flash oem oem.img

fastboot erase carrier

fastboot erase userdata

fastboot erase ddr

fastboot oem fb_mode_clear

If you get an error with something like "partition not found", change the "fastboot flash modem NON-HLOS.bin" command to "fastboot flash

modem_a

NON-HLOS.bin" for all commands where you get this error.
[Moto X4 Questions & Answers] taloras:
Yeah, the most recent I see is 21-12, with a 10-09 upload date on androidfilehost (earlier than the kernel build date of whatever firmware I'm currently running). Might have to wait a few days until some kind soul uploads something more recent. I'll try this one on that other PC, just to dot my Is and cross my Ts.
[Moto X4 Questions & Answers] cango123:
Good luck man, I hope it works
[Moto X4 Questions & Answers] taloras:
No luck. flash partition gpt.bin works, but flashing anything after that fails with either "invalid partition name" or "permission denied".

C:\Users\Paul\Desktop\Peyton>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.000s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.141s]
Finished. Total time: 0.281s

C:\Users\Paul\Desktop\Peyton>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.687s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.766s

C:\Users\Paul\Desktop\Peyton>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (94843 KB) OKAY [ 4.970s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 5.157s

C:\Users\Paul\Desktop\Peyton>fastboot flash modem_a NON-HLOS.bin
Sending 'modem_a' (94843 KB) OKAY [ 2.612s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 2.643s
[Moto X4 Questions & Answers] cango123:
Damn.. well then let's wait till someone uploads a newer fw and hope that it will work, I am running out of ideas for now..
[Moto X4 Questions & Answers] DarkLara:
Are you using the latest version of fastboot?

https://developer.android.com/studio/releases/platform-tools

latest build PAYTON_OPWS28.46-21-16:

https://moto.netlib.re/payton/
[Moto X4 Questions & Answers] taloras:
I am using the latest version of fastboot. Thanks for the link to that more recent firmware, I'll try that now!
[Moto X4 Questions & Answers] taloras:
No luck, even when using 21-16.

C:\Users\Paul\Desktop\Peyton>fastboot oem fb_mode_set
OKAY [ 0.021s]
Finished. Total time: 0.031s

C:\Users\Paul\Desktop\Peyton>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.000s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.125s]
Finished. Total time: 0.156s

C:\Users\Paul\Desktop\Peyton>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.271s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.344s
[Moto X4 Questions & Answers] johnjingle:
Try downloading mfastboot: https://androidfilehost.com/?fid=95916177934532795

It works when you run into these problems, at least in my experience. I have had numerous times when the fastboot in platform tools package was giving me errors.

Let us know.
[Moto X4 Questions & Answers] taloras:
No luck with mflashboot.

C:\Users\Paul\Desktop\Peyton>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (37 KB)...
OKAY [ 0.030s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.143s]
finished. total time: 0.173s

C:\Users\Paul\Desktop\Peyton>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (9520 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.332s

C:\Users\Paul\Desktop\Peyton>mfastboot flash modem_a NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem_a' (94863 KB)...
OKAY [ 2.547s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.568s
[Moto X4 Questions & Answers] cango123:
Can you boot into recovery?
[Moto X4 Questions & Answers] taloras:
As I mentioned in OP, I can't boot in to recovery, get the same "cannot be trusted" message as a regular boot. I can't boot the stock recovery or boot twrp via "fastboot boot recovery.img", both return the same "cannot be trusted" message.
[Moto X4 Questions & Answers] cango123:
Ohh damn, didn't see that...
[Moto X4 Questions & Answers] taloras:
Still open to ideas here ?
[Moto X4 Questions & Answers] gee one:
It looks like your bootloader was relocked and because of whatever customization, the boot signature is no longer valid. You can't unlock the bootloader without booting into the rom first to change the settings in the dev menu.

I think the only hope might be EDL mode, but I'm not sure if there is a way to get into it. I've only gotten there from bad flashes.
[Moto X4 Questions & Answers] oxxo.andatti:
Help

me paso lo mismo llevo mas de 5 dias intentando buscar una solucion pero nada hasta ahorita. si alguien tiene tiempo y puede buscar una solucion se los agradeceria mucho. saludos

the same happened to me over 5 days trying to find a solution but nothing until now. If someone has time and can find a solution, I would greatly appreciate it. regards

https://ibb.co/qMdnWnC
[Moto X4 Questions & Answers] vidra:
This just means that you have your booloader locked, try running fastboot oem unlock <> and then flash it.
[Moto X4 Questions & Answers] oxxo.andatti:
Habilitar desbloqueo oem

Ya intente ejecutar ese comando y se muestra un mensaja que hay que habilitar desbloqueo oem desde el sistema android. al menos que exista una opcion de habilitar desbloqueo oem desde fastboot

I already try to execute that command and it shows a message that you have to enable unlock oem from the android system. unless there is an option to enable oem unlock from fastboot

https://ibb.co/GVKjTWJ
[Moto X4 Questions & Answers] taloras:
My bootloader is indeed locked: as I mentioned in the original post, I was still running a factory ROM and had no customizations beyond Magisk. Preparatory to sending the phone back in for some warranty work for an unrelated hardware issue, I wiped the phone, switched off OEM unlock and USB debugging, and uninstalled Magisk. Some part of system is apparently still modified, given the phone's "cannot be trusted" message at boot.

On trying to run "fastboot oem unlock", I get a "enable oem unlocking in settings" message back...which, of course, I can't do, since the phone won't boot.
[Moto X4 Questions & Answers] taloras:
I suspect at this point, unless there's some way I can switch the oem unlock flag from fastboot, I need to get the phone in to a state where I can either blank flash it, or get it in to EDL mode.
[Moto X4 Questions & Answers] oxxo.andatti:
help solution

alguien tiene alguna idea de como solucionarlo, ya llevo varios dias sin ningun resultado

someone has some idea of ​​how to solve it, it has been several days without any results :crying:
[Moto X4 Questions & Answers] oxxo.andatti:
alguna solución

alguna solucion
[Moto X4 Questions & Answers] TeamRainless:
I've got WAY too many questions:

1. What was the "unrelated hardware issue"?

2. What do you mean you "wiped the phone"?

3. Is that the EXACT order you did everything in?
[Moto X4 Questions & Answers] taloras:
1: charging port is a little fiddly, tried with multiple cables.

2: wiped the phone, from settings -> reset within the OS, not via something like TWRP -> format.

3: yes, that's the order, if I recall. This was a couple weeks back now.
[Moto X4 Questions & Answers] TeamRainless:
If that is the order you used then you should've left USB debugging alone (it's not against warranty to have USB debugging active) and done the OEM Unlock last. Now you've locked your keys in and the car is one of those fancy S.H.I.E.L.D. models with bullet-proof windows.

If you still have your receipt you could try to just take it back to the store. Failing that I'd advise you to just send it in to Motorola. At this point you've got nothing to lose. Worst they could do is say "No."

At best you might get some nice engineer who decides to overlook your clear violation of warranty and restores your system.
[Moto X4 Questions & Answers] taloras:
There is no need to tell me I goofed; I am aware I goofed. "Doveryai, no proveryai," I should have done these things one step at a time, making sure it didn't think system was still modified before switching off usb debugging and oem unlock, rather than just trusting uninstalling Magisk would bring it back.

I was just hoping, since it's not hard bricked and I still have fastboot access, that there's some way of bringing it back from the brink. You reckon it's well and truly buggered?
[Moto X4 Questions & Answers] TeamRainless:
Well I didn't just SAY "You goofed"...

I explained it the way I did (including metaphors) for a reason.

You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK.

Let's forget about the phone entirely for a moment: How would you get your keys out of that tank?

You WOULDN'T.

There's nothing fastboot can do for you now. There's nothing ANYBODY here can do for you now. Your own research has borne that out. Every command you've tried has returned what result? "Key locked inside. Tank nuclear-resistant."

I can tell you how Motorola would do it... They would just wipe the whole thing and start from scratch. New IEMI number... new everything. They have the ability to sign brand new keys. You don't.

So yeah. That is a WRAP on your end. Time to kick it up to somebody that at least might have a chance to fix it.
[Moto X4 Questions & Answers] taloras:
Why dress it up with metaphors? Nuclear-resistant tank and all that? I understand perfectly well that oem unlock and usb debugging both switched off is why fastboot flash commands are returning "flash permission denied" messages. I even stated the steps leading to my predicament in my first post. Surprise surprise, turning off oem unlock means fastboot will squawk at me "turn on oem unlock" if I try to flash things with it.

I am not asking why I can't flash via fastboot, I understand why I can't, I am asking if I can use my limited fastboot access to get in to the phone some other way, such as putting it in to test/EDL mode as one can with other Qualcomm phones https://alephsecurity.com/2018/01/22/qualcomm-edl-1/ . Someone else in this thread even mentioned once getting in to EDL mode after a bad flash.
[Moto X4 Questions & Answers] gee one:
If you can get into EDL mode, I think you could recover the phone. Someone in the telegram group said press volume up and power at the same time to get into EDL mode. Good luck.
[Moto X4 Questions & Answers] TeamRainless:
I'm a writer. I paint pictures with words. :)

But if you want the barebones version:

No.

I don't believe you can.

Normally with fastboot access you could... which is why you had all these people saying "try this and try that"... But with the specific steps that you took (which is why I asked), I don't believe there's anything you can do.

There was a thread where somebody discussed reflashing /System or something like that... but, again, because of the order of the steps... I really do not believe there's anything you can do.

You can ask [MENTION=9167870]MotoX4[/MENTION] or the guy that develops Lineage... they might know more than me. (I can't say I ever developed my own ROM)

But just make sure and tell them the order of the steps you took because that's the key. If they don't know of a way... then I don't believe there is one.

Good luck!
[Moto X4 Questions & Answers] MotoX4:
I'm not a developer. True I have contributed some code via Github to a few side projects but am a novelist at best. The current primary developer of Lineage OS for Moto x4 is erfanoabdi and there are other folks who have contributed to Lineage OS. My best skill which I use here on XDA is I'm good at dumbing down and translating "geek speak" into normal English (I'm way better at that than I am at coding anything).

OP -

Odds are your bootloader is indeed locked and everything you could try will fail. You claim you cannot even boot into TWRP which means you really do have a problem (because if you could, I'd suggest you install this https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view ).

You could attempt to download this firmware. https://www.androidfilehost.com/?fid=890278863836292604

Attempt to boot into bootloader (holding down both your power button and lower volume button at the same time). Once at the bootloader run .flash_all.sh as ROOT (do this in Linux). If you keep getting stuck at that error message, stay at the error message, and run the script anyway!

If that fails, you could in the last attempt, visit Motorola's website and use their commands to attempt to unlock your phone. But failing that, I fear you now have an overpriced paperweight (sorry).