text:
Is it possible to re-install Android OS When the OS is practically useless
As the title suggests I'am trying to re-install Andriod but their are several criteria that are preventing me
1. the Android operating system boots but upon passing the lock screen, all core processes such as launcher crashes meaning i'm unable to change settings (Even though sometimes I'm able to change the settings it just reverts back upon Reboot and the settings don't even work properly)
2. ADB does not detect the device (assuming because of USB Debugging)
3. Tried Android safe-mode it does pretty much the same thing as normal mode
4. Tried a factory reset but it just reboots and shows the Android recovery options instead of erasing
I'am currently out of options Please help
Thanks in advance

If you want more specific advice (e.g. how to install Android on your phone, or how to fix whatever problem makes you want to reinstall in the first place), you'll have to [edit] your question to give more details. Reinstalling Android is quite unusual, so it may be better to ask a new question describing the original problem: there might be a better way to fix it.

Short answer is yes!
Long answer:
you can Flash* Android "Stock Rom" for almost any type of android devices, even if the old one isn't loading at all.
as long as the hardware doesn't have any problems
but there is some problems
1. To find the stock Rom:
you will find it with a little search depending on device manufacture
2. To flash it without breaking your device:
this process can be very risky and highly depend on device type
3. you will lose your warranty
safest way is to find a near service center to do it for you
but you can find very useful stuff here:
https://forum.xda-developers.com/

It seems that i'm able to find some custom roms for my ZTE T815 XDA forums But no Factory roms on the internet so far I'll try and request the boot-loader key and Rom from the manufacturer

check this one: link , but be careful !! i didn't test this i just found it on google search

OK i've grabbed the Rom so how do flash the rom
BTW Do i need to unlock the Boot loader for this ?

and before you say "use Fastboot" that is not an options as ADB doesn't detect my device therefore i can't force it into Fastboot

you will not need fastboot or unlock you will only need the VCOM drivers, you can follow this tutorial link .... but be very careful as you can brick your phone easily by one simple mistake!

Dumb question but on the guide it said to only tick recovery which installed the recovery image do i tick any other options in  order to reset my OS

 I tried ticked all options and tried Format + Download but to no avail when i rebooted the phone the problem came back

I'm afraid that you have bigger problem now, as you shouldn't format mobile Flash memory using flash tools, as you will loose other partitions which keeps important data such as IMEI and MAC,...

NO i didn't do anything not even reset the OS it did nothing the os booted up like normal and the process kept on crashing

This is a common issue that I have had many times when flashing a custom operating system. Occasionally, I've found that a full rom reset (or factory reset), which is wipe data and davlik / art cache, might fix the problem however if it doesn't, then you need to re-flash.
So I ask, are you trying to flash a custom rom onto the phone? If so, then make sure you are not trying to flash a rom designed for another phone. Make sure the rom you are flashing is considered stable, and take a look at feedback from other (especially more experienced) flashers.
If you're using the factory rom, then try and reset it. If this doesn't work, then try looking for the factory rom somewhere. For HTC phones, this comes in the form of the Rom Update Utilities (or RUU), which you can find on the HTC Website or HTCDev. For Samsung phones, you can also retrieve the factory firmwares off the Samsung websites. I have no experience with any other phones, however I expect that they would also supply their firmwares online.

No i wasn't trying to flash a Custom rom and i'm unable to do a factory reset

it just happened randomly after a reboot


text:
Motorola DROID Maxx In Reboot Cycle
My Motorola DROID Maxx, for some unknown reason, is constantly restarting. I tried to put it into safe mode, but to do that it needs to restart and it continues to go through this loop. I had this issue only recently, then I wiped it clean. I put back on my phone the apps I had before (list of them below) and updated some of those that came with it. While I was trying to do that, it wouldn't connect to wifi. I tried to turn it on but it keeps turning off (quite the rebellious). Then it randomly started doing the restarting thing again. I have tried safe mode, but it ignores it. I have tried recovery mode but so far only managed to get into it once. I hit the power button by accident and left the recovery mode.
Later, I managed to get into recovery mode and selected recovery. I managed to get to the menu and rebooted the system. It was no longer in the cycle and was now only shutting down without warning (no vibrations or anything) every time I start it up. At one point, I couldn't start it back up, so I put it on the charger and managed to get it. Then I put it into safe mode and it started the cycle again along with occasionally completely shutting down. After it shuts down it doesn't start up until I start it up.
Any ideas as of why it is doing this? Also, does anyone have a solution?

Here are the apps I have added (to the best that I can remember):

