yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Q&A, Help & Troubleshooting] Rishabh001:
I wanted to factory reset my phone and I was on marshmallow. I had the update.zip file which I used while upgrading fronm lollipop to marshmallow. I thought that "apply update from sd card" in stock recovery and using that same update.zip would be a better way of doing the Factory Reset. The update's installation was aborted because of Status 7 Error Code and since then my phone is stuck in bootloop. The Moto Logo shows up and an android with the "Erasing" written below it follows and then it goes back and follows the same routine. So how can I restore my phone to stock official firmware on Locked Bootloader? I have never rooted my phone or unlocked the bootloader.

Please Help. I'm dying without my phone.
[X Style (Pure) Q&A, Help & Troubleshooting] lafester:
Since you messed up your phone, at this point you might as well try to flash stock firmware in fastboot. Can't get any worse.
[X Style (Pure) Q&A, Help & Troubleshooting] HikingMoose:
Will he need an unlocked bootloader to be able to fastboot stock? I'm new to Motorolas. But I agree, that you need to follow a typical protocol - applying an update.zip when you are already on the update and you are stock, is not typical. Probably causing the issue. I think you can salvage it, I don't think you cannot recover from it. But I could be wrong. Set up Android SDK and go through the processes you'd need to unlock the bootloader and root. Once you have those set up, you can try to fastboot the lollipop return to stock tool.
[X Style (Pure) Q&A, Help & Troubleshooting] lafester:
Read through the mm release thread. In the beginning there are some posts from locked users who successfully flashed stock firmware to recover from issues.
[Xposed Framework Modules] glauberlima:
Hi everyone.

Ever since my phone got Android 6 update I've noticied an wired behaviour regarding volume slider: it simply won't go away. And I'm not alone... just google it and see.

So if you are in the same boat, give this module a try and leave a feedback :)

WHAT TO EXPECT FROM THIS MODULE?

This module fixes Marshmallow's volume dialog excessive delay on closing. See the post #4 for screenshots.

DOWNLOAD - Xposed Repository

http://repo.xposed.info/module/com.glauber.android.xposed.volumesliderdelayfix

For either feature requests or bugs please use GitHub issues

https://github.com/glauberlima/VolumeSliderDelayFixForMarshmallow/issues

Thanks:

@rovo89 for Xposed Framework

All XDA community

XDA:DevDB Information

Volume Slider Delay Fix for Marshmallow, Xposed for all devices (see above for details)

Contributors

glauberlima

Source Code: https://github.com/glauberlima/VolumeSliderDelayFixForMarshmallow

Xposed Package Name: com.glauber.android.xposed.volumesliderdelayfix

Version Information

Status: Stable

Current Stable Version: 1.0.1

Stable Release Date: 2016-02-12

Created 2016-02-12

Last Updated 2016-04-09
[Xposed Framework Modules] glauberlima:
Changelog

v1.0.1 - 2016-02-12

Initial public version​
[Xposed Framework Modules] glauberlima:
Technical details

Original file: VolumeDialog.java

Original method: computeTimeoutH

Proposed change type: method replacement

Original source code:

CM13: https://github.com/CyanogenMod/andr...com/android/systemui/volume/VolumeDialog.java

AOSP: https://android.googlesource.com/pl...com/android/systemui/volume/VolumeDialog.java

The original method as it is:

private int computeTimeoutH() {
if (mAccessibility.mFeedbackEnabled) return 20000;
if (mSafetyWarning != null) return 5000;
if (mExpanded || mExpandButtonAnimationRunning) return 5000;
if (mActiveStream == AudioManager.STREAM_MUSIC) return 1500;
return 3000;
}

Now, look at the following line within original method:

if (mAccessibility.mFeedbackEnabled) return 20000;

Very suspicious, isn't it? If something related to accessibility is turned on then timeout is set to 20000 ms (20 seconds). We've found the culprit for the delay :)

So my proposed change is simple as that:

private int computeTimeoutH() {
return 1500;
}

Why 1500?

Because it's the lowest value Android has been using at original method.

And that's it :)
[Xposed Framework Modules] glauberlima:
Screenshots

Image 1: When the module is installed volume panel goes away after 1.5 seconds

[IMG="When the module is installed"]https://i.imgur.com/QaohUwd.gif[/IMG]

Image 2: When the module

is NOT installed

volume panel stays active for 20 seconds!

[IMG="When the module is NOT installed"]http://i.imgur.com/tufyr9B.gif[/IMG]
[Xposed Framework Modules] glauberlima:
Reserved 4
[Xposed Framework Modules] FlemishDroid:
Thanks. Is this also needed on CM13? I already use Gravitybox (MM).

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Xposed Framework Modules] gordonpn:
When does this happen? I don't think I've ever experienced this bug before.
[Xposed Framework Modules] fleming222:
I'm getting 'incorrect package name' when trying to download.
[Xposed Framework Modules] glauberlima:
This happens on Moto X2 (and probably the newer models too) running Android 6.

How many seconds does it take to yours to disappears after you increase/decrease volume by using hardware buttons?
[Xposed Framework Modules] XlAfbk:
~3,5s from pressing the button

What timeout does your module set? Configurable?

Edit: 1500ms as I see on Github. Still a tad long imho. Consider adding a UI?
[Xposed Framework Modules] glauberlima:
What's your phone?
[Xposed Framework Modules] glauberlima:
Where is this message being displayed?
[Xposed Framework Modules] XlAfbk:
Nexus 5 on CM13

I've grabbed your code from Github and changed the timeout to 1s in the meantime
[Xposed Framework Modules] glauberlima:
Huum, Maybe this bug affects only Moto's on Android 6.

Without this fix the delay is set to 20 seconds!

It's something to do with Accessibility options.
[Xposed Framework Modules] fleming222:
As a toast message when downloading using the xposed app.

I'm on a Moto X Force and my volume panel takes ~15 seconds to disappear.
[Xposed Framework Modules] joyousfrank:
Same time for volume panel here, Stock 6.0 Moto X Play.

Also getting "incorrect package" error.
[Xposed Framework Modules] Spikedude:
I have a Nexus 6P with Marshmallow 6.01. The delay is 20 seconds before the audio panel disappears. This occurs even though I have GravityBox installed and set the timeout to 5 seconds or less (setting under Media Tweaks).

UPDATE: The following problem has been fixed by the developer!

I also get the message that the "Package name is incorrect" when I attempt to download using Xposed (version 80). Therefore, I haven't been able to test your module yet. Looking forward to trying, though!
[Xposed Framework Modules] glauberlima:
Sorry for inconvenience. I've updated the package. Refresh and you will be able to see v1.0.1 :)
[Xposed Framework Modules] glauberlima:
Sorry for this error. I've updated the package. Could you try again? It will work now!
[Xposed Framework Modules] glauberlima:
[MENTION=1987981]fleming222[/MENTION] the fixed version is up. Refresh and try again. Sorry for this. :(
[Xposed Framework Modules] Spikedude:
Thank you! The module works as described. The audio panel times out after 2 seconds. Well done!

I always hate asking for something more, since it's your time being taken advantage of, not mine, so I'll just throw this out as a suggestion.

For me, 2 seconds is too short (though much better than 20 seconds), but for someone else it might be just right. Therefore, adding the ability to specify a timeout length would be very useful.

Thanks for your efforts and the excellent results! :):thumbup:
[Xposed Framework Modules] joyousfrank:
Hey there, great, thanks for uploading new version, it's working now, this is awesome, no more delay.

Greetings from Mexico!
[Xposed Framework Modules] glauberlima:
[MENTION=4514473]FlemishDroid[/MENTION], if you are experiencing the same issue described in the post #1, just install this module and see if it helps.

If you need any help let me know.
[Xposed Framework Modules] Stryder5:
I have an Moto X Pure Edition (2015). I only experience this bug when accessibility is turned on for Moto Voice. Glad to know there's a fix for it!
[Xposed Framework Modules] glauberlima:
It used to drive me nuts - 20 seconds is too much!
[Xposed Framework Modules] ragnarokx:
Working great on Nexus 6P 6.0.1. Thanks!
[Xposed Framework Modules] Fishawy:
I would like to try that on Galaxy S6 with Android 5.1.1, but I'm getting "package incompatible". Is it exclusive for Marshmallow?
[Xposed Framework Modules] glauberlima:
Yes, it's. This the bug doesn't affect Android 5. But to tell you the truth, I'd say it's completly safe to install it on Android 5. I will attach an special build here as soon as I get home.
[Xposed Framework Modules] glauberlima:
Hi [MENTION=2456449]Fishawy[/MENTION]