Facebook
Messenger
Google Sheets
Google Docs
Libib (had this before I wiped it, forgot to add it afterwards, so this isn't the issue)
Covenant Eyes (my dad put it on my phone, I don't know if he actually put it on my phone after the wiping, so this may not be the issue)
YouVersion (a Bible App, this is one of the last ones I put on there)

If I put anything else on my phone, I don't remember at the moment. Some basic things were updated (Google apps, camera, gallery, etc.)

Some additional information about my Droid (I don't know if this is of any help):
Model: XT1080 FCC
ID: IHDT56PE2
Type: M0DBA

Unfortunately, sounds like a hardware issue to me. Have you tried flashing the stock firmware?

What do you mean by "flashing the firmware"? BTW, my phone is no longer on the reboot cycle but it still is tempermental with the wifi. Same issues as stated in question. It sometimes decides to work while other times it turns off the wifi and I end up using data.

Flashing the firmware is essentially the same thing as doing a clean install of the OS on your phone. It would be similar to reinstalling windows on an empty hard drive for a computer. There could be a corrupted file on your current install or it could be a hardware issue(which we can't help you with unfortunately) at the very least flashing will eliminate the possibility of it being a corrupt file/software issue

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/

sort: votes


text:
Yu yureka Recovery
I have yu yureka phone on which I tried to unlock the bootloader and flash cwm recovery. As the process continued and at last the window showed ' finished'. I then tried to boot into recovery mode by pressing all hardware keys simultaneously but it didn't opened recovery and the phone started to homescreen. I need to know whether recovery is installed properly or not. I don't want to boot into the recovery mode because last time it did so and the phone was in bootloop so is there any way to know if the recovery is installed properly or not without rebooting it in recovery mode.
Thanks. Please help.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/


text:
How can I get old Android updates again after a hard reset?
I have an AT&T HTC that was running Marshmallow 6.0.1 and Sense 7. That's the last update my phone will ever get since it's an older model. I factory reset it to wipe it clean, which returned the software to Lollipop 5.0.2 and Sense 6. I've checked for updates in the settings and it tells me it's up to date even though it's not. Do I just need to wait a few days to get the update notifications? Or do I have to take it to AT&T and have them update it? Or do I have to flash marshmallow myself?
Model HTC Desire Eye
Build 2.09.502.3

It's unlikely that a factory reset can reset OS version. Can't help but wonder what you did prior to that. Anyway, I do recommend manual flashing.

Maybe it didn't, but I do know the interface doesn't look the same and I can't find certain apps in the Play Store because its downgraded. Do I have to root the phone before I flash it? I would rather not go through the rooting process...

Interface downgrade is possible, since HTC moved quite a bit of Sense apps to Play Store (even including the most central part, Blinkfeed!). Get them from Play if that's all you want. On the other hand, flashing does not require root, but does involve getting drivers right and finding a proper firmware, and for amateurs those troubles aren't exactly less than rooting.

Is there anyway you help me with flashing it? I really dislike the old interface. I've searched up and down and finding the right tools and firmware for my phone is pretty confusing to me.

By "interface" do you only mean the homescreen (launcher) or anything else? To help you with flashing a lot of details have to be provided, enough to be made into another question (which could be duplicate anyway).

It's biggest noticeable change is the lock screen. It shows my notifications right in the middle in big white boxes. And since the power saver option is always on, there's always a white box in the middle of my screen. Before I reset it back to factory, notifications would just display a thin black bar at the top and disappear within 30 secs or so. Power Saver was just an icon at the top by the battery icon. It looked much nicer. There's also some other minor cosmetic changes.  Other things include I no longer have HTC themes and some other HTC apps.

I have the general idea of how to flash. I just can't seem to find WHAT I need to flash? I've found things like Marshmallow 6 for HTC (pre-rooted). But that's not what I need, is it? I don't need to root to flash according to the above comment.

Hmm, then you probably do need a flash. You don't need root to flash RUUs (factory firmwares), but those you found do need root and/or custom recovery. Whatever it is, I suggest supplementing more details by editing your question - you didn't even tell us your model and system build number (something like x.xx.xxx.x).

Sorry, I'll add more details. I haven't been able to find a RUU with stock marshmallow. I have one for stock Lollipop, though that's not what I need since that's what I already have.

I have found things like stock marshmallow for HTC One M8s and some Galaxy phones. Theres one on the official htc website for marshmallow 6.0 for One M8. Would those work for mine? Would they include Sense 7?

No, don't even think about cross flashing. As of now I haven't found such RUU either... All I could think of is the "hard" way i.e. flashing stock-based images with a custom recovery, but since you specifically stated that's not acceptable, I'm at a dead end too.


text:
Problem in usb debugging
I wanted to move all inbuilt apps on my Samsung Galaxy On7 to the sd card to free up space. To do this, I followed this site.
However, even after enabling USB debugging, the desktop is not being able to show the device in adb devices list. I had previously uninstalked all android emulators (like BlueStacks) and have the full android sdk tools and Android versions 5.0 to 7.0 installed on my computer.
Anyone can suggest why this happens?
Any other way to move inbuilt apps to sd card without rooting the device?

On the site you linked the author wrote: "After all of the comments I’ve seen up to this point, I think it’s safe to say that this tweak will not work on Lollipop (and probably Marshmallow) unless the device is rooted."

@kirodge what are the potential problems I might face if I root my device? Can the process be reversed?

@WRICHIKBASU see our rooting tag-wiki and the details linked from there. Apart from that: if your device doesn't even show up on adb devices, and you're on Windows, it's probably a driver missing.

@lzzy My Driver was properly installed, and phone USB setting set to MTP.


text:
I have lost my Phone - Please help
I lost my phone somewhere and I know it is not in my house; it is ethier in my car or at the place where I got out of the car (which is by my school).
I do not know if my phone is dead by now and if not, then it is on silent mode. My question is:
How can I find where my phone is?
I got no apps and I tried the Google android device manager and it is saying no location found.
So, how do I find out where it is? I searched EVERYWHERE in the car. I need to know as soon as possible, and if there is no way you can help me, then is there anyway I can get my photos and videos etc from my LOST phone and transfer it to my NEW phone?

There is a solution: Since Device Manager (follow the link https://www.google.com/android/devicemanager? ) does not seem to help you and since you do not have another security application for tracking your device, I am sad to having your told that your mobile phone is lost.
This means that your old phone has not been turned on since it was lost. Another option was that it had a reset after that was "lost", which means it was stolen.
I hope someone else have a good idea to help you, bui it seems you cannnot do anything to recover it unless you physically find it.

You have to acrivate this first on your phone to make it work so no this isn't helpfull right now.

authors: Једноруки Крстивоје


text:
Need a good app for writing Android applications on phone itself
I am a beginner in Android programming,  and have started very recently. I mainly used to work on my computer (loaded with android SDK and versions 4.0 to 6.0 and having android studio and Eclipse IDE).
But, currently, for a long time, it is not possible for me to sit at my computer. Is there any good app where I can write, compile and run applications on phone itself?
I have a Samsung Galaxy On7 with Android 6.0 Marshmallow.
Update: please suggest anything but the AIDE IDE available in Google play store.


text:
Delete VIBER account from one number forever
Can you help me how should I delete my VIBER account from number +38xxxxxxxxxx because I cannot use two VIBER accounts at same mobile with two SIM cards?

I'm guessing you want to deactivate the account associated with the number so do this:
1.Open Viber.
2.Enter the More Options menu.
3.Select Settings.
4.Select Privacy .
5.Select Deactivate Account.


text:
Is it possible to make Android Emulator appear as an USB device on my Linux machine?
I need to access both ADB and MTP from one emulated device. May be there is some ready-made solution that can emulate android device via usb device emulating?
All that I found is an android kernel gadget https://android.googlesource.com/kernel/common/+/59c75bcf603f355ff34282422e8c3f2165b9d5f2/drivers/usb/gadget/android.c
It can be useful, but it's not the easiest way to do that.

You can not access ADB via MTP. MTP is a lightweight/limited file transfer protocol (most user would call it crippled). It is limited to one operation at the same time. ADB is an universal protocol for accessing Android devices via USB. It supports shell access, file transfer, port forwarding and so on. It is multiplexed and supports all features at the same time with multiple commands.

Yes, you're right, I messed up. I corrected the question. I am interested in emulating a device that will be able to work with two protocols via USB. Yes, it is very important that the device emulates connections over both protocols via USB.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Android 10: how to get write permissions on external USB drives
I've just bought a TvBox with Android 10 in it, and i've soon discovered that no app can write on the external HDD/flashdrives i attach to the USB port (seen as /storage/<long_number_here> ).
This is a problem 'cause the internal storage of the TvBox isn't enough for the apps i want to use (KODI is a good example: it generate a lot of thumbnails, taking up much space, but i can't configure it to use the HDD folder 'cause it can't write to it) or 'cause i'd like to use a wifi connection to update the files in the HD (the file manager which provide the connection cannot do anything on the HD).
While i'm not an android/linux expert, i'm not afraid on using ADB, rooting the device if necessary, etc, so i'm asking what should i do to obtain writing permission on every external device i may plug in the USB port.

https://gettechsupport.in/wp-content/uploads/2021/05/Force-allow-apps-to-write-in-external-storage.jpg.webp

Sadly, i don't have any of that options in my developer options.
I have one that says (translating from italian to english, sorry) "do not keep activities (delete any activity once interrupted by the user)" and "Force autorisation on external memory (allow the installation of whatever app on the external memory, no matter manifest values).

"Force autorisation on external memory (allow the installation of whatever app on the external memory, no matter manifest values)"

@alecxs, This does not work. File manager still can't write on external disk.

What file systems are on the external media you're trying to use?

@ChanganAuto: tried both NTFS and FAT32. The device creates automatically an Android and a Media folder on everythng plugged in it (the Media one is to record DTV on it), so the problem is really just on permissions, not on incompatibility of some sort.

stupid file manager? OTG usb-storage is provided only by uri not by path https://i.sstatic.net/a37p1.jpg

@alecxs: NO APP can write on the external drive(s), not just the file explorer (which is Xplore). Even the internal file manager.
I've never seen that dialog in this TvBox (even with my trusty old version of ES File Explorer, which i use from years on every cell i own): i was expecting it, but it never appeared.
Seems that i fall in the case mentioned here: https://www.lonelycatgames.com/docs/xplore/known-problems/write-external-storage
I have no "files" app (as mentioned in the "Why writing doesn’t work" chapter).

I don't have com.android.documentsui, too (at least not under that pkgname) https://i.sstatic.net/QDEqw.jpg

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
full adb restore not restoring [unencrypted] .ab file to bootloader unlocked Lineage device
This is a follow-up troubleshooting question to this one here in this very same forum.
After repeatedly confirming the connection through both of adb devices -l and fastboot devices -l tantamounting to at least ~5½ of overall sessions for the restore command of a 7.95GB-heavy backup file, whenever there's a successful prompt after proper command-execution of the following:
adb restore <filepath>
But I managed to notice the constant: The restoration always gets stuck on com.qualcomm.timeservice quite oddly till time-immemorial, since I understand that I might be at fault somehow, somewhere — but in spite of that, if the latest builds of so-called AOSP do not support alarm-ringing during device shutdown [not caused by battery-drainage], I can safely conclude that the alarm did work during switch-off state of my device at least once. Doesn't that translate to the package working fine, instead of having gone corrupt by the time I created the .ab file?
More details for those who un-stereotypically can digest in-depth  text, they may get better context over there with some back-citation to key comments in that preceding question over here.
But other than the exact package which gets stuck, I should also note that I did try adb push <PC's .ab filepath> <device's root-directory path> after 1-2 trials-&-errors to determine which one is exactly it. It went upto 100% in ADB Enabled recovery mode, and then.. Failed to be stored by the time I booted the device last-time I clean-reinstalled the latest-build[ as I originally send this] of LineageOS 19.
The rest of the context is summarised there, except that I haven't tried bmgr of adb shell 'cus using bu help wasn't much of a help, so it slipped my mind to try creating backup through that method — nevermind restoring.

com.qualcomm.timeservice is an internals service you don't need to recover. I would extract the backup data using abe, delete the data for this package, rebuild the backup file and try again to recover the data.

Ahh.. Hey, Mr "@Robert"! Here we 'meet' a-gain. Hope you're doing well. No I am asking with utmost sincerity.⏎Alright.. So I guess back to my irregularly-accessible PC then? (Since the apps like jackpal.androidterm function properly on rooted-devices only, no?) Also, is not locking the bootloader [as of] yet — a good-thing, no? Is it insignificant/immaterial/irrelevant? And do I have to create a newer backup-file and necessarily wipe the cache and system partitions, if not necessarily a wholesome clean-reinstall for the 6½th time?

P.S. Okay, Mr @Robert .. I had to struggle since past innumerable hours in innumerable sessions, since it turns out, in ascending-order of my misery: A) The adb.exe, a-gain download as part of standalone SDK platform-tools kit, had gone wholesomely corrupt but unlike the in-depth explanation at XDA, it hadn't reduced to "0KB" or anywhere remotely-near it. B) If it helps, frighteningly, turns out the very same case was with my .ab file in question — but I managed to 'miraculously' recover it full-&-proper when I regained my composure. C) One bad, one good — you say? Not that soon, ...

...given my jinx, after all. It turns that the PC I'm able to irregularly access had been deemed as "high-tech" as it is ancient( quarter-past-11-years as I "add" this) had been thoroughly rid of Java®, so I couldn't access any .jar file — as mandated by your tool. So I tried to install that "bestest-ever, open-source Java" programme from that .net official-web but in spite of installing the certificate separately, I still couldn't get it to installation. So we went to the OGs, ~~Sun® Microsystems~~ Oracle® and after having expended twice the amount of time and more importantly, the

bandwidth-allowance for a single, ubiquitous step in the ongoing voyage. C) After having installed it, it took my devraj m several tens-of-minutes to learn how to deploy the abe.jar[ through Windows® PowerShell® from the "Downloads" folder"] within the hostile/unhelpful environment taking the toll on my mind, and when I finally managed to do so i.e. convert that successfully-recovered .ab file, your recommended-tool turned-out to be profoundly useless for editing .tar aka, a misnomer of sorts. Since the conditions weren't conducive to me, I didn't have umpteenth hours to go find...

...and learn if there's some way either of cmd.exe, the former or Java® could help in editing .tar folders as pre-installed freemium WinRAR® was oh-so-surprisingly appeared cruel towards us in that month. So I had no choice but to put my research-skills into motion yet a-gain, and finally found a sorta-reliable tool going by peazip.exe which did the trick through one of the 3 baffling deletion-types, since the rest of 2 were about deleting the whole .tar in and of itself which I had managed to extract after so much chore. D) So I managed to repack the updated .tar into .adb after

since minutes of trial-&-error( did I miss nothing that useful-enough PeaZip® was showing all folders as literally of “0KB” of size vis-à-vis utterly-useless WinRAR.exe, including but not limited to the com.qualcomm.timeservice one you overtly asked me to delete( there were other com.qualcomm.[…] folders which I've no qualms to admit, was I significantly inclined towards ridding of them all but I guess to enhance my misery further down the order, I stuck to only-&-only "following down the orders like a robot/institutional-drone of neoliberal world-order. But waiiittt..! This was no-...

...-thing halfway through the mission. E) as the events summarised in point ‘A)’ kicked into action and restarting/shutting-down the PC didn't help it at all. F) Now I've installed the Android® Studio's .exe given the recurrence of Access is denied. errors with platform-tools only SDK, and after downloading and installing about fucking ~1GB of a file, turns out it was a mere shell( not necessarily in IT connotations) as I had to install discretionally needed "plugins" for total 3 so-called AOSP [sub-]releases given both of my phones, for starters. It took additional several-hours since

the whole carefully-selected once-&-all combo installation was of fatherfucking ~6¼GB in total-size, thereby bringing the total bandwidth-allowance spent for this last-resort tool to — by all conservative-estimates, quarter-past-7GBs alone. And for perspective, dare I remind that considering the timeline of this saga which started over from XDA® Developers' message-board to the here-&-now, a simplistic number-crunching still won't be able to di y quantifiable justice. Now I'm indescribably more-than-done with this, if this adb restore is not good. To fuck with brothafucking cockknuckle

Sorry, but I stopped reading after your 2nd comment. You are writing way too much and with too many fill words and irrelevant side facts. Please keep focused and your problem and the commands you executed.

My aplogies for your bother, then. All of the relevant commands have been already churned-out. But given your intolerance for proper-contextualisation, I guess I can offer you nothing besides that once a-gain, downloading-&-installing-&-then-repeat-cycle-for-3-AOSP-releases Android® Studio meant running PowerShell-7.3.2-win-x64.msi in-folder within the platform-tools sub-folder hidden inside Android folder of hidden root-folder AppData came across like the Best choice. And it was quite more helpful in suggesting corrections than MSDOS-era Command Prompt ever has been. Nothing else, IG?

running powershell.exe v5.1 in-folder within the sub-subfolder platform-tools, itself under the sub-folder Local within the folder Sdk of main-folder Android within the hidden AppData root-folder came* There! FTFM ♂ Nothing latest except the fact that in cookie-cutter length, that I've created a single .txt file of .\adb.exe logcat with the added-bonus of -v -time suffixed-in there, for at least the last 2 restoration attempts. Thought given my STML-addled memory, think I could give an idea as to how USB link suddely disconnects-&-immediately-reconnects that way.


text:
LG G2 has horizontal stripes on the screen when displaying high resolution images with moire pattern
Recently my LG G2 sometime has horizontal stripes on the screen. Firstly I thought that these stripes appear randomly and the problem might be related to connection between the screen and other hardware. But today I realize that the appearance is not random. When I open a specific type of image, that is images with moire pattern, these stripes will appear. These stripes will disappear when I open an image without moire and appear again when I open another moire image.
The phenomenon reduces when I zoom in the image. Also, the stripes won't appear if I resize the image to smaller resolutions.
The stripes appear whether the image is displayed in the galaxy app, or the default web browser, or chrome browser. Even when I set the image as the wallpaper, the stripes appear right on the wallpaper.
I have delete the system cache but it doesn't help.
In the picture below, stripes appear when I opened a image of grasses which has moire pattern.

Have you ever encounter similar problems? And can you guess this problem is caused by the hardware or software?

Are you talking about the white lines where the flowers are, just before the big gray/white part of the image ?

@ИвоНедев: Thank you for your reply. I have posted another image which illustrate the problem. These lines have random color and keep blinking.

Ugh.. that doesn't look too good. You say it only appears on images with these colors and nothing else ? What happens if you zoom the image, does the stripes change/change position/move at all ?

Try one of these https://www.reddit.com/r/lgg2/comments/3efz9y/lg_g2_secret_codes/ and look for the screen diagnostics. See if you can make anything out of it. Are you runing stock android, have you rooted/instaled anything fromwtihing recovery/ etc ?

@ИвоНедев: I still use the stock android. The secret code works and I can access the hidden mode of the phone. But the solution in that link doesn't help. Thank you very much for your help ^.^

@ИвоНедев: I have notice that it's not the color causes the problem but the moire pattern in the image. I have test with multiple images which contain moire patterns and the randomly moving horizontal lines appear with almost all of of these images.

I'm going to guess It's a software issue.  Try viewing same photo with the stock Galleries, and google Photos to see if there's a difference at all. Also if you set for instance the second image from your question as a wallpaper, how's the lines then ?

@ИвоНедев: the lines still appear whether the moire images are displayed in the stock galary, stock web browser, or chrome browser.
I also set the image that I showed above as the wallpaper and now the lines appear right on the wallpaper. However, the problem is less severe since the image is displayed in full screen (the appearance of lines always decreases when I zoom in the image). Also, for the same image, if I resize the image to smaller resolution, says 320x180, the lines will not appear.

Is this stock android, or have you installed something custom ?

@ИвоНедев: it's stock android.


text:
Lock password required after some time of not using it
Unlocking my phone every time gets a bit annoying, but I still want the phone to be locked for security purposes.
Is there a way for the phone to ask me for my passcode only if I haven't used the phone for longer than say 30 minutes?
This way if my phone is lost it will still have the password protection, and when I am using my phone in short spurts it won't force me to enter the password.
Nexus 6p
Android 7 Nougat

@beeshyams no it isn't rooted.  I updated my Q.

Sorry, deleted my solution as I didn't quite realise you are on Android 7. You can try this option and let me know if works .This may work is Macrodroid , easy to learn automation app ( may work since developer claims there could be issues due to Android implementation). Trigger: Empty Trigger ;Action: Screen Lock Off; Constraints: None. From the app widget . Select the widget, drop it on to your home screen and assign this macro to the widget. Click to manually enable / disable the macro

All  of what you need can be done on Native android; No apps or root required. Go into your settings, Display, and Set 'Sleep' To 30 Minutes of inactivity.
Then, go into the Lock screen/security settings, and untick 'Power button instantly locks device'
Now, even though hitting the power button turns the screen off, it won't lock, and if you leave the phone to it, it will lock and turn off after 30 mins.
As Ethan Said, you can also adjust how long after the screen turning off the phone locks, then just disable lock on power button as before.

With my android emulator I was able to prove that this is a native setting within Android. Assuming you have a password already (duh), go to settings-> Security -> screen lock settings (the gear) -> automatically lock. This is the setting that will determine how log after the phone is put to sleep, the password is enabled again.
However, this is only when the screen times out from being left on. When the screen is locked manually, the password will enable regardless. The only way to override this behavior is with rooted apps, and your device is not rooted.


text:
RTT/TDD/TTY keyboard not showing in dialer app, for those of us with disabilities

There is an option to enable TTY in LineageOS 16, but it seems to do nothing. Phone -> menu -> Settings -> Accessibility -> TTY Mode -> TTY Full
Full documentation of functionality for users: https://support.google.com/accessibility/android/answer/9042284?hl=en

This step never shows:

While the phone rings, the other person's screen displays an RTT indicator Real-time text.

Is this also supposed to enable TDD? Does the phone automatically detect TDD tones then fallback to TTY tones?

Edit:

Here is a page showing the desired functionality, but on iOS 10. https://support.apple.com/en-us/HT207033

It looks like iOS also  has more options which I think would be very useful  in LineageOS/Android, for example placing the call directly or automatically dialing into a relay.

Looks like there's a prerequisite from the linked Google Support: "To find out if you can use RTT with your device and service plan, check with your carrier.". Perhaps that's what you need to confirm first?

I am unsure which carriers don't support it, but mine says they do. Mine is an MVNO that operates off of AT&T towers in the US. Good catch though. Edit: Quote from FCC https://www.fcc.gov/consumers/guides/use-tty-devices-digital-wireless-phones: "Wireless service providers have upgraded their digital networks to be compatible with TTYs. Consumers are now generally able to use TTYs to complete calls with their digital wireless phones, including 911 calls, if the phone itself is TTY-compatible."


text:
full adb backup not creating .ab file for Realme 2 Pro
I am unable to create a full phone backup file of my Realme 2 Pro (model RMX1801) through the ADB. The phone runs stock ColorOS 7 (Android 10). The device is not rooted and I do not want to root it. Doing that would delete my data. Also, my device hasn't had any screen-lock protection days before I ran the very first command (which is several hours amounting to few days before the original-revision of this post) and remaining wholly unchanged to the best of my knowledge till the timestamp of latest-revision.
Here's what I've tried. I launched Command prompt (cmd.exe) and ran:
C:\Users\Dell> OneDrive\Desktop\adb.exe
C:\Users\Dell> adb devices
List of devices attached
86b3470 device

At this point I started to take backup. I have tried a couple of things and I'm categorizing them now.
Attempts when I entered no backup-encryption key whatsoever
C:\Users\Dell>adb backup -all -f -nosystem C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup -all -f -nosystem -shared C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab

Both of the commands showed on the UI that backup was taking place. But none of them created the backup file in my PC.
Attempts when I entered a backup-encryption key
C:\Users\Dell>adb backup -all -f -nosystem C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup -all -f -nosystem -shared C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab

No change, whatsoever.
I also changed the destination path from OneDrive/Documents to OneDrive/Desktop and repeated all the above commands. That did not work either.
Attempts with double-quotes
C:\Users\Dell>adb backup "-f -all -nosystem C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab"
C:\Users\Dell>adb backup "-f -all -nosystem -shared C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab"

Did not work.
Changed double quotes position
C:\Users\Dell>adb backup "-f -all -nosystem" C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup "-f -all -shared -nosystem" C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup -f "-all -nosystem -shared" C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab
C:\Users\Dell>adb backup -f "-all -nosystem -shared" C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab

Here's what happened in the case of double-quoted commands: All of the ones ending the double-quotes before the backup file's path appeared to have started the backup process but it did not create the backup file either. The duration of the backup process in the UI was also incredibly shorter, aka literally instantaneous, in these attempts.

As asked in the comments, the versions of adb are produced below:
C:\Users\Dell>adb version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as C:\Users\Dell\OneDrive\Desktop\platform-tools\adb.exe

C:\Users\Dell>adb shell adbd --version
* daemon not running; starting now at tcp:5037
* daemon started successfully
/system/bin/sh: adbd: inaccessible or not found

C:\Users\Dell>adb devices
List of devices attached
86b3470 device

C:\Users\Dell>adb shell
RMX1801:/ $ adbd --version
/system/bin/sh: adbd: inaccessible or not found
127|RMX1801:/ $

here are the [hitherto] unsolicited screencaps/screengrabs/screenshots:

Just to make sure: When executing the adb backup command your phone display has to be on and the phone has to be unlocked, otherwise you won't recognize the screen that is shown where you have to enter the backup password. Anyway for checking if backup works correctly use adb shell and then execute the backup commands locally on the phone using the bu command instead of adb backup. This way you will get all [error] messages bu outputs. See also https://android.stackexchange.com/q/231235/2241

Done as you asked, Mr alecxs! Alas.. My concerns have borne out, once a-gain. As referred to in this post which had direct involvement of "@Firelord". **You may also wish to pay attention on the newly-expanded part of my so-called “WOT”( precisely: the one above/preceding the adb shell part) in the original-post/"question". It has been added belatedly since I felt it was too concise enough, that it may end-up prolly giving wrong idea of my experience; especially for the target-audiences.

@Robert So I did part of what you asked me originally, the one-&-only part of your visible comment hitherto valid. Surprisingly, when I tried to try out the connection of device without switching from the preset-default of “Charging only”. So it didn't connect. There followed the multiple sessions of restarts and shutdowns before I realised that while I didn't turn-off "Developer Options", I had turned-off (voilà!) "USB Debugging".Unfortunately trying out this adb shell sub didn't return with an error — in fact, it didn't even execute the "Full Backup" [G]UI on my phone, no matter variables.

I would recommend to run adb logcat in a second cmd window. I once had a device where the manufacturer pushed a ROM with a defect bu version thus adb backup wasn't functional at all. I could see it on adb logcat where the stack trace of the error always appeared after executing an adb backup command.

Hold on.. I still have to try your belatedly original-post upon the sufficiently “readable” edits by our mutually-respected 'intermediary[?]' Mx "Firelord", Mr alexcs. So address-them-not-chronologically-but-not-entirely-either, your 2nd-/yesterday-latest 1stly: I had covered the matter of backing-up packagewise since my original-edit since get-go. It might not be sufficiently "readable", so to hold-your-fingers, read bullet-point 3 in this first-ever "cleanup", by mod Mr @Andrew T. — germinating tension there. Not exactly C for , but..

Before we proceed any further, Mr @alecxs: About your “ADB version”, it appears you also missed my indication that I've two adb.exe files within the same root-folder. But I dunno whether it's an enigma for computing-based machines supposedly more compliant with binaries than the rest of universe or myself inadvertently causing it by opening the folder from platform-tools out of sheer frustration. But the directly-accessible file has gone corrupt, gives Access is denied. in cmd with the same warning from MSW10 when I try opening it manually. That is why I had to rely on that 32-bit ver.

Ughhhh.. That several-dozens lines of codes within hundreds-of-milliseconds i.e. too quick to follow for an average member of Human Civilisation, Mr @Robert Just to be clear (if it must), I've tried that method and generated at least ~5 screencaps/screengrabs/screenshots of with the consciously deliberate --dividers 2nd optional-argument, so as to make them more readable than any of my "worst" revision — to be rather considerate. From both of horizontal-sized to even vertical-sized windows. Sorry Not Sorry that I didn't opt to create a copy-pasted .txt  out of concern for your health.

Done-dunna-done, Mr @alecxs! Other than Mr "Robert" here, I gave up on creating .txt copy-pasted files of my prior sessions on "whatever" version-&-bits of adb.exe for both of adb backup and adb shell-reliant bu cds, & 3-4 more — given "his" demand to redo what I've had already tried but only-&-only with adb backup. So.. Are those mercifully shorter-lines of text for my phone's each-&-every single gonna do the work for u? Or u would rather insist on creating a .txt which is, frankly, not readable for average Humankind; given there's 0 indication at all that u know whatcha  for.

stackexchange.com is Q&A site (like a wiki) and not the right place for troubleshooting and discussion. you're better off in a forum

Thanks for your clarity, Mr @alecxs — and I see that you've replied to me over there. But alas.. I already have done so since weeks Google's D2D transfer tool( originally named otherwise) in CloudBackup through the Activity Launcher app to open this one-time only app which was successful, just not in transferring much of app-data. Since as noted in the comment below, the device-switch apps are no longer OEM-agnostic — so I already do have a variant of that app on my app which simply treats every phone as "old" be it remaining pre-installed, or you install it on some non-BBK® brands' gizmo.

adb help specifies usage of backup
  adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
                               - write an archive of the device's data to <file>.
                                 If no -f option is supplied then the data is written
                                 to "backup.ab" in the current directory.
                                 (-apk|-noapk enable/disable backup of the .apks themselves
                                    in the archive; the default is noapk.)
                                 (-shared|-noshared enable/disable backup of the device's
                                    shared storage / SD card contents; the default is noshared.)
                                 (-all means to back up all installed applications)
                                 (-system|-nosystem toggles whether -all automatically includes
                                    system applications; the default is to include system apps)
                                 (<packages...> is the list of applications to be backed up.  If
                                    the -all or -shared flags are passed, then the package
                                    list is optional.  Applications explicitly given on the
                                    command line will be included even if -nosystem would
                                    ordinarily cause them to be omitted.)

according to usage the [-f <file>] parameter requires second argument <file> which is missing on your command:
adb backup -all -f -nosystem C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab

correct usage with 2nd argument:
adb backup -f C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab -all -nosystem

Note: full backup is not possible with adb. only apps with android:allowBackup=true in AndroidManifest.xml can be backed up with adb.
one can make test if adb backup is working at all with single package that allows backup, such as Chrome Browser which comes preinstalled on most devices.
example:
adb backup com.android.chrome

this will create backup.ab containing Chrome Browser app data. the location of the file is the current directory.

https://gist.github.com/airtonix/6332922#file-adb-output-L67

Ha! Regardless of the fact that I dunno whether you could figure-out why the ADB version “on your phone” is not showing, in spite of following that hyperlinked thread of "@Firelord" confirming that they could since they are on a rooted device. It turns out, that you were right! As you can skim through the revisions, **the only thing wrong in my command-lines for backup commands( the 2nd-guessing by adding double-quotes not considered) was the position of file-path. When the .ab actually did get created, my light-bulb moment of finding that dir folder-path and turns out, backup-files..

...dating back to as earliest as 10[th of] this month, this year( January 2023) were created. Few were junks like veritable 0B sized to less than 5 KBs or so — and all of them without the .ab extension so they remained altogether null value of files, irrespective of their sizes. But while one was exactly the size that got created in Documents( 6.36 MBs), the largest one was at least 165+ MBs. Thereby, I've marked your reply as the correct-one, Mr "@alecxs". But since my purpose was to use ADB for device-switch purposes given the lack of pro bono OEM-agnostic solutions( in non-rooted

so-called AOSP ecosystems, at the very least) by now — I ran some adb restore commands but since all of those returned with "Restore ended" messages instead of ‘Restore finished’, analogous to “Backup finished” on my very different devices and yes, different forks with even 2-generations gap of public Android builds — should I ask for that as a seperate follow-up question for assistance in that regard, or following-up here is not egregiously contravening of the laws of this fora net, Mr @alecxs?


text:
Can't edit boot commands in VMware for Android x86
I'm attempting to install  Android x86 from https://www.fosshub.com/Android-x86.html following the steps on https://hackmd.io/@StanS/Android-x86, and after getting to the point where I can reboot and boot into the OS, I go to edit the boot command for step 4. I hit e twice, but then I can't change the boot command. It just gives me a line with out the string that I need to edit. on the previous page, it has the string listed, but everything I search for just says it should be there.

You need to type reboot
Or you can watch this tutorial on Youtube
https://youtu.be/nFtNKY1g6Lc?si=HzynNrGjrZaSI414

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.


text:
Cannot add new Certificates to Android Device
Using a Pixel 6a, running Android 13.
I am trying to install certificates from a private CA I have established on the internal network. I was able to install the root certificate by doing the following:
Settings > Security & Privacy > More security settings > Encryption & credentials > Install a certificate
From there I am able to select the ca.crt file I had copied from the CA server. I can see this new certificate when I hit "Trusted credentials" under the "User" section.
When I try to repeat those exact same steps to add a server specific cert, it's never added as I can't see it under "Trusted credentials". There is no error NOR a confirmation that this certificate was applied successfully.
Edit: When I successfully install the CA cert, I get a small tooltip/popup saying it's been installed successfully. When trying to install the non-root certs, I get no confirmation, and am simply returned to the previous UI view.

If you have installed the root CA certificate you don't need to install the server certificate, too. It is already trusted by the installed root CA cert. Note that user installed CA certificates will by default not affect most apps. Only a few like Chrome will accept it as a user certificate.


text:
App Search doesn't open in Play Store
I recently got an update on my phone to Android Version 12. Before this update, when I would scroll through my Apps I had a search bar on top where I could text-search through my installed Apps. If I typed in the name of an App I didn't have installed, it would offer to search through the Play Store for me.
This behavior no longer occurs. Instead, now when it can't find an installed App anymore, it automatically changes to a Google Search, but not without emptying my Search query entirely first.
Is there a way to get the old behavior back?
Model and Hardware: FP4
Manufacturer: Fairphone
Build number: FP4.SP1Y.B041.20230109

If you recently got Android 12 then your phone is not from Google and most likely dos not run plain Android or use it's default launcher app. Please edit your question and add manufacturer and exact model name of your phone. AFAIR the behavior you describe is determined by the launcher app which can be replaced by simply installing a different from Play Store.

@Robert I added manufacturer, model and build number. I never changed my launcher, I don't know where I can tell which one it uses by default, but I am using the default launcher my phone came with

Also posted on Fairphone Forum, just in case it gets responses: https://forum.fairphone.com/t/app-search-doesnt-open-in-play-store/93378


text:
Obb folder empty even though I can see inside data folder
I looked through everything I could find but I couldn't find a specific answer to this, sorry. I'm using a Samsung phone running android 13 - it isn't rooted and I can't risk rooting it. Both by using a computer through USB and through the AOSP Files app, I can see files inside the android/data folder, but inside the android/obb folder is appearing to be empty.
This seems strange, firstly as: I read that obb folders are only created when an app needs them, so I'm not sure why it would create them and then leave it empty. And secondly, because I would think there are other files inside these apps that are not showing up within the data folders, as some of the apps are quite big and there aren't files corresponding to certain things that seem to happen too quickly to be downloaded as they're needed - as well as, with how spotty the internet I use is, I would expect to have seen more connection errors as the game tried to access them if they were being downloaded each time.
Do I just not have the right permission to look in the obb folder, even though I can see in the data folder? And if so, is there a way to look inside it without root? For reference, I use a Windows computer. Thanks for any help you can give.
Edit: The file manager linked in this Reddit post about accessing the /data and /obb folders in Android 13 can apparently allow the user to access folders through launching the file manager as if it was within the app the folders belong to. However, even through this, the /obb folder appears to be empty on my phone.
The /obb folder is also empty in the com.sec.android.app.samsungapps app - could anyone with root access who also has that app look inside the /obb folder and confirm whether it is indeed simply empty, or whether I still cannot access it?
If it is truly empty, is there anywhere else that the data from a large app (.eg saved games, animations, character images - all things which I would think would be within the app itself due to fast loading speeds and the lack of connection errors, but are not appearing within the /data folder) might be stored that I am unable to find?
Edit 2: I've been looking into various ADB and ADB shell commands following this list of commands on Github. Is the adb shell pm grant <package name> <permission> only for things like giving permission to apps to use the camera? Or is there a way (not necessarily with this command) to use ADB to change things like read/copy permission? I have seen posts up until fairly recently say that you can still access data and obb through a PC, but they often don't mention how.

It's a bit strange that you can see files inside /android/data without being rooted since I couldn't see any files inside /android/data on Samsung Galaxy M12, Android 13. Are you by any chance using an external SD card?

@AndrewT. I thought it was strange as well - I'm not using an external SD card and can't see an SD card folder on it (this phone is refurbished, so I don't know if it's ever had one in it.) Following this Reddit post (https://www.reddit.com/r/Android/comments/yqenbr/how_to_access_android_13_data_and_obb_folder/) I downloaded the app which provides a shortcut into AOSP file manager. I don't know for the main app I'm interested in, but the app com.sec.android.app.samsungapps also appears to have an empty obb folder, and I can't think of a good reason for it other than permissions.

I just checked on my Pixel 3a running Android 12 and I can see the content of /obb but not /data using Files by Google app. However, I am still unable to access /obb on Galaxy M12 running Android 13 even though I know for sure that there are files inside there, since it stated "modified x minutes ago" just after I installed a big game.

This might be related: Android 11: Can't see contents of "/sdcard/Android/data" even with root, though I could browse /obb and /data using adb shell, if that's possible for you.

Thanks for answering this again! I'm a beginner with adb, but I gave it a shot. In adb shell, when I used $ cd /sdcard/android/obb/<app name> and used $ ls, it didn't return anything, as if it's still empty. Is this the correct obb folder? Or maybe the wrong commands?


text:
How To Root Samsung A510F?
I have tried Framaroot, Universal Android Root, IRoot, Z4Root, TowelRoot  and obviously, kingroot. I also attempted to try chainfire's auto root but could not find a compatible file to flash for my device. Here's the link to chainfire's list of compatible devices Chainfire Auto Root
Here is the screenshot of my device software info

You should try rooting with TWRP.

Download TWRP Odin flashable here
Download Odin here
Boot in download mode with POWER + HOME + VOL DOWN
Connect the phone
Flash with Odin 3.10.7. Select the downloaded file using the AP slot. Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot
Flash the file below in twrp.
DO NOT LET TWRP ROOT YOUR DEVICE WHEN IT ASKS FOR. USE ONLY THE FILE BELOW:
Root Chainfire SU

NOTE 1:  FLASHING CUSTOM STUFFS VOIDS YOUR WARRANTY. AND THIS WILL TRIP THE KNOX FLAG.
NOTE 2: ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Settings > Developer Options > OEM Unlocking

Thank you for your quick answer! However, is it possible to flash a custom recovery without root and pc?

On some devices root is not needed, on others it is a must. I've never tried flashing a custom recovery without a PC. Flashing a stock recovery through a custom recovery seems possible though.

What do i need to make sure such that I will not brick my phone? There was once i attempted to root my phone by flashing chainfire auto root using odin and ended up bricking my phone. I got it fixed by taking to Samsung and they said the motherboard was spoiled.

I cannot assure you if i gonna work or not.

Is it possible to turn my phone into a emulator on the pc? I would like to test it on an emulator first if possible.I know I am asking to many questions but I am just not confident that all will turn out well.

I don't know or even don't think this could be possible. But if you don't feel confident, just do not attempt anything.


text:
Escalate privileges in ADB shell to fix build.prop permissions
So I've done
# mv /storage/emulated/legacy/build.prop /system/build.prop

on my SM-T311 (Android 4.4.2) and now it won't boot.
The only change I've made was adding one line at the end:
net.hostname=Tableta

I've tried using adb shell (forum.xda-developers.com/showthread.php?t=1927198) to revert the changes, but my PC won't detect the device when connected with USB cable in recovery mode.
Although, when I select apply update from ADB windows detects it and it shows up in adb, but I can't do adb shell. (RESOLVED)
Is there a way to fix my tablet without losing my data, or am I doomed?
Okay, I've made progress. I've plugged the device in when it was boot-looping and windows detected it. Through device manager I've installed USB Driver for Windows, revision 7 and that made me able to use the ADB interface. I've confirmed, that build.prop file permissions and owner group are wrong. Unfortunately it wouldn't let me chmod the file or remount.

I've also tried
>adb root

but it hangs forever with no output so I have to close the console window.

If you have a custom recovery you could boot into you could dirty flash the stock rom of your tablet.

Unfortunately it's a stock recovery.

@MacGyver Then just flash one!

Thank You @AndyYan for finding that tutorial for me! I've flashed TWRP and fixed permissions with its File Manager! It's alive!


text:
Is there a way to disable the inactivity screen lock?
And I don't mean the Screen Timeout or the actual phone lock.
I have a Samsung Galaxy A8 running Android 9, and since I found out it hasn't been updated since 2018, AKA before OneUI, I decided to do it.
But since that update, when I don't touch it for a bit, LESS than the ten minutes I set the screen timeout to be, the phone screen get dimmer and lock itself with a 'drag to unlock' message.
It is annoying as I am using a third party program to help me grind in a mobile game, and what it feels like every five minutes I need to unlock the phone screen so that it can keep working. The screenlock must be new because it didn't happen before I updated it.
I tried to see how to turn that off, but all I find is the Screen Timeout and the phone's actual lock, same for google searches. I can't find ANYTHING on this screen lock.
Hell, even the 'Don't go to sleep while plugged it' dev setting doesn't stop it.
Edit : Added a picture to show what I am talking about.

The thing that cause this screen to appear is Game Booster.
I turned it off and I am on my way to uninstall it forever.
Here's the link to a reddit post related to how to turn this thing off.

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.


text:
How to regain lost access to encrypted data, known lock pattern
My S10e is running LineageOS 19.1, rooted with Lygisk.
After one specific reboot after changing the SIM card, it entered a boot loop where it showed the Lineage boot animation for a few minutes, then reboots.
I never got to the unlock screen anymore.
After reinstalling bootloader etc. as well as dirty flashing LineageOS, the phone boots up again but I don't get access to data on the interal /sdcard.
The partition is accessible but all files/folders are encrypted.
Trying to access them in TWRP terminal (or trying anything else like Nandroid backup) I always get the error "Required key not available".
So, my questions are:

can I in some way bring the phone's software to exactly the same state as before and making it recognise data, so that I can decrypt it?
will enabling phone encryption again and using the same lock/encryption pattern be sufficient? (I fear not)
Or is my assumption that it should be possible to reconstruct the key when using the same lock pattern on the same hardware & software flawed in general?
EDIT:
Is there any kind of redundancy of storing keys in LineageOS, which would allow to restore the original one?
I do have a SeedVault backup - does it include the original encryption keys?

Only in some old Android versions the cryptographic key (for the user data partition) was directly derived from the lock pattern/pin/password. On recent versions this is not the case instead random generated keys are used, protected e.g. using GateKeeper, so I doubt that you will be able to "reconstruct" the key. Not sure how exactly the keys management works on LineageOS.

/sdcard actually is /data/media so it's very unlikely you have decrypted /data

@alecxs I didn't mention /data but "data" on /sdcard, more specifically user data mounted from /dev/block/platform/13d60000.ufs/by-name/userdata

/dev/block/platform/13d60000.ufs/by-name/userdata is the only rw partition, all other partitions are mounted ro. all data is saved in /data. My best guess is the encrypted files in /data/media/ belong to another profile and therefore cannot decrypted with same credentials like the rest of files?

Ok, maybe I mixed things up, seeing different paths at different stages via adb shell vs TWRP terminal. Current situation is I see all those encrypted folders in /data/media/0 which belongs to my original profile (there never was any other profile on the phone).
Shouldn't I see a fileencryption= parameter in fstab somewhere (there is none)?

if the flag is gone in /vendor/etc/fstab* it must happened by magisk or any zip. this TWRP can handle LOS encryption

@alecxs Thanks for the TWRP link, never found that one while searching for a TWRP with encryption support for Samsung devices. However, what do you mean by "can handle LOS encryption"? twrp decrypt says "no crypto support was compiled into this build" just the same as the latest TWRP official one.
Access to /data/media/0 fails with "permission denied" instead of seeing encryted files, though.
And I don't have /vendor/etc/fstab, just /etc/fstab. Does it make any sense to add fileencryption= parameter there? If so, what syntax exactly, any non-default values with it?

(LOS) LineageOS FBEv1 encryption is supported, but Samsung encryption is not. maybe yours is FBEv2. /etc/fstab is from TWRP, you need to mount /vendor

@alecxs Did mount /vendor and found /vendor/etc/fstab.exynos9820, it contains the expected fileencryption= param.
How would I make TWRP use it, too? Tried using the same line in /etc/fstab and /etc/recovery.fstab* to no avail.

@alecxs Which fstab file does TWRP use?
Is there any way to tell if LOS FBEv1 or v2 is used (I'm on LOS 19.1)?
twrp decrypt says "Attempting to decrypt..." but then still "Not crypto support was compiled into this build"
And finally: should I rather move this conversation to XDA?
I'll only be able to look into this again coming monday, though...

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer.


text:
Connect to a Network over wifi or ethernet adapter, with twrp and use the terminal?
Im a noobie with twrp and android, i have Install it on a very cheap Nexus 5 and it works.
Is it possible now, connect with twrp to a network with the terminal, if not possible over WiFi could it be work with an ethernet adapter?
Can i modify or upate twrp to get network functionality?

I want only twrp on the phone without any android or rom an execute some terminal network commands, is it not possible?

TWRP is only a lightweight OS that AFAIK does not contain drivers for Wifi or Ethernet. You may be able to modify TWRP but effectively that would be like building your own custom ROM which isn't easy and requires to learn a lot.

@Robert no, building my own is not my intention and also not my area. Is it something similar to twrp with network functions, what is easy to install, handle, use and manage custom rom's if needed?


text:
Nexus 6 failed to update OTA 6.0.1 from MMB29V to MMB20X
Urgent help please.
the april 2016 patch was downloaded on the air and I performed update but after restart, The bot screen came with "error" and then the red error message is shown directing me to g.CO/ABH in which flashing is suggested. note after restarting, many applications together with settings app crash. I performed the OTA update again and no chance. Is there any solution except flashing? if the answer is no, so how can I perform a full backup before flashing? My serious aim is no data loss. ftp works through wireless but too slow. the usb mass storage function shows an empty folder on PC. USB debugging is connected but adb shows no device. Also in bootloader mode adb shell failed. The device is not rooted and recovery is locked. Here's the brief last log:

Source: shamu:6.0.1/MMB29V/2554798:user/release-keys
Target: shamu:6.0.1/MMB29X/2704508:user/release-keys
..
performing verification
using existing stash /cache/recovery/.....
deleting recovery /cache/recovery/---/--
..bytes free on /cache (.. bytes needed)
failed to verify blocks (expected ..., read...)
stat "/cache/...." failed: No such file or directory
partition has unexpected contents
failed to read block for diff
failed to execute command [.....]
deleting stash 5a79....
script aborted: system partition has unexpected contents
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Now tried to update from sdcard (stock rom downloaded for nexus) in recovery mode, got:
E:unknown volume for path [/sdcard]
-- Couldn't mount /sdcard.
Installation aborted
Repeated my try to update from ADB (adb sideload) but this error in the log:
sideload-host file size 1009749527 block size 65536
Finding update package..
I:Update location: /sideload/package.zip
Opening update package...
I: read key e=65537 hash=20
I: 1 key(s) loaded from /res/keys
Verifying update package...
E: footer is wrong
I:verify_file returned 1
E:signature verification failed
sideload_host finished
Installation aborted
I'm not sure even after data wipe the error remains or not, so prefer not to wipe yet, because the phone works!
Should I give up?

the title is wrong: from MMB29V to MMB29X, then I tried to flash shamu MOB30D

First off I'm assuming that the device is already flashing unlocked since you said you tried to flash the update from recovery. You shouldn't need a backup but make one anyways because recovery might be flashed over. Read everything first before you get started.
Download current image (the one you have now, you can try 29X or latest 30D), it's best to restore your system then update for guaranteed results and no misbehavior after reboot (I'm a little adventurous so I'd go for the 30D). unpack the .tgz and cd into the resulting directory.

fastboot flash radio radio.img
fastboot flash bootloader bootloader.img

Note the images aren't radio.img and bootloader.img, just do radio and tab and bootloader and tab.
Unpack the .zip that was extracted from the .tgz. cd into the resulting directory.

fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot

This should maintain all your data on the device after you reboot and I'm about 99 percent sure it'll work. So you shouldn't be needing to backup. If you run into problems after reboot you'll need to flash cache as well.
Reboot into bootloader again and use

fastboot flash cache cache.img
fastboot reboot

If it still doesn't work, you'll need to have a backup, reboot to fastboot and use the flash-all.sh that was extracted from the .tgz file. This would delete all your data but you can flash recovery again with fastboot flash recovery <image filename> and restore Data from the backup you did.
PS. If you have to flash cache you might lose some data but only relating to system apps and services.

Thank you, it was a silly incomplete ota update to Android N preview from Google and the main problem was the settings app crash. I got the solution from other caught in users: update from ota image provided by Google special for such problems. Unfortunately all data got lost before!


text:
Can a Nexus 6P be factory reset when screen cannot be used and phone off?
I broke my Nexus 6P screen, so am replacing it - usually I would factory the phone. However, I can't as the screen is completely black.
I power cycled the phone, but I am unable to enter the pattern to unlock the phone (fingerprint scanner only works after you enter the pattern after restart).
I used Android Device Manager to wipe it, but as I can't decrypt it through entering my pattern, it isn't online, so can't be wiped.
However, does any of this matter if the pattern can't be entered after power cycling? Surely the device is encrypted so my data is secure. And if anyone manages to guess my pattern, the device will be online and ADB will wipe it.
Should I do anything else?

Take a look at our locked-out tag-wiki. I remember there was a way via ADB to "reset" the pattern (to "none"), which might work in your case as well. Apart from which, it could be possible utilizing fastboot to do the wipe. Not sure concerning encryption here, but might be worth considering.

If you enter the password wrong too many times on your nexus device, it will factory reset your data (by default). It is also possible to factory reset through recovery mode by turning phone off, holding power and down volume simultaneously, clicking volume buttons until hitting recovery mode, then clicking factory reset.

Thanks - I can't enter anything on the screen though, and I am unable to see when the option for factory reset is highlighted in recovery mode.

OK it is a bit tricky but then you have to just click volume button and enter recovery mode by guessing. See this video: https://youtu.be/0nDLvy8F5qk and click buttons exactly as he says.


text:
Apps trying to install in background
I recently wanted to install a metronome app, so I downloaded one from the Play Store, but in the "install" step nothing happened. The app just wasn't there. I installed another one and forgot about that strange issue.
Yesterday though, something started to happen. Every now and then (and it's getting more and more frequently), I get a notification that some app tried to install itself (!) but was blocked because it's from "unknown sources", and it's prompting me to disable the "block install from unknown sources" check from Settings.
It looks like there are more than one apps trying to install themselves: "Superb Cleaner". "com.android.helper.patch[...]" and some more.
At first I though these might be system updates and was tempted to disable the "unknown source" block, but now I am worried I might have some malware on my phone.
I do have some sensitive information (browser logins, credit card data), and I also don't want to factory reset my phone.
Where should I search for the APK that is trying to install itself (or the APKs)?
EDIT:
It's this application: https://play.google.com/store/apps/details?id=com.andymstone.metronome. I'm not entire sure the app is the cause, but it's strange that I don't have it installed, but in my google play account it appears as "Installed"...
My phone is an Allview X2 Soul Style with Android 5.1.
After I have unchecked the "block apps from unknown sources", now I keep getting prompted the install screen for these apps. I keep pressing "Cancel" but they come again every half an hour or so. :(
EDIT2: Here are the adb logs requested: Windows and Activities
EDIT3: Dumpsys log for the suspicious package: Dumpsys

Does the app show up in the list of apps in the settings?

No. It does not appear anywhere.

You could try uninstalling the second metronome app and see if everything stops breaking then.

For the sake of completeness, can you provide the link to the metronome app that you installed? This may help us to test it in a controlled environment. Also, what's your Android model? There's a recent discussion on XDA that a company pushed an OTA with malware.

Editing the question...

Could you setup [tag:adb] in your PC and if the installation prompt appears again, use the PC to issue the command: adb shell dumpsys window windows and/or adb shell dumpsys activity activities and provide us the output? The output may be large (overwhelming), so use a code paste service, such as pastebin to upload it. Do provide us the screenshot for that installation prompt.

@Firelord Thanks for the suggestion, I have edited the question adding the logs you requested.

I have installed Metronome Beats on an emulator, run it, and.. nothing happened. The app's working properly, and there's no suspicious activity (the only permission is to have internet access, which is for showing ads, but nothing harmful). IMHO, it's not the cause (Play Store sometimes has that kind of bug). Now, reading the Activities log, it does certainly point to  com.android.tools.callassistant, which is the source.

@AndrewT. Thanks, but can you explain why you think that is the cause? And what could I do to remove it? I've done some Android programming a while ago but I have no experience with adb. I assume adb can do a lot of cool stuff though.

@AndrewT. : It appears that the calling package com.android.tools.callassistant is reported as malware by AVG and so as at many places on web per Google search. Seems to go by the label Caller ID. // Bogdan: could you do adb uninstall com.android.tools.callassistant and later see if adb shell pm list packages com.android.tools.callassistant reports anything?

@Firelord I have tried but it does not work: "Failure [DELETE_FAILED_INTERNAL_ERROR]" is the message I get.

I think it is a system app. Could you provide us the info of adb shell dumpsys package com.android.tools.callassistant? After that, do adb shell pm hide com.android.tools.callassistant.

@Firelord Done, edited the text to add the logs. I did hide the package, it says new hidden state is TRUE. How does that help? I'm thinking, can't I just disable these installation popups that keep coming over and over? There must be a way in Android to simply say "I don't want to install anything, period"...

pm hide makes Android treat the relevant package as being uninstalled, which means it wouldn't run at all unless it is reinstated. pm disable is more flexible and requires higher privileges but in the end, our goal to disable the package has been achieved. As for the prompts, if they are like this then my answer here might be of some service to you.

@Firelord Thanks. I have hidden the package, and indeed I cannot disable it - I am getting a Java SecurityException - Permission Denial. I'll wait and see if the prompts stops. FYI, I was getting the exact screen with "install blocked", then I unchecked the "don't install from untrusted source" checkbox, then the prompt changed to the install screen of the app. But it's still comming with the same frequency.

@Firelord Also FYI, although I have hidden the malware package, I can still uninstall an app... What does that mean?

Can you show me how the Unknown Sources setting looks like in your device? [Prompt] changed to the install screen of the app suggests me that you enabled Unknown sources setting. Now, did you follow my linked answer? It has instructions for non-rooted devices too. If you follow them you shouldn't be getting the installation screen at all. As for your last comment, hiding emulates that the program has been uninstalled but the APK (the code) still exists and it cannot run again unless you reinstate the app manually.

@Firelord Thank God! Hiding the package stopped all notifications! It's still there, but nothing bad happens anymore. Thanks a lot for the instructions! If you think it qualifies as a resolution for the question, post an answer and I will accept it.

Every now and then (and it's getting more and more frequently), I get a notification that some app tried to install itself (!) but was blocked because it's from "unknown sources", and it's prompting me to disable the "block install from unknown sources" check from Settings.

It's not a notification but a dialog and it looks like this:
(Click image to enlarge; image courtesy of Piyush)

At first I though these might be system updates and was tempted to disable the "unknown source" block, but now I am worried I might have some malware on my phone.

Yes, never enable that Unknown sources setting if you're in uncharted waters.

Where should I search for the APK that is trying to install itself (or the APKs)?

It's a bit difficult to find the app. I recommend finding the cause for the effect. In our case, the effect was the dialog hinting that the Unknown sources setting was blocked. That dialog is shown by Package Installer (a system-cum-core app). Package Installer is used by user or system apps which do not have the permission android.permission.INSTALL_PACKAGES to install an app. Since you did not attempt to side load an app, it stands to reason that an app called Package Installer without your consent. Our imminent goal is to find out that particular app.
The system service activity logs many important details. Among other things it shows the called package which in this case is Package Installer app with package name  com.google.android.packageinstaller or com.android.packageinstaller. It also shows the calling package or the package which launched an another package.
Find the package name
Now, using adb in PC execute the command:
adb shell dumpsys activity activities      # this command should be executed only when that dialog is in foreground

Demo output: notice the highlighted line:

In the highlighted line, the string after launchedFromPackage= and before userId is the package responsible for launching Package Installer app. In your case it would be a different package name. Note down that package name (henceforth denoted as <pkg>).
Locate the apk
Now that we know the immediate cause we can hunt down the home or in other words, the apk. Execute the command:
Note: Finding the location of apk is required only for forensics. If you're not interested in that, I recommend you don't bother with this step and immediately jump to the heading Uninstall/Disable/Hide the app.
adb shell pm path <pkg>

Demo output:

bash-4.2# adb shell pm path com.estrongs.android.pop
package:/data/app/com.estrongs.android.pop-1/base.apk

The string next to package: is the location of apk. You can also find the same information inter alia through the command:
adb shell dumpsys package <pkg>

Uninstall/Disable/Hide the app
If you know the label of the package or can get to know it through any means (such as with AppXplore) then go into the application manager under Settings app which typically comes down Settings → Apps → All apps in stock Android, find the malware app and uninstall it.
Things to note

If Uninstall button is grayed out and so as the Force stop button then your app must be a device administrator. In that case, go into the Security settings, choose Device administrators option and revoke the administrator privilege from the app. Come back and attempt to uninstall the app.
If you don't find the Uninstall option then your malware app is a system app. Whether your vendor shipped it or the app exploited your system or tricked you to install itself is another matter to deal with. For a system app, the button Uninstall is replaced by Disable.

If both Force stop and Disable buttons are grayed out then the app may be a device administrator as well. In that case, revoke that privilege and then attempt to disable the app.
If the Disable button alone is grayed out, then:

For a rooted Android: use adb to disable the app through the commands:
adb shell
su
pm disable <pkg>

To enable the app, replace disable with enable in aforesaid command.
You can alternatively use an app, such as Titanium Backup, to disable/freeze the malware app. You can also consider removing the apk using a file manager app.
For a non-rooted Android: provided that you're using Android 4.4.x or above, use the commands:
adb shell
pm block <pkg>      # for Android 4.4.x
pm hide  <pkg>      # for Android 5.x and 6.x

To unblock/unhide the package replace block by unblock and hide by unhide in appropriate aforesaid command. In this particular case, hiding the package would achieve the same result as disabling would.

The package would remain disabled or hidden until you revert the changes.

Note for readers
It has been confirmed by question's author that the malware app in their phone has the package name com.android.tools.callassistant. I found its label as Caller ID and it has been reported as a malware by AVG.

Some mobile phone manufacturers include an OEM app that automatically download and install other apps. (They reduce the cost of the phone or increase their profits with these marketing deals.) So, you will need to find and disable that app which is doing the sly installs. In my case, it was an app called Cube26.
Use apps like Startup Manager or Task Killer to see if find out which app is doing the downloads. An Android developer can also find out the app by looking at LogCat view of the IDE when the phone is debugged via USB. Ensure that your wireless router is not compromised.
Another thing you can do is to remove your Google account from the phone and add a new one with another gmail address. This will ensure that the apps that you have already downloaded don't get automatically installed again. This time, install only those apps that are well known and have good reviews. Before this, of course, remove/disable unwanted apps.


text:
Galaxy Note 2 JellyBean update
I have a Galaxy Note 2 GT-N7100 running on Android 4.1.1 JellyBean. The 4.1.2 update has been released a while back, but I still am reluctant to upgrade. I have read over the Internet that it causes the battery to drain faster than normal. Is there any truth to this?

Yes there was Issue with Battery drain but they had solved the issue and you can go for 4.1.2 and performance is good.

Yes its true and write know the issue is fixed so no need to worry u can update you version to 4.1.2.


text:
Why live wallpapers use phone call info
When I install any live wallpaper, I am shown a list of items that the app will access. Most of these live wallpapers also access the phone call details. I cannot understand why? Is there any technical reason related to it or something else. Also I think it may cause privacy damage.
So should I allow these apps access my phone call details?
Thank you.

As you don't give any example, we need to guess. I doubt it's for "stopping themselves" for the call dialog like Amit suggests (as a background "live wallpaper", they don't need to do that specially for call dialogs: either they generally need it for any dialog, or not at all). I rather suspect some ad module behind this (see my answer here for details). For ad modules, the combination of INTERNET and READ_PHONE_STATE are quite usual: the former to retrieve the advertisement material, and the latter to access your IMEI for identification (good cop: to know which ads you've already seen so they are not repeated too often; bad cop: to get IMEI, IMSI, your phone number, phone numbers you've been in contact with -- so a profile can be built).
Note that the developer of the app (or live wallpaper in your case) has no control at all what those ad modules do. All he can do is to take care to chose a "good one", and avoid the "more malicious" ad modules.

So, is there a way to differentiate between good cops/bad cops?

Follow the second link in my answer, check the last block there. It mentions 3 apps which are checking for "piggie-backs". The Lookout one includes details on the ad network's behaviour, see its screenshots in the playstore for an example.


text:
What does a streaming application do when I switch from mobile data to wifi?
If I am watching/listening to streamed video/audio whilst on mobile data and then become  connected to a wireless network, what does my phone do?
Does it keep streaming through mobile data or does it switch to wireless? Or is this something that's different across different applications.
My phone is a Galaxy S3, running Jellybean stock.

Usually recent versions of Android Handles these network switching automatically. When you are connected to WIFI, Your content would be streamed via WIFI connection .You can confirm this The mobile network symbol - H/H+/E/4g would not be available in the status bar of the mobile.
Usually, Android manages WIFI and Mobile network automatically, I.e., when both WIFI and Mobile Internet is enabled and If WIFI is avaialble, Mobile internet is not used. When  u leave the WIFI network, you would get connected via Mobile data. Hope this helps :)

I'm not sure this really answers the question (even though the OP marked it correct). You say switching is handled "automatically", but it's still a little vague to me that a stream that is already running would cross over to a wifi connection from mobile data. If I am listening to streaming radio, wouldn't I most likely hear a transition, a pause or break, when the service was moved from mobile to wifi?


text:
What is "Kies via Wi-Fi" in S3?
I see that "Kies via Wi-Fi" sends only 2.3 kb and receives only 876 bytes the last four hours in my phone, but it uses 26 mins of my phone CPU time and 20% of my phone battery. Is it something that I can stop it? If yes, how to stop it?
Thanks

Kies via WiFi (a stock ROM app) connects your phone to the Kies software on your computer via WiFi.
I am on CM10.1, which doesn't have Kies via WiFi. BUT, there is probably a setting in the Kies via WiFi app that lets you disable the auto-connect function.

Alternatively, when running Android 4.0+, it might be an option to simply freeze (disable) that app/service? I don't have a Samsung phone, so I cannot tell for sure -- but that would be what I'd look for if not using such an app.

It is an app that is used to update your smartphone or tablet. The only way to kill it is to root your phone and uninstall it. It is a system app and cannot be killed.

open kies via wifi, go to the settings, and turn off Autoconnect.
Settings -> More Settings -> Kies via Wi-Fi -> Settings -> Auto connect off


text:
How to prevent Android from creating LOST.DIR on SD card?
After the phone restarts, there is a LOST.DIR folder created on the external SD card. Is it possible not to create this folder if nothing is lost?

LOST.DIR is just a storage space (directory) for files that were recovered upon boot. You can safetly remove it with no problems. The sysytem keeps it just in case you want to get your recovered currupted files back.
A quick google search yielded:

LOST.DIR - what is it?

As for preventing it from being created, just prevent the SD card from becoming corrupted. Here are some things to keep in mind while using an SD card:

Always eject before removal
Never remove while files are being modified
Never remove from Android device while device is on

If you have your device connected to the computer, the SD card will usually automatically mount itself on the computer. Remember to eject it before disconnecting the device.

This thread has a ton of good info. Basically the gist of it is, if you are following all of the precautions to keep the SD card from getting corrupted (ejecting before removal, ect...) then the SD card is partially incompatible with your device. If you move to a higher class SD card, the problem usually goes away on its own.

I wonder if that directory could be the equivalent of lost+found on unix systems.

@ott I would imagine that it is, considering that LOST.DIR is created at startup after a disk check, which is exactly what happens on *nix with lost+found.

"As for preventing it from being created, just prevent the SD card from becoming corrupted." does not work for my device. After I delete the LOST.DIR folder, restart the device, a new empty LOST.DIR folder is created.

@ohho see my edit

"running a defrag program" is a nonsense suggestion, since fragmentation on flash media is a non-issue.

I don't get the last part: Basically the gist of it is, if you are following all of the precautions to keep the SD card from getting corrupted (ejecting before removal, ect...) then the SD card is partially incompatible with your device.

If you are doing everything you can to keep it from corrupted, and it is still getting corrupted, then the SD card is partially incompatible with your device. Buy a higher class card and that should fix your problem.

Delete LOST.DIR folder.
Create a file named LOST.DIR

When system tries to create LOST.DIR folder,it can't because a file exist with the same name.


text:
How do I transfer music files to Nexus 4
I plugged in Nexus 4 to my windows machine(XP Service Pack 2) and it didnt recognise or install any software automatically. I downloaded Google USB Driver from SDK Kit and installed it and now it shows up as recognised device in the Device Manager, but how do I copy files to Phones Storage ? There s no send to option as its not connected as a USB mass storage(which is not there in this device as well)

AFAIK the Nexus 4 does not use UMS but MTP instead. On Windows, it should show up directly in the Explorer. Having neither a Nexus 4 nor Windows, I can only refer to hear-say -- and refer you to How To - Connect Nexus 4 to XP like MTP device - xda-developers

The XDA article How To - Connect Nexus 4 to XP like MTP device describes the steps needed for Windows XP as follows:

Connect your Nexus to PC.
Go to My Computer>Properties>Device Manager and double click on MTP device
Go to Details and copy (Ctr+C) info like (USB\VID_18D1&PID_4EE2&MI_00) (you can copy it from here too, if it is identically)
Unplug Nexus from PC.
Go to C:\Windows\inf folder (it's hidden)
Find a file "wpdmtp.inf" and open it with any text editor (Notepad)
Modify or Paste (Ctrl+P) what did you copy at step "3" as bottom I showed.

; Installation inf for devices supporting Media Transfer Protocol (MTP)
;
; Copyright (c) Microsoft Corporation.
;

[Version]
Signature="$WINDOWS NT$"
Class=WPD
ClassGUID={EEC5AD98-8080-425f-922A-DABF3DE3F69A}
Provider=%Msft%
LayoutFile=layout.inf
DriverVer=02/22/2006,5.2.5326.4762

[DestinationDirs]
MTP.Files.Kernel = 12
MTP.Files.XPRT_USB = 11
MTP.Files.Core = 11
MTP.Files.UMDFDDriver = 12,UMDF ; copy to system32\drivers\umdf
[Manufacturer]
%MfgName%=Generic,NTx86,NTamd64
;
;Device is identified by Microsoft OS descriptor
;If your device does not support it, use specific VID & PID for identification
;
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
;
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00

Save and close the file.
Connect your Nexus to PC
Go to Device Manager and update MTP driver.
Tick chekbox "Install the software automatically (Recomenden)" on driver installation dialog and install driver.
  Wait for a moment and you can see Nexus 4 like an MTP device.

Now you should see the MTP device, and be able to transfer files to it.
Hope this solves your issue :)

Yes this helped, but I got 2 problems, 1> File was nt there - So downloaded WIn Player 11 and it was solved. 2> I had installed ADB driver before, so when I uninstalled that and tried to install driver it always instalelled ADB driver instead of MTP. So instead I chose Manual Location and it gave 2 options install as ADB or MTP and I chose as MTP and all is good now :) Thanks for that link ! Didnt come across that link while I was googling,

Glad it helped -- and thanks for the updated details!


text:
Is there anyway to increase the bass in Jelly Bean?
I know the iphone had a similar feature built in. I'm using a Samsung Galaxy S4 with Android version 4.2.2

Have you tried to use one of the many equalizer apps at Google Play?

@Izzy Ah, perfect!

You can access the built-in graphic equalizer by going to Settings, then Sound, then Audio effects.


text:
Do I need to wipe when upgrading from CM10 to CM10.1?
I am using CyanogenMod 10 on my device and saw that CM10.1 (Android 4.2) is available on get.cm.
If I upgrade, do I have to wipe my phone or will it just work?
Or what problems will I have to expect if I don't factory reset it before?

It just works, no need to wipe.
You don't need to wipe, according to a blog post on CyanogenMod's Google Plus channel:

Upgrading from CM10 to CM10.1
As you may have noticed, we started updating some devices from cm10 (Android 4.1) to 10.1 (Android 4.2) during the weekend. The upgrade process has been tested extensively for the older devices (manta and mako didn't have that problem since they started out with 10.1), so you should be able to update directly without losing any data.
The single application known not to work is the Clock: Our changes to 4.1's clock to add the Stopwatch and Timer in CM10 aren't compatible with Google's own implementation of those features in 4.2 (which we're using in cm10.1); If your clock starts crashing after upgrading to 10.1, simply go into the Settings -> Apps menu, choose Clock from the All tab, and hit "Clear data".

Though not really needed (as to that note), it never hurts to wipe Dalvik and clear caches. In some cases (especially when one heavily installed/uninstalled apps for testing) this even gives a speed-burst -- and it won't delete any data.

You don't need it. Even CM maintainers only have sarcasm left for that: https://plus.google.com/115049428938715274412/posts/7u9rJsNrYzd


text:
How to flash a zip file without signature verification?
I have lenovo a3300-gv running android kit-kat. I tried to flash a .zip file in it using flashify. But it fails to flash as signature verification fails. I read some articles stating to flash in CWM/TWRP recovery to avoid this error. But I can't get custom recovery for my device. So, is there other way to flash in stock recovery without signature verification?

Unless you could somehow get the manufacturer's private key to sign it, no.

I'm afraid no (no easy one). As you have no custom recovery for your HW platform there is chance you can't rebuild a firmware for your phone. Bypassing this signature is possible only by modifying the source (actually this is what is done in teamwin or clockworkmod recoveries).


text:
Accessibility services get disabled automatically
This Christmas I gave a Wiko Lenny 3 to my son, it comes with Marshmallow.
When trying to install a parental control I sadly discovered that there's a bug (I suppose) that is well documented for Lollipop/Samsung, that prevents accessibility services to be activated.
In other words, as soon as I activate the parental control in the settings/accessibility/services option, it always appears off, although it's on, and resets to off randomly and at every reboot. This makes totally unusable the parental control.
The questions are:

is there a fix for this? (Any solution with battery savings was tested with no success)
is there a way to understand, via logs or monitorings, what is preventing the services to be activated?
would rooting some how change something?
is it safe or even possible to install a different and clean Android version?

Related/possible dupe: Accessibility services gets disabled automatically

Changing the launch setting to start manually and not automatically seems to work.
In Huawei devices, it can be found in Apps - app name - Battery - Launch.

Battery saving options, on the other hand, didn't help in my case.


text:
Added lock screen pin to encrypted device - can't unlock on boot now
I have an encrypted cyanogenmod 13 device. I set the password manually via the command line using a guide like this. More recently I added a lock screen pin, and I think I set it to not ask on boot but I'm not certain now. I rebooted the device for the first time since adding the new pin but I can't unlock it now.
When it boots, it's loading the same disk unlocking screen as before, but it's asking for the pin instead. Entering it doesn't work, however. Since it's expecting a pin all it presents is a number pad - can't type the encryption password in case that's what it wants.
The question is, obviously, how can I unlock it. I know both the encryption password and the lock screen pin so I could do it via the USB+command line but neither ADB nor fastboot detect any devices.
Some users elsewhere have suggested trying the sim pin but a) same thing happens when sim is removed and b) the sim pin doesn't work anyway.
I'd like to get this unlocked soon, if not possible I need to do the whole setting up from scratch process as soon as possible.
Note: I have access to the device via the teamwin reovery thing which has a filemanager and terminal. Is there some command I can run to set the unlock type/keyboard back to normal?

Edit: I was able to use ADB when in recovery mode, but obviously changes made to settings.db don't propagate. What do I need to do to regenerate the "initramfs" or whatever android uses that contains all the necessary data to boot when encrypted? I assume that it has it's own copy of settings.db.

I explicitly said I know the password, the linked question is about hard resetting a device when you don't know the password. I just want to know how to make the device present the right keyboard so I can type the password in.

Since I have access to the recovery, I simply backed up everything, did a full-format (which wipes the encryption), restored, disabled the damn lock screen pin and then added the encryption again.
Not the ideal solution but hopefully helps someone in a similar situation.