Sorry for the delay. Here you go the special LP build:

https://github.com/glauberlima/Volu...er.android.xposed.volumesliderdelayfix.lp.apk

:)
[Xposed Framework Modules] Fishawy:
Thanks a lot! :)
[Xposed Framework Modules] beren:
imagine there is no way to solve this problem on android N...yet

when active the accessibility for keepas2android i have the infamous delay, if i disable it goes back to 2 seconds.
[Xposed Framework Modules] glauberlima:
Did you try this module?
[Xposed Framework Modules] beren:
ehm...android n.....xposed.... XD
[Xposed Framework Modules] glauberlima:
I meant... Volume Slider Module :P

Any error message?
[Xposed Framework Modules] beren:
I don't expect to be able to run xposed on android n, so can't try the module.

Should I do?

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Xposed Framework Modules] glauberlima:
You're right [MENTION=1035665]beren[/MENTION] :)

As soon as Xposed becomes available for Android N I will be able to port this module :)
[Xposed Framework Modules] jonny6pak:
Thank you for this! Is there any way to change the delay value without having to compile the apk myself? Just wishful thinking.
[Xposed Framework Modules] glauberlima:
For sure!

Would you mind openning a issue for your request? Here's the link:

https://github.com/glauberlima/VolumeSliderDelayFixForMarshmallow/issues
[Xposed Framework Modules] Stryder5:
Worked perfectly on my Moto X Pure Edition (Style) on Marshmallow. Thank you so much for this fix!
[Xposed Framework Modules] glauberlima:
Hi [MENTION=2832063]XlAfbk[/MENTION]

This feature is under development:

https://github.com/glauberlima/VolumeSliderDelayFixForMarshmallow/issues/4

:)
[Xposed Framework Modules] RelQM:
Is there an xposed module that sets volume menu timeout to half a second or even less?
[Xposed Framework Modules] R4W1L:
Oneplus 3, cm13 sultan - great Module, exactly what I searched for :)
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
Long story short, I installed Cyanogenmod and TWRP only to be continually bombarded with those stupid warnings Google has recently introduced (the yellow one about the unlocked bootloader and custom ROM and the red one about the software being corrupt) as well as a warning about the software being corrupt after the phone had booted into the ROM. In an effort to get rid of all 3 warnings I started experimenting (couldn't find anything online) and so re-locked the bootloader both via adb as well as via developer options > unmarked "enable bootloader unlocking". Now TWRP is throwing up a password prompt to decrypt the partition and passed that, my phone is no longer able to boot into Cyanogen as it just gets stuck at the boot screen logo.

I've tried wiping Dalvik, cache, system etc. but so far its not many any difference. I thought about installing the vanilla ROM to hopefully bypass it but since I only have access to fastboot mode, I can't use the adb push command to transfer anything to the sdcard.

Am I screwed? :crying:
[Nexus 5X Q&A, Help & Troubleshooting] k.s.deviate:
No you aren't, just enable OEM unlock and USB debugging. And flash a factory image and start over. There may be another way without flashing back to stock but I cant think of it ATM.
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
The problem is I can't do that. Attempting to use the OEM unlock command is blocked by the bootloader setting in the ROM. An oh so nifty feature of android v6. And since I can't boot into the ROM, I don't see anyway of unlocking the bootloader in the first place.

What's truly retarded is that u could do this on any android v6 device. As far as I can tell, it's a replicable way to brick any phone =\
[Nexus 5X Q&A, Help & Troubleshooting] 2x4:
if you can still get into TWRP you're fine. You may lose all of the data in the encrypted partitions though.

if you can't perhaps you can flash via ADB.

for future reference, never do OEM lock if you're not completely stock.
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
I can get into twrp but it doesn't help me any. I can't wipe any partitions because they're encrypted by the locked bootloader. I have no idea what else I can do.
[Nexus 5X Q&A, Help & Troubleshooting] 2x4:
can you flash on top of the locked partitions?
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
I may not be explaining clearly. I have nothing I can flash. With the partitions locked, the .IMG is hidden from twrp. I can't push anything to the sdcard either as I have no way of executing that command whilst in recovery or fastboot mode?
[Nexus 5X Q&A, Help & Troubleshooting] 2x4:
if im not mistaken, you can use an OTG cable and access those files via TWRP
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
Don't know what a OTG cable is. I also don't see the point. The cyaanogenmod IMG is useless as it clearly was never designed to boot on a device with a locked bootloader. Otherwise I'd be able to get into the ROM to begin with.

The only way I see that I can resolve this is by unlocking the bootloader and bypassing the ROM bootloader lock setting without booting into the ROM to do it. That's the lynchpin that's screwing me over.

Thanks for trying to help.
[Nexus 5X Q&A, Help & Troubleshooting] 2x4:
youd have to flash the stock image not the CM image if this was even going to work, since that one can work with the bootloader locked.

this is an otg cable.

[IMG="otg cable usb-c"]http://ecx.images-amazon.com/images/I/51MX0dwuMZL._SX425_.jpg[/IMG]
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
Well the issue there is as I've said before, how can I push the file to the phone when I dont have access to the adb push command? There is no pre exiating vanilla .IMG on the phone. Only the CM .IMG I used in the first place.
[Nexus 5X Q&A, Help & Troubleshooting] 2x4:
I was saying put the stock image on a USB drive, plug USB drive into OTG cable, plug OTG cable into phone, boot into TWRP recovery, mount USB-OTG drive, flash from there
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
Lol. Fun times. If people simply read, these things wouldn't happen.

This ought to work.

http://xdaforums.com/showthread.php?t=3053783
[Nexus 5X Q&A, Help & Troubleshooting] 2x4:
Thanks for the link, Good to know.

I was aware locking it would cause this issue but wasn't aware someone had already found a solution.

thanks!
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
Interesting idea. I bought one (micro USB to USB A) and tried to mount it but no dice. TWRP has 2 radials under selectable storage to mount. Internal and USB OTG. But selecting the "USB OTG" radial doesn't do anything. It doesn't move the highlighted radial to that option. Could it be due to my OTG setup? USB A female to micro USB male to micro USB female to USB C male ( micro usb female to usb c male part came with the phone since usb c is not popular yet).

Edit: OK, i finally figured out a way to transfer files over. No commands required (File explorer to the rescue). That said, does anyone know where I can get a vanilla .img? Googles official page only has them in .tgz. Tried extracting the .tar and then extracting the files in the .tar it and re-compressing in .zip that TWRP can understand (TWRP therefore sees my created zip file) but i just hit an error: "Could not find 'meta-inf/com/google/android/update-binary" etc. when trying to install it.
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
Doesn't work. Error: "Failed (remote: device is locked. cannot erase). I think its coming up against the same issue TWRP's built in formatting functions get hit by in this scenario.

Looks like this solution suffers from the same chicken and egg scenario i'm currently in.

Honestly, now that Google has introduced these spam error messages even when you're able to run CM, it ain't worth it. I may have to abandon CM in favour of vanilla Android seeing as there doesn't appear to be a way around them *sigh*.
[Nexus 5X Q&A, Help & Troubleshooting] SlimSnoopOS:
Use 7Zip if you are on Windows. That will open the tar file and allow you to pull what you need.

Now that you figured out how to transfer files, put a rom zip on your phone and install it via TWRP. Then enable OEM Unlock and USB Debugging. Then do whatever you want with fastboot.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
Have you seen this thread:

http://xdaforums.com/nexus-5x/help/req-help-to-unbrick-t3251740

It may be your only way back.

Spam error messages? Do you mean the bootloader unlock warning that you can easily replace?

You could have used this tool:

http://xdaforums.com/nexus-5x/themes-apps/tool-change-bootlogo-images-imgdata-tool-t3240052

Or flashed this zip:

http://xdaforums.com/nexus-5x/themes-apps/bootloader-theme-material-bootloader-t3298420

*sigh*
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
That's the problem. Its impossible to do that without first unlocking the bootloader. And I can't unlock the bootloader because I can't get into the ROM. And I can't get into the ROM because its screwed by the locked bootloader. You begin to understand the infinite loop i'm in? :eek:

Attempting to flash any ROM other than (i hope) vanilla results in an error cascade as TWRP can't mount any of the partitions because its locked out by the locked bootloader to begin with. TBH I may hit the same issue with a vanilla ROM anyway as theoretically, it should suffer from the same issue. Namely TWRP's inability to mount/write to any partition due to the locked bootloader to begin with.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
You cant flash the stock images without an unlocked bootloader. Your only option is the LGUP Tool.

http://xdaforums.com/nexus-5x/help/req-help-to-unbrick-t3251740
[Nexus 5X Q&A, Help & Troubleshooting] SlimSnoopOS:
Ok. Just one more thing, cuz it seems [MENTION=5983945]PiousInquisitor[/MENTION] has more resources that deal with this issue. Have you mounted system and data partition while in TWRP then tried installing a custom rom?
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
TWRP can't mount/write to anything. Because the bootloader is locked, it can't decrypt them.

At the moment I'm actually looking at professional services in my area to see if they can help. I tried the lg tool but that can't recognise my phone for some reason. So yeah, I think I've exhausted all troubleshooting I can do myself. May just have to chalk it up to a learning curve with Android 6 and that oh so innocuous setting in dev options that ultimately ****ed me over.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
Not spending the time to familiarize yourself with the (documented) peculiarities of a new phone is what porked you. I'm sorry if that sounds mean, but is the truth.

I think you are giving up prematurely. The method I linked to works (based on the comments in the thread). I'm confident you can get your phone working again using it. You just need to get over the first big hurdle which is installing the correct drivers.

If you are sure you are going to throw in the towel that's fine. I'm willing to help you through this though. Tomorrow though. ;)
[Nexus 5X Q&A, Help & Troubleshooting] dccxviii:
No offense taken. But to be fair, i'm not aware of anywhere on the web that explicitly illustrates how such a single setting on the phone can pork me that badly. Especially one in the ROM as opposed to everything else that is more low level like the bootloader or recovery (tbh I only randomly came across the setting as I was exploring the dev options and noticed it as a new setting. I'd wager most other people wouldn't have picked up on it at all). I guess I just got used to how all the previous versions of Android worked that the new setting in ver 6 caught me unawares is not entirely unexpected. In my experience something like this is really only going to rear its head when people like me get caught by it, post online and if someone is lucky enough to randomly come across it before they go through the same process, then all the better for them.

As for the LG method, i've installed the various drivers but Windows only sees the phone via the ADB interface or android composite drivers. I've tried manually loading the LG ones but unfortunately the installers aren't very useful to the manual windows driver pointing tool. I.e. I have no way of getting windows to use the appropriate LG driver. Thus the LG software will never recognize my phone.

If you can help with that, i'd greatly appreciate it. Ideally i'd need the raw driver files themselves as that would be by far be the simplest method of pointing Windows to use the LG driver as opposed to any some executable that you just have to 'hope' Windows decides to use when you plug a device in. But so far i've not been able to find them. Tried extracting from the .exe but there doesn't seem to be a valid driver file in the package (which is strange).
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
I borrowed a roommates Windows (10) computer this morning and followed the steps right up to the point where you click start. This computer had no issues recognizing the phone with the drivers properly installed.

I am struggling with the idea that windows is having to choose what drivers to use. Im not an expert on windows drivers but im pretty sure the software of the devices you plug in determines what drivers are used.

So, you installed the drivers linked in the post (LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1)? No errors? It completed successfully?

That is only part of the driver installation process. When you put the phone in download mode (hold volume down whilst plugging the phone into the computer) there will be two the downloads and installations that will automatically occur. Be patient, that take for ever.

Once that is done you should be able to follow the rest of the OP that was posted.

Did you happen to watch the video in the other post? The process you should follow/experience is the same for installing the drivers. The crack and LG Flash Tool are not applicable for your unbricking.

If you run into any errors or problems post back with some detail. Sometimes its the little things the block the big things from happening.
[Nexus 5X Q&A, Help & Troubleshooting] :
I don't want to state the obvious here but you should not have locked the bootloader. That's the last thing to do. I have been keeping a track of this thread and I've done my fair research on android's bootloader. Right now you cannot use the fastboot protocol because the bootloader is locked. You cannot unlock it because you did not toggle the allow oem unlock option. You cannot load anything via twrp too. Google introduced this feature as a part of their anti theft program. Wherin a stolen device can't be reset via fastboot. Your only options are to go to the service center and let them reset the phone using their proprietary tools. Google has already acknowledged this situation and hopefully they will be providing a fix in later versions of android. Meanwhile, I'll still keep messing around to see if I can come up with a workaround for this issue..