text:
Phone always goes to TWRP recovery when powered on
I just recently installed/flashed TWRP Recovery on my rooted Samsung Galaxy S6 running Android 5.1.1 with no custom rom.
TWRP Recovery runs fine I assume (haven't tried any features), although whenever I now boot up my phone it goes straight to TWRP recovery. I definitely do not want this, help?
How I installed TWRP Recovery:

Downloaded and installed Flashify from Play Store
Opened Flashify and selected Install Recovery (or similar) and selected TWRP
Downloaded ..forgot.. It ended with .img
Pressed "Yup!" To flashing it
Pressed "Reboot Now"

I don't really know much about flashing stuff/TWRP and really any advanced root stuff. How do I make my phone not boot into TWRP Recovery every time (I can't access my phone now...)Phone's model number: SM-G920I

DM-Verity

"This device uses dm-verity!
  This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."

DM-Verity Reference: https://twrp.me/devices/samsunggalaxys6.html
Is most likely the culprit here.  What this does is run a check on boot and if you are using the stock kernel and it sees a different recovery or even ROM than DM-Verity expects it will not allow you to boot the OS and only recovery so that you can put the official OS and recovery back.  The only way to fix this is to use a custom kernel (or custom ROM that includes a custom kernel),
OR of course if you were to do a full factory image flash (using ODiN you visit Samsung site and get the Factory image meant for your device (be sure model matches your phone's before downloading), put device in download mode and run Odin to flash the factory image.  Of course you will lose root and the custom recovery this way, but it should boot.
Since you did not include your actual model number I hesitate to link just any ROM or Kernel as they may be intended for another variety of the S6.  If you would like comment or edit your question and add the SM-blah model number and I can be of more help in linking ROMs/Kernels (not really what this site is for, but if you need those to get your phone basically running I can at least find the most popular variety of what you need which should hopefully get you working again.  Yuo can google SM-blah ROM XDA and that should give you links to the XDA forums for your device.  They are very well know community that does custom Android work of all kinds.  I can't say it enough make sure you verify your phone's SM-blah model number against the developers ROM info page to make sure it is actually meant to be used with the exact version of the S6 you have.
Possibly Flashify (DOUBT IT)
Flashify selected the wrong partition automatically (it does warn you to verify it chose the right partition before flash), so you would need to flash a ROM and start again (Flash ROM, GApps AND Recovery.zip [https://twrp.me/devices/samsunggalaxys6.html])  DO NOT FORGET TO FLASH THE RECOVERY IF IT IS IN WRONG PLACE YOU NEED TO GET IT IN RIGHT PLACE BEFORE RESTARTING AFTER FLASHING THE OS IF NOT YOU MAY LOSE THE RECOVERY.

Added my phone's model number at the end of my question. I will be more than happy to use a custom kernel/rom. I was kinda assuming I could get away with it because I used an auto-root kernel to root my phone, so I thought I could get away with it.

Well auto root gives you root and it may also include a kernel, but that would most likely be a separate run through from the root procedure (though it could copy a kernel during root.  Also if your phone has had an update and is using a different version of Android may need an updated utility.  You have root though or no super user and you would have failed the recovery flash.  Is it TWRP or stock recovery when it boots now?  On it with model hold for more info.

Hmm? I didn't do anything yet, so it's still TWRP? I have SuperSU (chainfire). Also haven't updated my phone (5.1.1) since rooting it.

Here is a ROM I would suggest if you are just getting started.  It is a modified stock ROM [Marshmallow]: http://bestandroidstuffs.com/install-android-6-0-1-xtrestolite-rom-on-galaxy-s6-sm-g920i/
Another one is a port of S7 Edge ROM giving you all the features S7 Edge has: http://www.teamandroid.com/2016/04/08/install-android-601-noblerom-galaxy-s6-g920i-marshmallow-custom-rom/  and finally a CM13 [unofficial]: http://forum.xda-developers.com/galaxy-s6/development/rom-galaxy-s6unofficial-cyranogenmod-t3434849

Here is just a custom kernel (modified stock) if all you wanted to try was just to swap out the kernel: http://forum.xda-developers.com/galaxy-s6/development/rom-tyrannus-rom-v1-0-31-07-2015-t3169760  Finally the XDA Forums [JUST BE SURE TO ALWAYS CHECK TO MAKE SURE WHATEVER YOU DOWNLOAD IS FOR THE SM-920I] as this section of their forums covers about 15-20 different versions of the S6: http://forum.xda-developers.com/galaxy-s6

How do I download the files for the Marshmallow ROM and add them to my phone storage if I can't access my phone or is it possible to access it via PC (even with lock screen enabled)? Also, what data is being deleted when I do a factory reset from TWRP?

Well you have several options if you can use Micro SD card you could remove it from phone use adapter and plug in to computer copy files and put back in phone.  TWRP should have a file manager and I believe even allows you to mount storage over USB cable to computer if you check in it's settings.   You could use an adapter which enables you to plug USB drive into your charge port (usually like under $5) if your device and/or recovery supports USB OTG (Probably does).
Worst case you need to manually boot to download mode and use Odin (will need ODIN ROM image frm XDA forums or Google search)

SOO worst case is you find the XDA unbrick thread with your Factory ROM in an image meant for use with Odin then download that and the right Odin version (should be whole thread with instructions on how).  Then Connect USB from computer to phone do manual button press boot method to get to download mode open Odin (with admin rights), open image file with Odin and then flash.  This will be a full factory image without root.  You could pre-collect everything then use same root method and when you get recovery on boot then flash custom stuff.
That should make sense I hope.

http://www.gizmoadvices.com/unbrick-unroot-galaxy-s6-and-galaxy-s6-edge/ should be what you need. They say unroot in the title, but they have you do that by flashing the factory image so really this is how to unbrick your Samsung S6

"Unbricking" the device seems to be a good option, but what will it change, eg Change back to Stock Recovery, change kernel? Because I rooted my phone using an auto-root kernel, will it mess up if I change my kernel? And, afterwards, can I install a custom rom and then reinstall TWRP Recovery and it will work?

Unbricking will take the phone back to how it was when you got it out of the box, and then you can choose to root it again if you want.  If you use the same method just download the custom Kernel (could try just this if using a modified stock kernel and see if it boots or skip this and go for custom ROM and Gapps replacing the factory ROM) ROM, Gapps, Recovery and whatever else then when you get to the point it boots to only recovery the files are already there.

Wait, couldn't I use the adb push to put the ROM files on my phone instead? Otherwise, I will try unbrick it and root again, install a rom and then try install TWRP again. But it will delete all my data? The only thing I care about is my photos, how can I transfer them to my computer from TWRP Recovery?

You could try it, but depends on if the recovery supports it.  ADB is a daemon that runs in the background so if you can not boot in to Android ADB is not available.  I think TWRP has tried to do something in allowing ADB during recovery, but I think it is a custom version and I don't know if it has access to the actual device storage (depends whats mounted which there is a mount menu in the recovery, but if only /recovery is mounted its only thing you could copy to which would not have enough room for much of anything and would not be accessible for installs).

It's not a bad thing to take the phone back to factory.  Yo already know how to root it, and yeah it's extra steps, but it is Friday and the weekend now just set aside a couple hours get the factory image and use an older Windows machine if your current one does not like the exe.  You can not put the exe on the phone it will do nothing for you the factory image is inside that exe and you need to run it to get what you need out of it your phone can't use it.

Which kernel/rom should I install to get out of the "soft brick", and if possible can you tell me how to instal, with TWRP Recovery? I will try putting the file on the phone with ADB. If that doesn't work I will take the phone back to factory. I don't really want to reset it to factory, since I want to keep my photos, but it won't matter that much if it's the only (and easiest) option to fix my phone.

I provided links to both a modified stock kernel and modified stock ROM for your phone in earlier comments.  Those links take you to the XDA threads where you can read the info about them if you wish before downloading.  They are not direct file download links.  You can also find more info on things like using ADB in recovery for your device possibly in the XDA QA threads.

I decided to do the factory reset with Odin. I connected my phone, ran Odin and put my phone into download mode. I then downloaded the firmware. It says it's a 1.7GB file, estimating 7 hours.. So I took my phone out of download mode by holding Power+Up+Down volume. I turned it back on, and some how it booted up normally. Any idea how putting my phone in download mode could have any effect? Restarted phone and still booted up. Should I try go in recovery mode and see if TWRP is still there?

@Mike may I suggest you go over all those comments and see what can be integrated with your answer, and then delete the ones of you that got obsolete plus "flag obsolete" those of Kamdroid which are no longer needed? Currently, it's a bit too long a tail of comments here :)


text:
Mount "/" andriod in pc for scan with av
I want a method for scan all andriod system from my pc with a antivirus, for example I've a backup with CMW, but the problem is that i need extract "tar" files and delete virus, then repack tar...
Do you know how can I mount "/" files of andriod to my pc ?
Note: I have root with busybox, but the virus is powerfull, he is with many files in /system /etc /data ... and others... I could flash it, but i need delete files with av... I've scanned the tar files, and eset nod32 found more than 50 infected files
Another Note: Factory-Reset isn't not way, because the virus is in /etc, /data, /system/ and anothers...**
Thank you very much.
Greetings!

I don't know if a PC-Antivirus can scan and remove Android viruses... My advice would be a complete factory reset if you don't have any important data on your phone that you didn't back up. You can always browse and export your file from old Nandroid backups with an app, for example this one: https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=de

You should remove those malwares before doing a backup! If your phone is rooted, just install BusyBox and I'll show how to remove them. Only data partition can be mounted to be seen in PC

Ty dude, but factory restore not work for advanced virus, because its are in /system and /data and /etc... etc... could flash the device but i need remove it with av

@esQmo The av have detected 50+ viruses in the tar files of backup... I have root and busybox... but its is very hard, because the names are strange

The better way is to remove them manually or automatically by a tools. Or install system remover apps and unista all malwares then make a backup

Safest way is to factory-reset and then install a clean ROM. Everything else is prone to errors. No need to say to not restore stuff from the current state (to not have the malware return).

@Izzy Factory-reset NOT WORK, The virus is in /etc, /system, /data, and others..

@Milor123 read again: I wrote factory-reset and then install a clean ROM. Installing the ROM overwrites /system and others. Depending on the recovery used, you could even do a format before that.

@Izzy This won't work on Samsung devices flashed through Odin, unless you check NAND clear all option. The malwares will still there. The best way I think, is removing them manually as one can do for bloatwares then install a clean ROM.

And pray you didn't miss a thing, @esQmo – well, another reason I won't buy a Sammy device. Thanks for pointing out!

@Izzy I won't, I'm careful. And besides, malwares package names are easily identifiable. Using system apps make things easier than using a command terminal.

source: Stack Exchange

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

sort: votes


text:
TWRP not recognize my sdcard
I've ported a twrp 3.0.2 to my device (kitkat 4.4), all works nice, but when I try press backup, and select store, only shows the internal store...
Device description: Azumi a50c+ with rom Kitkat 4.4. Its a MT6582
NOTE: this works fine in twrp 2.7 but then try change to 3.0.2 the sdcard cant be select in the options
My partition is:
=================
Phone store: 8GB, divide in:
    Internal store >> 4.2GB
    ext sd card (this is a internal partition of phone store) >> 2.33
    System rom.....

=================

    =================
SDCARD: 16 GB

THIS IS THE PROBLEM, In the recovery sdcard 16gb is detected in this partition in mmcblk1p1 but cant see the sdcard in "select store" option of   twrp 3.0.2.

=================

What files of ramdisk should I modify?  check the images...

What is the best way to fix bug of my TWRP 3.0.2? Thank you very much

Which device? I guess you done something wrong or missed in fstab so it doesn't handling it well. That happens when you port. The best way is to find device tree and modify it to fit twrp needs and compile it from source. Question will probably be locked due it more fits developement questions. So feel free to contact me if you need help i'm not expert but maybe I can help.

@ЈеднорукиКрстивоје Thank you very much dude, I've solved it, the problem was in fstab and one line of init.rc... Greetings! :D

@ЈеднорукиКрстивоје hey dude, can you help me with this: https://android.stackexchange.com/questions/169120/format-preloader-and-reflash-mtk6582-sp-flashtools Thank you

I've solved it
Note: this process requiere extract files of recovery.img, you can use "CarlivImageKitchen"

add this line and flags to the /etc/recovery.fstab files, and chage /sdcard to /external_sd example:
The mmcblk1p1 is the block of my sdcard:
 # Extructure is:
 # Mountpoint #type  #partition block     # block             #flags

/external_sd  vfat  /dev/block/mmcblk1p1  /dev/block/mmcblk1  flags=display="Micro SDcard";storage;wipeingui;removable

Problem Solved!

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

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


text:
Andriod 4.4.2 "optimizing app x of 50 android" after flash Gapps
I've flashed Gapps for kitkat in my andriod 4.4.2, and now when I turn on the phone, The problem is that always said "optimizing app x of 50 android", the which take much time. (I also happened to this with a cell phone jellybean after flash Gapps)
I've tried advance factory reset from TWRP but this not change, also reflash other Gapps..
Note: I dont wanna update kitkat to Lollipop because lollipop have so many bugs in my phone (Azumi A50+)
Help me please, thank you very much

Download another Gapps and flash it.

I've tried it too @esQmo

Download the minimal gapps from micro to nano, from here: http://opengapps.org/

If you have a stock firmware, there may be compatibility issue with the existing Gapps.

I've tried flash nano instead of pico, but its send me error 70 (because system haven't enough space), then the playstore and services are bugged, but it solved my problem xD, I dont know but accidentally the error solved my problem, now I've reinstall 'google services and playstore' with TitaniumBackup. Thank you very much dude @esQmo

You're welcome. I'm now going to put it as an answer, just mark it as ACCEPTED for other to find it.

@esQmo ty dude, with pleasure friend

I guess you have a stock firmware, this might lead to an incompatibility with the existing Gapps.
Try downloading the minimal Gapps,  nano or pico package from here

Note: I think that if this not work also could try remove all services of google with a tool as TitaniumBackup and reboot, then reinstall manually NOT WITH Gapps. Thank you very mucho. Greetings!

Does that happens only on first and second boot or everytime you boot phone? If you use custom rom it's probably rom releated bug, contact developer and report bug.

I happends Always after load the logo, in my phone I cant use custom roms, all roms have many bugs as "the camera lost 9 Megapixels"

@Milor123 Then why did you use TWRP to flash gapps?

Its my recovery, Is it wrong to use it?

The thing is why flash gapps when you use stock rom that allredy have gapps

Because I was problem and the playstore stopped, then I had to install Gapps

You should try factory reset, not flash gapps over. However now try flashing stock rom via software on pc or via download mode (depends on phone)

Factory reset not work dude

TRY FLASHING STOCK ROM, do you even read what I wrote?

Yes it could be solved with the stock rom, but I need my data system and others things, I want not lose my system information

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


text:
Apps not showing .How to reinstall the factory apps
Ok so i rooted my Samsung Galaxy Tab 2 10.1 inch tablet and i wanted to get rid of some useless factory apps that i never used but after i did that and exited kingroot i had no applications on my screen..my wallpaper is still here,the bar on top from where u can activate wifi, gps etc.(i dont know how its called sorry) is still functional (and i can go to settings from there but it doesnt work every time) and the digital buttons are working perfectly..it seems like everything works fine exept that when i restart i get the com.android.phone error. I accessed google from the task killer from where i can also go to the app manager witch works good also.
PS:Factory reset doesnt resolve the problem.

I also noticed that if i press the home button or the go back button in order to leave to the home screen it doesnt work..i have to kill the current tab in order to get to my actuall "home screen"

Sounds like you removed the launcher (homescreen) along with some other critical stuff.
For now, go to Settings and turn on USB Debugging, plug into your PC, install appropriate drivers, and sideload another launcher app, so that you can see all your apps and backup data. After backing up, flash a factory firmware via Odin from your PC to get a fresh start (you do need to root again).


text:
How does handover from wifi to gprs work?
I start a google hangouts call and I'm connected to wifi.
Then when I leave home, the call is handed over from wifi to GPRS.
How is this done?
Does the app help doing the handover or is this transparent to the app?
When switching to GPRS, the phone gets a new ip address, so a new connection is necessary, right?


text:
Listing all android processes from PC
Is there a way to list all the running processes in an Android phone from a PC? Maybe using adb?
I remember a mode in the old Eclipse version of Android Studio, was called LogCat. Is it possible to have something similar from console ?

Naturally adb shell ps

Logcat records info, warning and other stuff thrown by apps when necessary - it doesn't explicitly tell you what processes are running.
If the list is what you want, use the classic Linux command top. Android also have it (although not as friendly to use). Here's an example output from my own Nexus 6P:
shell@angler:/ $ top

User 0%, System 0%, IOW 0%, IRQ 0%
User 15 + Nice 1 + Sys 22 + Idle 2451 + IOW 2 + IRQ 1 + SIRQ 1 = 2493

  PID PR CPU% S  #THR     VSS     RSS PCY UID      Name
 4060  1   0% S    15 1987132K  52032K  fg system   com.quicinc.cne.CNEService
 4913  4   0% R     1   6260K   1432K  fg shell    top
 1423  1   0% S   123 3282976K 134448K  fg system   system_server
 3487  0   0% S    37 2133616K 144432K  fg u0_a19   com.android.systemui
  379  1   0% S    12 197504K  12460K  fg system   /system/bin/surfaceflinger
24196  0   0% S     1      0K      0K  fg root     kworker/u17:4
10311  3   0% S     1      0K      0K  fg root     kworker/3:4
 4139  0   0% S    34 2230348K  62884K  bg u0_a156  com.taobao.idlefish:channel
   41  4   0% S     1      0K      0K  fg root     ksoftirqd/4
  258  0   0% S     1      0K      0K  fg root     mmcqd/0
    8  1   0% S     1      0K      0K  fg root     rcu_preempt
 4848  0   0% S     1      0K      0K  fg root     kworker/0:2
32569  3   0% S     1      0K      0K  fg root     kworker/u17:9
  447  3   0% S     1      0K      0K  fg root     irq/215-fc38800
  383  1   0% S     1   6356K   1176K  fg root     /system/bin/msm_irqbalance
  297  3   0% D     1      0K      0K  fg root     msm-core:sampli
  245  0   0% S     1      0K      0K  fg root     cfinteractive
 4011  0   0% D     1      0K      0K  fg root     mdss_fb0
21510  2   0% S     1      0K      0K  fg root     kworker/2:2
   25  1   0% S     1      0K      0K  fg root     perf
   30  1   0% S     1      0K      0K  fg root     kworker/1:1H
   31  1   0% S     1      0K      0K  fg root     smd_channel_clo
   32  1   0% S     1      0K      0K  fg root     smsm_cb_wq
   34  1   0% S     1      0K      0K  fg root     deferwq
   35  0   0% D     1      0K      0K  fg root     kworker/u17:0
   36  1   0% S     1      0K      0K  fg root     rpm-smd
   38  3   0% S     1      0K      0K  fg root     irq/48-cpr
   39  3   0% S     1      0K      0K  fg root     irq/51-cpr
   40  4   0% S     1      0K      0K  fg root     migration/4
   43  4   0% S     1      0K      0K  fg root     kworker/4:0H
   44  1   0% S     1      0K      0K  fg root     mpm
   46  1   0% S     1      0K      0K  fg root     writeback
   47  1   0% S     1      0K      0K  fg root     bioset
   48  1   0% S     1      0K      0K  fg root     crypto
   49  1   0% S     1      0K      0K  fg root     kblockd
   50  1   0% S     1      0K      0K  fg root     khubd
   51  4   0% S     1      0K      0K  fg root     system
   52  1   0% S     1      0K      0K  fg root     ipa_power_mgmt
   53  1   0% S     1      0K      0K  fg root     sps_ipa_power_m
   54  1   0% S     1      0K      0K  fg root     ipawq14
   55  1   0% S     1      0K      0K  fg root     iparepwq14
   56  1   0% S     1      0K      0K  fg root     ipawq43
   57  1   0% S     1      0K      0K  fg root     iparepwq43
   58  1   0% S     1      0K      0K  fg root     ipawq13
   59  1   0% S     1      0K      0K  fg root     iparepwq13
   60  1   0% S     1      0K      0K  fg root     ipa_power_mgmt
   61  1   0% S     1      0K      0K  fg root     ipa_rm_wq
   62  1   0% S     1      0K      0K  fg root     ipa_interrupt_w
   64  4   0% S     1      0K      0K  fg root     kworker/4:1H
   66  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   67  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   68  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   69  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   70  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   71  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   72  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   73  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   74  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   75  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   76  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   77  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   78  1   0% S     1      0K      0K  fg root     irq/261-msm_iom
   79  1   0% S     1      0K      0K  fg root     irq/263-msm_iom
   80  1   0% S     1      0K      0K  fg root     irq/102-msm_iom
   81  1   0% S     1      0K      0K  fg root     irq/102-msm_iom
   82  1   0% S     1      0K      0K  fg root     irq/102-msm_iom
   83  1   0% S     1      0K      0K  fg root     irq/102-msm_iom
   84  1   0% S     1      0K      0K  fg root     irq/74-msm_iomm
   85  1   0% S     1      0K      0K  fg root     irq/75-msm_iomm
   86  1   0% S     1      0K      0K  fg root     irq/75-msm_iomm
   87  1   0% S     1      0K      0K  fg root     irq/75-msm_iomm
   88  1   0% S     1      0K      0K  fg root     irq/75-msm_iomm
   89  1   0% S     1      0K      0K  fg root     irq/273-msm_iom
   90  1   0% S     1      0K      0K  fg root     irq/273-msm_iom
   91  1   0% S     1      0K      0K  fg root     irq/272-msm_iom
   92  1   0% S     1      0K      0K  fg root     irq/97-msm_iomm
   93  1   0% S     1      0K      0K  fg root     irq/97-msm_iomm
   94  1   0% S     1      0K      0K  fg root     irq/97-msm_iomm
   95  1   0% S     1      0K      0K  fg root     irq/350-msm_iom
   96  1   0% S     1      0K      0K  fg root     irq/350-msm_iom
   97  1   0% S     1      0K      0K  fg root     irq/350-msm_iom
   98  1   0% S     1      0K      0K  fg root     irq/298-msm_iom
   99  1   0% S     1      0K      0K  fg root     irq/298-msm_iom
  100  1   0% S     1      0K      0K  fg root     irq/298-msm_iom
  101  1   0% S     1      0K      0K  fg root     irq/79-msm_iomm
  102  1   0% S     1      0K      0K  fg root     irq/78-msm_iomm
  103  1   0% S     1      0K      0K  fg root     irq/78-msm_iomm
  104  1   0% S     1      0K      0K  fg root     devfreq_wq
  105  1   0% S     1      0K      0K  fg root     cfg80211
  106  0   0% S     1      0K      0K  fg root     irq/15-bcl_vbat
  107  1   0% S     1      0K      0K  fg root     irq/460-bcl_iba
  108  1   0% S     1      0K      0K  fg root     rpciod
  131  7   0% S     1      0K      0K  fg root     kswapd0
  132  2   0% S     1      0K      0K  fg root     ksmd
  133  1   0% S     1      0K      0K  fg root     fsnotify_mark
  134  1   0% S     1      0K      0K  fg root     nfsiod
  154  1   0% S     1      0K      0K  fg root     ad_calc_wq
  155  0   0% S     1      0K      0K  fg root     rot_commit_work
  156  0   0% D     1      0K      0K  fg root     mdss_dsi_event
  157  1   0% S     1      0K      0K  fg root     apr_driver
  158  1   0% S     1      0K      0K  fg root     pil_vote_wq
  159  0   0% S     1      0K      0K  fg root     shm_svc
  160  1   0% S     1      0K      0K  fg root     qmi_hndl0000000
  161  1   0% S     1      0K      0K  fg root     msm_ipc_router
  162  1   0% S     1      0K      0K  fg root     k_hsuart
  163  2   0% S     1      0K      0K  fg root     msm_serial_hs_0
  164  2   0% S     1      0K      0K  fg root     msm_serial_hs_0
  165  0   0% S     1      0K      0K  fg root     hwrng
  166  0   0% S     1      0K      0K  fg root     diag_real_time_
  167  1   0% S     1      0K      0K  fg root     diag_modem_data
  168  1   0% S     1      0K      0K  fg root     diag_lpass_data
  169  1   0% S     1      0K      0K  fg root     diag_wcnss_data
  170  1   0% S     1      0K      0K  fg root     diag_sensors_da
  171  1   0% S     1      0K      0K  fg root     diag_wq
  172  1   0% S     1      0K      0K  fg root     DIAG_USB_diag
  173  1   0% S     1      0K      0K  fg root     diag_cntl_wq
  174  1   0% S     1      0K      0K  fg root     diag_dci_wq
  175  1   0% S     1      0K      0K  fg root     kgsl-3d0
  176  1   0% S     1      0K      0K  fg root     kgsl-events
  177  1   0% S     1      0K      0K  fg root     governor_msm_ad
  178  1   0% S     1      0K      0K  fg root     kgsl_devfreq_wq
  199  3   0% S     1      0K      0K  fg root     spi5
  200  1   0% S     1      0K      0K  fg root     usbnet
  201  1   0% S     1      0K      0K  fg root     sharedmem_qmi_w
  202  1   0% S     1      0K      0K  fg root     qmi_hndl0000000
  204  1   0% S     1      0K      0K  fg root     irq/212-msm_dwc
  205  1   0% S     1      0K      0K  fg root     k_gserial
  206  1   0% S     1      0K      0K  fg root     uether
  208  1   0% S     1      0K      0K  fg root     dsx_rebuild_wor
  209  1   0% S     1      0K      0K  fg root     dsx_exp_workque
  210  1   0% S     1      0K      0K  fg root     s2wiwq
  211  1   0% S     1      0K      0K  fg root     dt2wiwq
  212  0   0% S     1      0K      0K  fg root     irq/502-fpc1020
  215  1   0% S     1      0K      0K  fg root     fwu_workqueue
  216  0   0% S     1      0K      0K  fg root     msm_cpp_workque
  218  2   0% S     1      0K      0K  fg root     irq/495-batt-mi
  219  0   0% S     1      0K      0K  fg root     irq/504-synapti
  220  1   0% S     1      0K      0K  fg root     therm_core:noti
  221  1   0% S     1      0K      0K  fg root     therm_core:noti
  222  1   0% S     1      0K      0K  fg root     therm_core:noti
  223  1   0% S     1      0K      0K  fg root     therm_core:noti
......

It clearly lists everything possible (the list scrolls for more than 3 pages).

ps is more fitting option. While ps and top share most of its source code and features - the obvious difference is that ps gives you one time snapshot (what OP wanted) and top is designed to provide the same stats continuously (until interrupted by user or specified number of times) optionally sorted by specified column and limited to specified number of processes

@Пионерка Thanks, I'm not a Linux guy by any means so professional tips are great.

How do I know which process belongs to which app? On some rare cases, there are multiple processes per app, and there are also processes that have a customized name. Also, seems "ps" doesn't show all processes anymore (shows about 2) even using root. How do I make it show all? Or how do I make "top" to show only current state and that's it?

Edit: Qdevicemonitor on your PC

You can get a logcat using adb command

adb logcat and to save it adb logcat > logcat.txt and the saved file would be in platform tools directory
To get logcat of different times adb logcat -v long > logcat.txt
Source : Guide on ADB at XDA

In Terminal Emulator:

logcat > /sdcard/logfile.txt

You have several apps on Play Store, Logcat Extreme is one such app ( requires root). More apps can be found here, thanks to Izzy
Related with useful info How can I view and examine the Android log?

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


text:
Unable to flash factory ROM on Pixel
I'm trying to restore the factory ROM on my Pixel. I've downloaded and unpacked a factory image for my phone, and when I run sudo ./flash-all.sh I get FAILED (remote: partition [bootb] doesn't exist). Here's the whole transcript. Can anyone suggest a workaround?
target reported max download size of 536870912 bytes
sending 'bootloaderb' (32728 KB)...
OKAY [  0.836s]
writing 'bootloaderb'...
(bootloader) Valid bootloader version.
OKAY [  1.600s]
finished. total time: 2.435s
rebooting into bootloader...
OKAY [  8.593s]
finished. total time: 8.693s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radiob' (57192 KB)...
OKAY [  1.428s]
writing 'radiob'...
OKAY [  0.909s]
finished. total time: 2.337s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.106s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
    Size: 122633060352
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 29939712
    Block groups: 914
    Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: XXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [  0.050s]
checking version-bootloader...
OKAY [  0.051s]
checking version-baseband...
OKAY [  0.050s]
sending 'bootb' (24821 KB)...
OKAY [  0.642s]
writing 'bootb'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [bootb] doesn't exist)
finished. total time: 1.095s

The only reference I can find to this issue is here, but it's not clear whether anyone solved it: http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497/page49

Try fastboot flash flash-all.sh instead? I successfully flashed stock Marshmallow onto my Nexus 6P but now I'm forgetting the specific command...

This was the phone.

You might want to mention what you have done to your phone so it requires reflashing. Also is your phone a generic Google version or is it a carrier branded version?

It was a generic google version. Unfortunately I don't know how I got it into that state. Some combination of rooting it, trying to unroot it, and trying to flash the factory ROM. My hope was that "partition [bootb] doesn't exist" would suggest some simple command to repartition the whole world, but I haven't found one yet.

I had this same issue. (Using Ubuntu Linux) At first, I was getting the "Fastboot too old" error. I was able to bypass this error by running the fastboot commands manually, rather than from the ./flash-all.sh script file.
Then I found that I was getting the error stated above when running sudo fastboot update image-marlin-opm4.171019.021.d1.zip. To resolve it, I had to uninstall fastboot, adb and android-sdk-platform tools from my system (assuming they were the old versions that the CLI was trying to use instead of the new version I had just downloaded in to my ~/platform-tools folder. (Under Ubuntu just using sudo apt-get remove adb fastboot android-sdk-platform-tools, other distros may require a different command, ie. pacman for Arch, Manjaro). After this was done, just in my home directory, to verify that fastboot had been uninstalled, typed sudo fastboot devices, which returned command not found error, this is good.
Then I navigated to my ~/platform-tools directory and ran sudo ./fastboot update image-marlin-opm4.171019.021.d1.zip which directly uses the fastboot application in that directory and it all worked fine then.
Output:
ewan@obiwan:~/platform-tools$ sudo ./fastboot update
image-marlin-opm4.171019.021.d1.zip extracting android-info.txt (0 MB)
to RAM...
--------------------------------------------        Bootloader Version...: 8996-012001-1711291800 Baseband Version.....:
8996-130091-1802061512 Serial Number........: HT69J0201460
--------------------------------------------        Checking product                                   OKAY [  0.050s] Checking version-bootloader
OKAY [  0.050s] Checking version-baseband
OKAY [  0.050s] extracting boot.img (29 MB) to disk... took 0.180s
archive does not contain 'boot.sig' archive does not contain
'boot_other.img' archive does not contain 'dtbo.img' archive does not
contain 'dt.img' archive does not contain 'odm.img' archive does not
contain 'product.img' archive does not contain 'recovery.img'
extracting system.img (1762 MB) to disk... took 16.977s archive does
not contain 'system.sig' extracting system_other.img (551 MB) to
disk... took 5.994s archive does not contain 'system.sig' archive does
not contain 'vbmeta.img' extracting vendor.img (251 MB) to disk...
took 2.891s archive does not contain 'vendor.sig' archive does not
contain 'vendor_other.img' Sending 'boot_b' (30173 KB)
OKAY [  0.851s] Writing 'boot_b'
OKAY [  0.301s] Sending sparse 'system_b' 1/4 (524284 KB)
OKAY [ 14.661s] Writing sparse 'system_b' 1/4
OKAY [  4.363s] Sending sparse 'system_b' 2/4 (524284 KB)
OKAY [ 13.404s] Writing sparse 'system_b' 2/4
OKAY [  3.584s] Sending sparse 'system_b' 3/4 (524284 KB)
OKAY [ 13.773s] Writing sparse 'system_b' 3/4
OKAY [  4.445s] Sending sparse 'system_b' 4/4 (231592 KB)
OKAY [  6.100s] Writing sparse 'system_b' 4/4
OKAY [  1.612s] Sending sparse 'system_a' 1/2 (524284 KB)
OKAY [ 13.654s] Writing sparse 'system_a' 1/2
OKAY [  3.652s] Sending sparse 'system_a' 2/2 (40680 KB)
OKAY [  1.133s] Writing sparse 'system_a' 2/2
OKAY [  0.400s] Sending 'vendor_b' (257548 KB)
OKAY [  6.709s] Writing 'vendor_b'
OKAY [  2.661s] Setting current slot to 'b'
OKAY [  0.089s] Rebooting
Finished. Total time: 118.310s

Use the lastest Android7.1.1 fastboot tool to flash images. I have successfully flashed the Pixel 7.1.1 (NMF26Q, Dec 2016) today.

So, got any Links, Documentation, Screenshots, Or Anything?

Yes I assume flashing the stock ROM just works for most people. But it didn't work for me, and my question is about how to fix it.


text:
Fastboot recognizes device but unable to flash (stuck with no output)
I'm trying to flash a custom ROM on my Android smartphone using fastboot. When trying to flash the recovery, the command does not output anything and is stuck.
./fastboot flash recovery recovery.img

Environment:

ROM: PixelExperience 11 (Plus) (Official for X00TD)
Recovery: Supplied with the ROM
Smartphone: Asus Zenfone Max Pro M1 (X00TD / ZB601KL Variant)
PC:

                 /////////////                user@pop-os
             /////////////////////            -------------
          ///////*767////////////////         OS: Pop!_OS 20.04 LTS x86_64
        //////7676767676*//////////////       Host: 80F6 Lenovo B40-80
       /////76767//7676767//////////////      Kernel: 5.15.8-76051508-generic
      /////767676///*76767///////////////     Uptime: 54 mins
     ///////767676///76767.///7676*///////    Packages: 1896 (dpkg), 27 (flatpak)
    /////////767676//76767///767676////////   Shell: bash 5.0.17
    //////////76767676767////76767/////////   Resolution: 1366x768
    ///////////76767676//////7676//////////   DE: GNOME
    ////////////,7676,///////767///////////   WM: Mutter
    /////////////*7676///////76////////////   WM Theme: Pop
    ///////////////7676////////////////////   Theme: Pop-dark [GTK2/3]
     ///////////////7676///767////////////    Icons: Pop [GTK2/3]
      //////////////////////'////////////     Terminal: gnome-terminal
       //////.7676767676767676767,//////      CPU: Intel i5-5200U (4) @ 2.700GHz
        /////767676767676767676767/////       GPU: Intel HD Graphics 5500
          ///////////////////////////         Memory: 2679MiB / 7865MiB
             /////////////////////
                 /////////////

(Also tried, unsuccessfully in the older Kubuntu 18.04, with the same result)
I've tried using both the system supplied (Ubuntu repository) version of fastboot and the one shipped with Android's platform tools.
Installed the system version with sudo apt install android-tools-adb android-tools-fastboot.
fastboot Versions:
user@pop-os:~$ fastboot --version
fastboot version 1:8.1.0+r23-5ubuntu2
Installed as /usr/lib/android-sdk/platform-tools/fastboot

user@pop-os:~/Android/platform-tools$ ./fastboot --version
fastboot version 31.0.3-7562133
Installed as /home/user/Android/platform-tools/fastboot

Prerequisites:
Have configured udev rules as shown below (to avoid "no permission" error when running fastboot without sudo)
#/etc/udev/rules.d/51-android.rules

SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666", GROUP="plugdev"

And added current user to the 'plugdev' group with sudo usermod -aG plugdev $LOGNAME
Issue:
After rebooting into fastboot mode through either the hardware keys (VOLUME UP + POWER) or the command ./adb reboot bootloader, my device is recognized by fastboot.
user@pop-os:~/Android/platform-tools$ ./fastboot devices
XXXXXXXX04HP    fastboot

But when I try to flash the recovery, the command gives no output and is stuck
user@pop-os:~/Android/platform-tools$ ./fastboot flash recovery recovery.img

And just when I unplug the device from the PC, it gives an error
user@pop-os:~/Android/platform-tools$ ./fastboot flash recovery recovery.img
Sending 'recovery' (21517 KB)                      FAILED (Write to device failed (No such device))
fastboot: error: Command failed

Conclusion:
As recommended in the hyperlinked guide and other resources, I have tried using different USB ports (both 2.0 & 3.0), different cables and, as mentioned, different PC and version of Ubuntu. Nothing resolved the issue.
However, using Windows 10 with the same PC (its dual-booted), USB port, cable and the mobile device, I was able to successfully flash the recovery and later the ROM also.
There are similar questions to this one with some whose accepted answers are not very helpful and most of them are old. I would really like some help with this issue.
Thanks in advance for your inputs.

as you already pointed out it's not an issue with the android phone but with linux, i suggest to migrate that question to https://unix.stackexchange.com

Posted it here. Thanks @alecxs

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


text:
Couldn't Connect Private DNS (Own DNS)
I have created my own DNS resolver for blocking some web pages and I can't figure out how to use it on Android. If I configure the DNS of any other device to use my DNS, it works like a charm (I've tested this both Windows and Ubuntu).
I tried configuring it in the Private DNS section of an Android, but it keeps saying "Couldn't Connect". If I use 1dot1dot1dot1.cloudflare-dns.com instead, it works.
So, my question is:
What are the requirements for a DNS Provider to be configurable in the Android's Private DNS section?

Does your DNS resolver support DNS over TLS/DoT?

Yes. When I started looking at the differences between my DNS and Cloudflare, I realized I didn't have support for DoH and DoT. So I applied the necessary changes to support both.

I don't have the rep to just use the comment so this is likely a far cry from a good answer.
The verbiage where you can specify does state hostname so (without rooting?) we have to let the system resolve the hostname. You could use one.one.one.one as well, for the sake of less typing.
I would suspect it's just a typo but you might also check if you entered -com or .com in your device. If you're using the address as entered in the OP, it should be 1dot1dot1dot1.cloudflare-dns.com.
I could be mistaken but, since Android 9, it seems like any private DNS app on the branded Play Store requires the use of VPN tunneling contrivance, on the device. It also looks like the only check it makes is that the TLD field does not begin with a number, as far as how it decides to validate it.

Thanks for noticing the -com. It was a typo, I've edited the question. I'll read your answer carefully tomorrow.

No problem. I'm of the inclination that there is not a non-hostname answer, on Android 9+ Play branded devices, for the behavior you want so I would think you could leave it marked as unanswered. I believe this was changed to enforce DNS over TLS.


text:
Can I get a virus from a browser that doesn't have storage permission?
I am using Android 8.1.0 on an LML212VL LG Tracfone (more info at bottom). I downloaded the "DuckDuckGo Privacy Browser" app through the Google "Play Store" app. (This is the link I get when I click "Share" and "Copy to clipboard": https://play.google.com/store/apps/details?id=com.duckduckgo.mobile.android .) Later I went into the "Settings" app, and under "Apps & notifications", "App permissions", "Storage", I can see that DuckDuckGo's storage permission is disabled. (I don't remember if it was that way by default or if I did that, but I've kept it that way for most of the time I've had the app.) Also, within the "Settings" of the DuckDuckGo app, accessed via the menu at the top right, I have "Automatically Clear..." set to "Tabs and Data" and "Clear on" set to "App exit only".
Basically, I hoped to have a browswer set up so that it is not able to download anything that it doesn't delete on app exit, without asking for my permission in a specific way that I recognize. (Normally when I try to make an app do something I've denied it the permission to do, a certain type of pop-up appears, and I've made sure never to check the "Don't ask this again" box. When I try to download something in this DuckDuckGo app, the pop-up says "Allow DuckDuckGo to access photos, media, and files on your device?", and when I tap "DENY", a banner appears at the bottom of the screen saying "Downloading requires storage permission".) One problem, though, is that it clearly does keep a cache of some kind, since I can see it in the "Settings" app, under "Apps & notifications", "App info", "DuckDuckGo", "Storage". I sometimes delete the "cache". I think website language preferences and maybe autocomplete suggestions are kept in this "cache". I can also delete the "data" that the app keeps, but that undoes the settings I set within the app, tries to make me go through the introductory tutorial when I open it, and randomly tell me about how many things trying to track me it blocked ad it does the first time or so you use the app, so I don't do this as often.
My question is this: Does this mean that I can't possibly get a virus from a website through this app, even if I click on something suspicious, as long as I don't enable these permissions? Alternatively, does it mean that any virus I do get would be trapped 'within' the app in some sense and disappear when I close the app, when I clear the cache and data in "Settings", or at least when I delete and reinstall the app?
What made me worry about this is an event that happened some months ago while I was using this browser. I clicked on a link to some website or something, but it had apparently been replaced, and a pop-up appeared telling me that malware had been detected on my computer and that I needed to download something to scan for it and get rid of it or something. I didn't trust this at all, but for some reason I clicked "ok" to close the pop-up (I think I thought I needed to do that to close the tab without closing the app). As soon as I did this, the pop-up disappeared, and a loading bar appeared on the screen behind it with some text saying what it was supposedly doing (I think downloading something). I freaked out and immediately closed the whole app (which, remember, should clear tabs and data) and/or took the battery out of my phone.
I think I looked some stuff up on the internet using another device, but it didn't give me much peace, except telling me that what had just happened to me was a well-known scam to make people download malware and maybe suggesting that I use some supposedly more trustworthy malware-scanning app (I don't remember if I did, but, if so, I don't think it told me anything). When I turned my phone back on, I think I disabled "Wi-Fi" (and "Mobile data", but that was probably already disabled) in the "Settings" app, under "Network & internet"; then, I went into "Apps & notifications", "App info", "DuckDuckGo", and then probably clicked "Force Stop" and then "Uninstall", agreed that I really wanted to uninstall it, probably saw that it disappeared from both the "App info" list and my "App locker" (or whatever the place where clickable icons for every app are and that is down from the home screen is called), then (after re-enabling internet) reinstalled it through the Google "Play Store" app.
I don't have any particular reason to THINK I have malware on my phone (at least not anything that isn't usually on an Android phone), but there's not any way I understand that I can really be sure, except that I could be fairly sure if I factory reset my phone, and I don't want to do that. Thus, I'm wondering if I can at least be sure on logical grounds that I don't have any malware from that particular encounter or from any other site I went to with that browser.
As promised in the first paragraph here is the "more info at bottom" about my phone:
In the "Settings" app under "System", "About phone", "Hardware info":

"Model number": "LML212VL"
("Up time", "S/N", "Wi-fi MAC address", and "Bluetooth address" are also given, but I don't think they would be helpful.)

Under ... "About phone", "Software info":

"Android version": "8.1.0"

"Android security patch level": "June 1, 2020"

"Baseband version": "MPSS.JO.3.0.c12-00036-8937_GENNS_PACK-1.229846.1.264977.1"

"Kernel version": "3.18.71"

"Build number": "OPM1.171019.019"

"Software version": "L212VL16g"

I can't guarantee that's what they were when the scare a few months ago I mentioned was, but it is what it is now, as of February 15, 2022.

If an app has storage permissions or not is totally irrelevant if it can be exploited or not (unless you download a malicious file your self). Attacks on web browsers usually use an exploit chain, a combination of multiple exploits:

The first exploit allows you to execute code with permissions of the web browser on Android.
Next one exploits a vulnerability of your OS to get full permissions (privilege escalation: leave the restricted app sandbox).
If necessary the last exploit then can give you root permissions, giving the attacker full access to everything (if step 2 has not already leveraged permissions to root).

For step 1 it is important to use a web browsers that is properly maintained, and updated regularly. But zer0-day exploits are discovered quite a few, e.g. for Chromium based browsers you have usually one zero-day vulnerability per month, often more.
Step 2 and 3 require an updated Android OS. As your phone is missing nearly two years of security updates there might be vulnerabilities for exiting the sand box and/or getting root.
In a general sense if there is a flaw in the browser runtime such as the javascript engine, or rendering engine and adversary could conceivably cause your browser to execute an arbitrary procedure as long as the OS allows it.


text:
Rooted Moto Z2 Play: Unable to power on after unhiding Magisk Manager app, upgrading Magisk version and reboot. Is there any way to fix this?
I have a Moto Z2 Play device (android 7.1.1) that was rooted with Magisk (v20.1) with Magisk Manager app (v7.4.0). Magisk Manager Hiding feature was also activated.
When I deactivated the Magisk Manager Hiding:

Magisk Manager v7.4.0 got auto updated to v22.1 and Magisk was shown as not installed
Selected direct install option in the app to install Magisk (v22.1)
Rebooted the Moto Z2 Play device

And the device failed to power up... Is there any way to fix this?
I have tried Fastboot boot to TWRP and flashing Magisk-v20.1.zip but to no avail, device still doesn't start up normally when I press the power button. Currently I can still boot into fastboot/recovery mode.

flash stock boot.img to repair what magisk broke

Thanks @alecxs, would there be any difference between flashing stock boot.img and flashing stock rom?

does not harm but not necessary as magisk does not modify system

UPDATE: @alecxs answer worked for me, still trying to figure out how to accept it as the answer.
Apart from flashing stock boot.img, I also flashed magisk v20.1 uninstaller and reflashed magisk v20.1 installer to fix the booting issue.

Flashed stock boot.img using fastboot flash boot boot.img -> device now powers up, but goes into boot loop
Flashed magisk v20.1 uninstaller via TWRP -> device still goes into boot loop
Flashed magisk v20.1 installer via TWRP -> device starts up normally with all my data still intact and magisk + magisk manager both back to original version (magisk v20.1, magisk manager v7.4.0)

Hi, it seems you accidentally created a duplicate account. Please refer to the help center to merge your accounts and regain ownership of the question and reply to the comments on your post, including accepting an answer (comments cannot be accepted though).


text:
Will Installing A Google factory Image Give Me The Ability To Receive OTAs Again
If I restore my Nexus 5x using a Google official factory image, will I receive OTA updates if I don't root afterwards?
Sorry for the previously confusing question.

Yes... It returns it to out of box factory condition. You can accept OTA updates like normal.

@acejavelin You should write that as an answer so that Luke can accept it.

Yes, please!  :)

Yes... It returns it to out of box factory condition. You can accept OTA updates like normal.
Be sure to follow the complete flashing instructions using the latest factory images from Google, available here. Once this has been completed your phone is essentially "new" and completely stock, and you can accept any OTA or other official updates as you wish.


text:
Infinite boot animation screen Nexus 5
**
SO I AM RENDERING THIS NEXUS 5 DEAD (BRICKED FOREVER)

My daughter was using this Nexus 5 device and the power button started causing her problems.
Well I removed the power button and ordered a new one. So now the power button is not an issue.
But I guess during the time that the phone constantly kept rebooting due to the bad power button, something got corrupt.
Now the device gets to the boot animation and never goes any further.
There are no options in recovery for me to use.
I have working ADB and Fastboot on my PC. I can see the device with Fastboot but not ADB because I can't get the device to boot into the OS for me to enable USB debug.
But I know ADB works because I used it just the other day on a Galaxy S5.
I have tried to run fastboot oem unlock, it unlocks the device then once you reboot the boot loader, it says locked again.
I have tried using Nexus Root Toolkit and hit unlock and it unlocks then says the phone will reset itself and just be patient. It may appear to bootloop but just wait.
I waited for an hour and still just sits at the boot animation.
What are my options without being able to enable USB debug since the device will not boot to the OS?
I am able to Temporarily boot to a custom recovery, but I can't mount data!!!
With Temporary TWRP, I am able to use ADB and I get a success message when I push a new system image to it, and when I push twrp recovery to it, but when the phone reboots, I find out that neither the system image or recovery were actually installed.
I looked into bad partitions, tried some fixes, and nothing works. I am so far beyond frustrated with this thing. I guess I will wait one more day to see if anyone else has any other ideas for me to try, then I am just going to put it in the trash.

Bootloop
Bootloader doesn't stay unlocked
Unable to mount storage
USB Debugging is not enabled and can't be enabled
Can't install OS image
Can't install Recovery
Can run TWRP temporary
Can use ADB when TWRP Temporary is running, still can't mount anything

Welcome! FYI, Its a boot-loop. Same thing though.

Hmmmmm, sounds like a soft-brick. Can Nexus root toolkit flash the Stock ROM? If so, do that; you will lose all personal data

No it won't work. I tried that several times and still gets stuck in boot-loop. When I try to format and erase in Temporary TWRP, it says unable to mount storage.

Did you use the mount option in TWRP to mount it manually? Does help ;)

Yeah, it won't let me mount /data. I tap on it and it thinks about it, but never mounts it. it lets me mount /system and /cache.

Your partitions may be Screwed then. Ack, I don't know how to fix that. Hold on...... I can't find anything. You may have to contact customer services, or maybe you' have to wait and see if anyone else here knows what to do.

Ok, thank you for your help so far. I will look more into partitions.

Cannot modify partitions. I am assuming this is because USB debugging was never enabled on the device. And since I can't get to the OS, I cannot enable USB debugging.

Ack. Oh well, sorry we can't help!

http://android.stackexchange.com/questions/110991/nexus-5-reboot-loop hope this thread helps

That didn't help either. I think this is done for. Maybe the memory is dead.


text:
How to add time to "wait" command in tasker
I am pretty new to tasker app and I am trying to create a profile to turn off music after 30 minutes. So I did this:
Profile: App (Music)

Task: MusicAutoOff

T1: Notify

* Title: Music Auto Off

* Actions A1: Wait 5 minutes, A2: Wait 30 minutes

T2: Wait 30 minutes

T3: Media Control

* Cmd: Pause

* Simulate Media Button: On

* App: Music

T4: Notify

* Music Turned Off

And all I want to do is wait additional 5mins/30mins before executing next commands when I press those action buttons on notification. How can I do this?
Any help would be appreciated.
Thanks in advance.
UPDATE:
Tasker XML Project File Added for reference: MusicAutoOff.xml
SCREENSHOTS:

Can you export Your task (as a file) upload it somewhere, and give us the link? It makes it much easier to help you.

@DanBrown I just uploaded the tasker file for reference

Tricky, I cannot import your script 'Failed to import profile data.' Are you using a custom scene (if so, send it!)

I didn't use any custom scene for that profile or task. Anyways i'll add some screenshots of the task and profile to the question.

I created a separate project for that task and exported to an xml file and update the old file with the new one.

Huh, alright. You want that wait to last longer, right? Have your tried Tapping it?

Yes, but that didn't work

Does the "Music Turned Off" toast ever show up on your phone?


text:
How do I make Android consider my WiFi Access Point as valid (blue?)
We have a very large wifi network at Stack Exchange, and the primary guest network is tightly locked down.  Our firewall rules permit essentially just http/https and vpn connections.    When our Android phones connect to the wifi, they show good coverage but the WiFi icon never turns from grey to blue.
What is the Android phone checking to make the grey/blue wifi icon decision in JB 4.2.2?

This is the "what is it checking" part (albeit, not entirely specific): What does it mean when the connectivity icons in the status bar go white/gray?

After probing the firewall logs, it appears that the grey/blue icon is triggered depending on whether or not your device has access to Google Play.  In our case, I had to open tcp-udp port 5228 (as per http://support.google.com/googleplay/bin/answer.py?hl=en&answer=2651367) and after turning wifi off and back on again, the icon became blue.
I can't confirm whether http/https is also part of the equation; we already had that open so it's possible if one is running into this issue even after opening tcp-udp 5228, that http/https may also be required.


text:
Can I remove User Dictionary Application itself ? not just words in it?
My process monitor shows the User Dictionary Application is taking up all the CPU the device has got so even phonecaller app crashes.
I'd like to remove the whole User Dictionary Application if possible.
I don't want to use this feature anyway.
Would I be able to remove it ?
If I could, would removing User Dictionary cause any serious issues ?

On my Galaxy S3, running 4.1.2, the User dictionary is a background service that can be disabled. If you are running a similar device look into the following:
Settings\App Manager\All\User Dictionary
Click the disable button.
If you are using a different device or system this could get you started in the right direction.

Thanks ! that did the trick. As soon as I find out this application is not necessary for my device to operate, I'll completely get rid of it.


text:
How to forbid a dual-SIM system from using mobile data on one SIM?
I set the SIM card for mobile data like this:

And it works most of the time. This SIM is Austrian and I spend most of my time in Austria.
However, when I venture into Slovakia — the country of the other SIM card — strange things begin to occur.
Once I place a normal GSM call, or send a GSM SMS using the Slovakian SIM card in Slovakia I get a notification from the provider that I transferred 50kb of data and that they automatically assigned me 500Mb until the end of day. That is their policy.
I spoke to the provider and the lady told me that this is simply not possible and the problem is in my phone.
Could this be a bug in the Android OS?
I am using a Samsung Galaxy A20e with Android 11.
Since I chose SIM2 for the mobile data, I don't even have an option to explicitly de-activate the data:

The evil SIM seems to have provided data for all sorts of apps:

EDIT
Mystery most likely solved — there seems to be a setting that overrides the ones in SIM card manager:

Check if you have activate VoLTE. Typically such "data usage glitches" are cause because the mobile network provider does not correctly identify a mobile data connection as connection only used for VoLTE. Starting with 4G there is no longer a voice network. I am not sure if the wrong classification is a bug of the MSO, the phone or both.

@Robert  Thank you! So far it seems you are right.


text:
SD Card doesn't show up after attempting to format as internal storage from stock crDroid Android 10 Files app
After attempting to format my SD card as internal storage for Samsung Galaxy Tab S 10.5 LTE (SM-T805) using the preinstalled Files app on crDroid (Android 10), it is no longer recognized by my device. I believe it is now completely corrupt, as even Windows is unable to read it after attempting to use an SD card adapter. It's not even listed in the disk management program.
Please help as I was dependent on my SD card as I only have 16GB on this device.
Edit: after formatting it in twrp it shows up in my device however im still not able to format as internal as some java error comes like i said before...

https://imgur.com/a/LQ82msb
first pic is when the storage is formatted as internal and the second is after doing as external

please try these adb shell sm commands (from question) and check which one throws the java error (line by line):

Does this answer your question? SD card not appearing when formatted as internal

All fine. That is per design. Once formatted MicroSD Card as adoptable-storage, it becomes part of your Internal Storage and will disappear. Because it is an encrypted file system, no PC card reader can detect it.

Well thats the problem it dint become adaptable storage my storage still shows 16gb but the sd card disappeared...coming to think about it a java error was thrown at me after attempting to format but it was one of those disappearing notifs at bottom of screen....


text:
OTG USB devices not detected anymore on Xiaomi Redmi Note 7 but can charge the phone and share files with computer
I noticed that either USB key or the Razer Kishi gamepad where undetected by my device although it did work some time ago. It may be related to an update or a material problem, I don't know. I tried the devices on both my computer and other android devices and they are perfectly detected.
I have no setting to toggle on Settings > Additional Settings, while I saw on the internet that OTG devices have a setting to toggle on for OTG.
See attached picture for the specs of my phone.
Is there any way to confirm whether it's a software issue or a physical issue ?
And would anyone know which steps to take in either case ?

EDIT: Extra information provided:

If your phone works on a charger and a PC then a general physical problem of the phone is unlikely.
The most probable problem source is an software update.
USB-C hardware issue
But there is one exception: I assume the phone has an USB-C connector which is by definition reversible. This is implemented by providing all connectors twice.
So if one of the connectors is damaged than it may still work but only in one direction. Additionally there are devices (and USB-C cables) known that have by design problems with this reversibility, they fail to detect USB devices in both directions or have other problems in one direction.
Therefore please when connection USB devices to the phone always check both directions of the USB-C plug just to make sure.
Software issue
There are several apps to be found in Play Store that check the OS for OTG support. Not sure if there is an app that works for your phone and Android version, but I would give it a try.

I added the results of testing the OS for OTG support to the question. I tried it by myself but did not thought it helped.
Hardware issue: What you mean is that I may have a device that works when it is connected to a PC ? (phone is the peripheral) but not when I connect the phone to some usb key ? (usb key is the peripheral). I don't understand what you mean by check both directions of the USB-C plug, what is an exemple of procedure you'd like me to do?

@RobinVogel All USB plugs have two directions how you can insert such a plug in a socket. Before USB-C only one direction worked, the other was mechanically blocked. Since USB-C both directions are possible, there is no "wrong direction" anymore on physical level. However some devices still have one "wrong direction" on technical level (because of a damage or a bug in the hardware design).


text:
How to emulate a mouse?
I am running Android 4.3 "jelly bean" in a VirtualBox VM. Google has released an ISO of an x86 port on code.google.com. It's a fairly straightforward installation, and easy to setup. You can find a tutorial here if you need help. But let's get back on subject.
Anyways, I have successfully installed it. It does not seem to have mouse integration, which I desperately need. My laptop which I am running it on does not have a touchscreen. It is a 64-bit Dell something-or-other laptop I received from a friend, and it is running Ubuntu 16.10. Is there any available APKs or workarounds for the mouse? I can use the mouse, but no pointer displays. For example, I can click and drag the top menu bar that displays notifications, battery, etc. and open that, or click buttons (if I'm careful), or use it as if it were my finger. I simply need it to display the mouse pointer. The only workaround I can think of is unlock the developer tools and use the mouse tracking option that draws a line when you tap. However, that only works if I click and drag.
The question: Are there any APK's or workarounds for displaying a mouse pointer or emulating a mouse, and if there is/are, how can I use/activate/install/get them?
edit: This isn't something I can't live without. I'm just experimenting, maybe going to do a little android gaming just for fun. I can do most of the UI navigation with the keyboard, but a mouse would make things much easier. Also, I am looking for a no-price, costless workaround. That said, I'd rather not do anything like buy a controller.
~ P

4.3 does support displaying a mouse pointer, and it Should Just Work when you start using the mouse.

@DanHulme I have the mouse connected at all times. Still no luck.

It seems that I have found a temporary answer. In the "Input" taskbar menu of Vitualbox, there is a mouse integration option. Left unchecked, Android draws the mouse pointer. However, if Mouse Integration is on, it relies on the host OS, which does not work. This option is less convenient, but it works for now. If anyone has any recommendations to permanently fix this, please post an answer.
~ P


text:
Two copies of an app taking space
My old HTC M8 is running very low on space, and I noticed it has 2 copies of several apk installed in /data/app for example com.twitter.android-2 and com.twitter.android-3. All in, this appears to be taking 1Gb.
This phone is rooted, so I can fix it, but is this a bug or just an artifact of the phone being old and having had several OTA updates in its time?
Would I be able to test/fix this without being rooted (except for factory reset).
OS version is 6.0
com.twitter.android-1:
-rw-r--r--    1 system   system    33495510 Nov 14 20:41 base.apk
drwxr-xr-x    3 system   system        4096 Nov 14 20:41 lib
drwxrwx--x    3 system   install       4096 Nov 14 20:41 oat

com.twitter.android-2:
-rw-r--r--    1 system   system    38637594 Aug 13 08:31 base.apk
drwxr-xr-x    3 system   system        4096 Aug 13 08:31 lib
drwxrwx--x    3 system   install       4096 Aug 13 08:32 oat

The expected behavior, from Lollipop onwards, is for Android to incrementally rename the directory in which an APK is placed, each time an update occurs. Is your device rooted? If yes, could you show us the permissions, ownership and attributes of com.twitter.android-2 and com.twitter.android-3?

updated. Maybe relevant that the phone rarely sees wifi for any length of time, I keep it in the car (so it may often get partial updates).

@DeathMaskSalesman is it normal that the second directory is kept after the update completed? To my understanding, as soon as that step is finished the "older directory" is removed. In my case, if it was not, the result was a bootloop (remember?).

@Izzy It is not normal indeed. As I said, the directory is normally renamed once the update is completed.

To my experience, the older one is removed. If I list contents of /data/app, some directories end on -1, others on -2 – but there's always only one directory per app. But be that as it might: 2 directories per app is not normal, on that we seem to agree – so something must be going wrong there.


text:
Command error by running "fastboot oem unlock"
I am unable to use the following command on an HTC One M7
# fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [  0.001s]
finished. total time: 0.001s

Why do I get this error and how to unlock my bootloader?
In addition
# fastboot flashing unlock
...
FAILED (remote: not allowed)
finished. total time: 0.000s

What device (and Android version) do you have? Without further information we can't know for sure why you're getting that message. It's possible that you need to use fastboot flashing unlock instead as this is the new version of the command.

You don't unlock an HTC phone like this - in fact most phones can't.
Provided yours is unlockable (i.e. not an AT&T/Verizon variant), you need to sign up and apply for unlock here and use the token you acquired to complete the unlock process. The site itself will walk you through thoroughly.


text:
Disable Cyanogen 10.1 notification drawer widgets
I want to remove the notification drawer widgets, but despite having System > Notification Drawer > Power Widget unchecked, it keeps showing up.
When I have new notifications, pulling down the drawer reveals them; but if I do it a second time, without any unseen items, I'm treated to a screenful of widgets I don't really need and have to manually switch back to the notifications list.
How can I disable this, and have a plain old notifications dropdown?

It sounds like you're describing the "Quick Settings panel", which is different (and actually a feature of vanilla Android Jelly Bean). Try System > Quick Settings panel > Quick pulldown > Off. Or possibly provide a screenshot if you can, to make sure we're talking about the same set of notification bar toggles, since CM 10.1 has two.

Indeeeeeeed! Given 10 years I would've never realized it was showing up when I pulled the status bar FROM THE RIGHT EDGE. Move the comment to an answer, and accepted it will get

@uʍopǝpısdn you can get it if you do a 2-finger pull-down too, how many years would it take anyone to notice that without being told about it!

@GAThrawn more years than the feature is going to last

So to sum up the bit of confusion that is in CM 10.1 now - there are actually two sets of notification bar toggles. One works like the old set from previous CM versions, and it appears in one row above your notifications when you pull down the bar. These are the "Power Widget" toggles.
The second set was a feature added upstream in Jelly Bean, and is referred to as the "Quick Settings panel". These are laid out as multi-row tiles - which it sounds like you are describing - and you can switch to this view by tapping the top right icon on your notifications shade (after pulling it down):

You cannot, to my knowledge, get rid of the Quick Settings panel completely, as it is baked in to Android. However, you can prevent it from appearing of its own accord by going into
Settings > System > Quick Settings panel > Quick pulldown

and selecting the "Off" option. The other options are "Right" and "Left", with the idea being that you can basically divide the notification pulldown into two swipe areas if you like. For instance, by choosing "Right", you can access your notifications by pulling down from the left side of the bar, and access the Quick Settings panel by pulling down from the right side of the bar. If you choose "Off" then the only way to get to the Quick Settings panel should be if you pull down your notifications and then tap the icon in the top right. Effectively, this disables the Quick Settings panel from ever appearing unless you explicitly choose to see it.


text:
Is there any android support for bicycle sensors?
I've seen some Bluetooth Smart (4.0) technology for tracking tire rotation rate (bike speed), peddle rotation rate (cadence) and even heart rate monitors.
Some heart rate monitors are supported by google mytracks now.
Anybody aware of support for cycling sensors?

Not aware, but a quick check in the playstore shows there are several bicycle apps supporting "ANT+ sensors" for speed and other things. Take e.g. a look at IpBike ANT+™ Bike Computer, ANT+ Bike Display Demo, IpBikeKey, and others. Starting point: ANT+ Playstore search :)
Please note that, as Ifor pointed out in his comment, that this requires special support from the Android device's hardware. Details can be found e.g. at the IpBike page.

nice , hadn't heard of ant + before!

Neither did I :)

You will need a phone with built in ANT support or a USB ANT stick and OTG cable.  I have some details on the web page for my app IpBike web page at http://www.iforpowell.com/cms/index.php?page=ipbike

Thank you for this useful details, @Ifor! As you can see above, the entire ANT+ thing is new to both of us, so I suppose we both were not aware of the need for special support from the Android device's hardware -- good thing to know! I hope you don't mind if I include that details with my answer.

Unfortunately USB host mode on my galaxy i9000 would take considerable hacking, but good to know for future in any case. people seem very happy with the USB ANT stick on galaxy s3s.


text:
Chats are no longer RCS after restore
I have Android 14 with root. I restored my text messages from a backup made with Swift Backup. Now no conversations are using RCS, even the ones that did before the restore. For example it's now showing the received and red check marks. RCS is already turned on in settings. I tried toggling it but it didn't help. I'm using the stock SMS app. How can I fix this?

Restoring RCS messages is hacky as there aren't real APls in Android to deal with them from Swift Backup Telegram ss stated but developer

Actually, this may be Google's doing:

Google is cracking down on rooted Android devices, blocking multiple people from using the RCS message feature in Google Messages. Users with rooted phones — a process that unlocks privileged access to the Android operating system, like jailbreaking iPhones — have made several reports on the Google Messages support page, Reddit, and XDA’s web forum over the last few months, finding they’re suddenly unable to send or receive RCS messages.
One example from Reddit user u/joefuf shows that RCS messages would simply vanish after hitting the send button. Several reports also mention that Google Messages gave no indication that RCS chat was no longer working, and was still showing as connected and working in Google Messages.

Looks like the question is about restoring text messages as RCS, not about being unable to use RCS after rooting.

That's exactly what I thought at first but then the description explains that conversations are not RCS. Maybe the OP didn't test sending and receiving new messages.
I also wonder if anything can restore the messages to a new phone as RCS rather than them converting to SMS/MMS.


text:
How to view/edit a long URL?
I have a long URL displayed in the URL box of Chrome on Android 11. I would like to view and edit it. When I use a pencil tool, only the last part of the URL is visible and accessible for editing. How to scroll left to the beginning of it? I tried two fingers with no effect.

It mostly depends on the keyboard you use.

If you use Gboard, there is no HOME key. But, you can use its Text Editing feature. The top arrow key mimics the HOME key. See recording below.

If your keyboard has a HOME key like PC's keyboards do, then pressing the key will send you to the beginning of the URL.

I was using the UP key, as suggested in the answer, that used to work until a few days ago. Now it doesn't, and I have to drag the pencil icon for long seconds. Does anyone else has the same observation and found a way to restore the normal/efficient behavior?

@jbd It still works on my side. Gboard version 13.7.12.582282722-release-arm64-v8a. What version do you use?


text:
Write protection of loop device // Read-Only Filesystem
After spending days on that topic I am in need of additional ideas ;)
Facts: MTK6757 / Android 7 / Kernel 4.4.15 / FS EXT4 (No F2FS) / Working Root
I have a fresh and clean 64MB EXT4 .IMG File in /data/adb. e2fsck agrees with that ;)
Problem: Mounting and/or writing to it via Loop Device fails.
What I have checked:

Access rights of the file
Access rights of the block device
Access rights of the destination dir
Manually created the block device
Manually setup via losetup
Played with all options
SElinux Permissive / Enforcing

Behaviour:

It only gets mounted with "mount" because it calls a ioctl BLKROSET (thx  strace)

Mount and /proc/mounts show RW

As soon as I write (mkdir) to it, it switches to RO
(dmesg says Switching to RO cause of Buffer I/O error on dev loop0, logical block 0, lost sync page write)

When I enforce writing it gets written to cache but not to the file
ioctl /dev/block/loop0 0x125d 1 mkdir /sbin/.core/img/test

And now the strange part:
When the img file is on /sdcard it works.
The SE Context is of course different, but i also tried in Permissive.
When the mounting occurs BEFORE Zygote starts or in Recovery, writing fails also on /sdcard (Update: Because during boot /sdcard is not available yet)
Anybody any ideas?
Update:
It gets even more interesting:
Turns out writing to /sdcard only works as long as it is mounted as sdcardfs.
If sdcardfs is deactivated it gets mounted as FUSE properly, but writing doesnt work anymore.
As all the facts hint toward a selinux \ vold \ FS problem, i tried to restage the sdcardfs evironment.
Assign root \ sdcard_rwandu:object_r:sdcardfs:s0` to the file in a different directory.
Doesnt work ;(
Then I compared the selinux policies of 2 devices where it works with the problematic one.
Turns out allow vold block_device : blk_file { ioctl read write create getattr setattr lock append unlink rename open } is completely missing.
But injecting that doesn't help too...
Any experts or suggestions?


text:
How can I see the fingerprint of my adbkey?
You should know that Android 4.2.2 (or just before) introduced RSA key checking for adb access. – The device asks now if you want to allow access.
To avoid asking every time, the computer presents an RSA key, which can be permanently accepted.
The dialog on the phone shows the RSA key fingerprint. – On Linux, the public/secret key pair is here: ~/.android/adbkey(.pub).
How can I show the fingerprint of that key file? (I’m looking for a command line to do that on the Linux system.)

This is also needed when trying to verify the RSA key fingerprint presented when enabling USB debugging.

adb is usb debugging @JonathanCross

Now the keywords "usb debugging" are inside this answer  :-)

This line will do it (found here):
awk '{print $1}' < ~/.android/adbkey.pub | openssl base64 -A -d -a | openssl md5 -c

awk '{print $1}' < ~/.android/adbkey.pub | base64 --decode | md5sum works as well

how do I run this in windows

since a commit on Nov 15 2018 (https://android.googlesource.com/platform/system/core/+/2dc4cabe0639c71014d729dd92eff19289429c89), adb keygen no longer generates the public key. You can use adb pubkey ~/.android/adbkey | awk '{print $1}' \ | openssl base64 -A -a -d | openssl md5 -c | tr a-z A-Z  to get the MD5 fingerprint. Source: https://joachimschuster.de/posts/debug-on-device-rsa-fingerprint

Run:
echo {public key} | base64 --decode | md5sum

On Android 5 and above, the hash function used was changed to sha256. If your hardware is such, your could try:
awk '{print $1}' < ~/.android/adbkey.pub | openssl base64 -A -d -a | openssl sha256 -c | awk '{print $2}'|tr '[:lower:]' '[:upper:]'

On Android 10 I am still getting MD5.


text:
Mobile data can't connect (with exclamation mark) but wifi
My phone is Motorola XT1033 dual-SIM (Lollipop 5.1)

have active mobile-data internet packages
can connect and open provider's website (to check package status & quota)
valid APN settings (at least following provider's instructions)

There is a problem on mobile-data connection, see the differences here:
Data ON, Wi-fi OFF

there is an exclamation mark on the mobile-data signal bar
NOT connected to internet (even the signal is H)

Data ON, Wi-fi ON

there is NO exclamation mark on the mobile-data signal bar
connected to internet

What I've tried so far

rebooting my phone
turn mobile-data off and back on
re-attach the SIM card
install my SIM card to another handset (can't connect to internet)
install another SIM card to mine (can connect to internet)

Does anyone have the same problem? I'm looking forward for the solution.

Have you tried switching to GSM only mode ? maybe the WCDMA network falling short in your locality.

@reachrk i just try it but it still not works


text:
Android won't factory reset
I've been having trouble with my phone lately so I decided to back up my data and factory reset, but every time I want to do it the "reset phone" button does not work, I can't even press it. I have also tried to hard reset but when I get to the screen where I choose factory reset (the screen where there is a android guy saying "no commands"), there are no commands to choose so that is also a negative for resetting.

Sounds like you'll have to resort to fastboot and stock firmware.

how do i do that

A quick Google search: XDA Moto G Flashing Guide

Maybe you check our factory-reset tag-wiki, which also mentions an alternative way to do a factory reset, not requiring fastboot. Also see: How to do Factory Reset

Oh, wait: "The Android guy saying "no commands"? That sounds as if you've already been to your devices custom recovery and have wiped /system and/or /recovery, so it no longer has any OS installed. In this case you've really messed up, and flashing a new firmware via fastboot is the only way out.

don't worry. Do just what I say:

Turn off you Motorola Moto G 2nd Gen(I mean moto G2).
Afterwards press and hold the Volume Up and Volume Down for about 2-3 seconds.
While still holding these keys press the Power button for a short while and release all buttons.

Then select option Recovery by using to navigate Volume Down, and to confirm Volume Up.
In the next step hold down the Volume Up for a few seconds when an Android logo appears on the screen.
While holding the Power button, press and release the Volume Up key.
Press Volume Down to choose "wipe data/factory reset", and then push the Power button to confirm.
Select "Yes--delete all user data". Use Volume Down button to scroll and Power button to select.
To restart the phone, select "reboot system now".

Success! The hard reset is done!

Source : All credits go to hardreset.info

This will not help the OP, his OS is corrupted according to the conversation above. Consider providing fastboot flashing instructions rather than reset instructions which he has already tried.

Just had the same problem with a Moto G2: I wasn't able to click the button to reset. So I tried your instruction and it worked perfectly. Thanks.

@Aaron Gillion - how do we give flashing instructions ? I face the same issue with android one and also if it swtches on its stuck on the welcome screen.

but when i get to the screen where i choose factory reset (the screen where there is a android guy saying ''no commands''), there are no commands to choose so that is also a negative for reseting, thanks in advance...

This 'no commands' screen is actually part of the process. When you get this screen, continue with step 6. as explained earlier.

While holding down the Power key, press and release the Volume Up key, then release Power'

I also got the 'no commands' screen but after checking this motorola support page I found roughly the same steps as described earlier and it worked!
Good luck!!

Try installing TWRP, or just unlocking the device. when you unlock the device the device will factory reset and if you want you could install TWRP. to unlock your device, open "Developer Options/Settings" in the settings app and click "Allow OEM Unlock[ing]".
Then enter fastboot and on your computer write:
fastboot oem unlock [Unlock Key From Motorola's Website]


text:
Can't remount /system in rw
I'm trying desperately to push an app with adb  on the /system/app folder (to install the PlayStore on my low cost tablet).
So I tried to remount the /system partition with root rights:
mount -o remount,rw /system

But it gives me the same response every time:
mount: Read-only filesystem

And I also tried with command:
mount -o remount,rw -t ext4 /dev/block/actc /system

but it's the same thing...
And I really don't understand why, even with the root user, I can't modify this...
So if someone has an idea, it could save one person in distress :p

I have the same problem with Android 4.4.2, Nexus 4. When I make this command kernel adds the folowing message in dmesg: EXT4-fs (mmcblk0p21): re-mounted. Opts: (null). Why (null)? I explicitly requested rw!

did you ever figure this out? I'm having the same problem. Using a samsung galaxy tab.

@JacobMinshall and @Dmitry, if you're still interested, try running `/system/bin/mount explicitly, rather than implicitly running the xbin one. That worked for me.

The syntax of mount command usually requires you specify the target:
mount -o remount,rw /system /system

This output could be useful for us to better understand your problem:
cat /proc/mounts

As a last resort, as you have root you can try saving raw image of system, mount it on your box and push the app there, then flash it back on your device. To save raw system image:
dd if=<block device mounted on /system> of=<output file>

If you go that way make sure you keep the original system image in case something goes wrong.

hope I got dd command in the stock rom ...

@Wang I've never seen dd missing but there are probably some incomplete system images on some devices, in that case you can use cat /block/device > output-file

Of course all commands shown in this answer require root permissions, so you have to execute them with prepended su command.

For me...nothing was working and finally this worked:
adb root
adb remount

"adbd cannot run as root in production builds"

I'm not sure how generally applicable this is, but I had the same problem and found that this reddit comment solved it for me (on Android Lollikat, which is cm11):
http://www.reddit.com/r/cyanogenmod/comments/2m9t61/how_do_i_remount_system_rw_on_cm11_m12/
Basically, I had to remount by explicitly using /system/bin/mount -o ... rather than just mount -o .... I'm guessing that at some point the version in /system/xbin started taking priority and for some reason that version fails silently. (I say "at some point" because link2sd didn't start complaining about RO until recently.) It looks like it should be possible to edit the PATH to fix this so as to not have to use the command line every time I or an app needs to do this. I'm not sure how yet, though.
FWIW, here's the actual script for my device (s5360 on cm11 / LolliKat). It runs from anywhere but I ended up storing it in /system/xbin so it's globally available to shells.
#!/system/bin/sh
echo "Remounting /system as RW (read/write)..."
/system/bin/mount -o remount,rw /system
mount | grep yaff

That last line is just to give quick feedback as to whether it actually worked or not (since my internal partitions are yaff2). The line before it could be made more explicit as any one of these, but on my device this isn't necessary:
/system/bin/mount -o remount,rw /system /system
/system/bin/mount -o remount,rw /system /system
/system/bin/mount -o remount,rw /dev/block/mtdblock8 /system
/system/bin/mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /system

mount -o remount,rw /system  worked for me. My device is Nexus 5 with Android 5.1.1 LMY48B

I had a similar problem.  I had success when I used Busybox (not to be confused with the Toybox system app):
busybox mount -o remount,rw /system

I found I could mount the system in rw using TWRP's Recovery mode, hitting "Mount" and selecting "System", making sure "Mount as read-only" is unchecked. Then I could copy APK's to the system/app folder using TWRP's built-in file manager.
All my other attempts at mounting as rw using ADB or terminal emulator failed. Didn't try using BusyBox.
From memory, that has worked for me in the past.

Do you have an insecure kernel (boot.img)? Write access to the system partition is usually blocked by the kernel at boot. You may need to flash a modified kernel to be able to obtain write access to /system with adb.
Can you mount /system as r/w in the OS? Then you could push the file to the SD card using adb or just normal USB (MTP or Mass Storage depending on the device) and then copy it to the proper location and set permissions using terminal on the device or a root-enabled file manager. Then reboot and it should be there and installed.

I think when we try to access /system that means it is not rooted yet. They whole point of using root adb shell is to push something like su to /system to root it.

@Wang the OP clearly stated that he already had root


text:
How can Android keep a TCP connection alive when changing network provider?
I'm curious about how Android can keep a TCP connection alive while I'm switching from 3G (mobile data) to WiFi and vice versa.
I'm asking this after I seen that I had an uninterrupted radio stream thought TuneIn radio.
Is that valid only for TuneIn (via some code workaround) or is it a cool feature in the Android API calls?

A TCP connection cannot be kept alive during a network change, since you get a new IP address, causing all connections being terminated.
TCP builds upon IP to get the data delivered. If you change networks you also change your public IP address which is used by the TCP connection to let TuneIn deliver data to you.
This invalidates the current connection and forces you to establish a new one.
But there is still a chance of getting an uninterrupted audio stream. The TuneIn app most likely buffers the stream for two or three seconds to compensate for connection hiccups or even a reconnection.

TuneIn Radio can buffer up to 30 seconds in settings, so switching from WiFi to 3G and vice versa will not interupt the playability. Only if you had a weak 3G connection would you notice any pauses or other issues with play.

Also they may use UDP for delivering streams.

One of the newest solutions to this problem is MPTCP (Multi-Path TCP) . But this one is also not yet widely supported (Apple's iOS7 supports Multipath TCP for its traffic generated by Siri).
MPTCP can stablish multiple sub TCP connections and if supported by devices on a connection, then The connection can be kept even if your IP changes (Wifi to 3G/4G and vice versa).
If you want to know more about MPTCP, read the following article:
http://queue.acm.org/detail.cfm?id=2591369

There's no way to keep a TCP connection alive if your IP address changes (and it will change when going from 3G to WiFi). You don't need uninterrupted connection for uninterrupted playback though - most "radio" apps prebuffer some data to keep the music playing even when you lose connection for a while.


text:
What is the difference between USB On-The-Go (OTG) and USB Host Mode?
What is the difference between USB On-The-Go (OTG) and USB Host Mode?
They seem to be more or less the same. Are they?

In the context of Android devices, the terms are often used interchangeably.
Host mode
USB has two different kinds of endpoint (connected device), like a client-server interface. One device is the computer (or host), and it's in charge: it's the server. All the other devices (the peripherals) are the clients, and can only communicate with the server. Usually, a device can only act in one of those two rôles: it wouldn't make sense for (say) a keyboard to be the host. That's the way the protocol works, and the connectors are designed to make that easier for users: hosts have the rectangular A connector, and peripherals have either the square B connector or a mini- or micro- version.
Host mode is a name for when a device is acting as a host. Every USB connection has exactly one device in host mode. PCs always run in host mode. (You wouldn't usually call it that for a PC, because it's not really a "mode", it's always like that.)
USB-OTG
A phone is a bit different, though. Sometimes you want it to act as a peripheral: for example, so you can plug it into a PC, so the PC can access the phone's storage. Sometimes you want it to act as a host: for example, to connect a physical keyboard or mouse to it. This is why many Android devices now support USB host mode as well as USB peripheral mode: they can act in either rôle. But how can you make this work, when a host's USB socket is different from a peripheral's?
This is where USB-on-the-go (OTG) comes in. It adds an extra pin to the micro-USB socket. If you plug a normal A-to-B USB cable, the device acts in peripheral mode. If you connect a special USB-OTG cable, it has the pin connected at one end, and the device at that end acts in host mode.
This can be a little confusing if one cable has seemingly identical plugs at either end, which do different things. But cables with USB-OTG at both ends are uncommon: it's more common to use an adaptor, which has a host-mode USB-OTG plug at one end, and a rectangular USB-A socket on the other. You can plug a normal USB cable into this adaptor, and it will work normally.
Conclusion
The names refer to two different parts of the USB technology, but they're very similar. After all, if a device "supports USB-OTG," it must support acting in "host mode". The converse is often the case, but not always. Most Android devices that support host mode do so via USB-OTG, but there are a few counterexamples: the original Asus Eee Pad Transformer, for example, has USB-A sockets in its keyboard, allowing it to act in host mode without a USB-OTG cable. And of course PCs support host mode without USB-OTG.
So although the terms are usually used to mean the same thing in the Android world - can I plug a USB stick into my phone? - and for most devices it makes no difference which you're talking about, there is a distinction.

Don't forget the power.... OTG requires a y-split cable for those that require external power - perhaps for a device that requires stronger power...Also USB peripheral did come into presence until after Honeycomb which introduced it.

@t0mm13b Actually it's entirely possible to supply power to connected devices via USB-OTG, just as with normal USB. It's just that most phones won't supply enough power for high-current devices like hard disks: but that's to do with the specific device, regardless of whether USB-OTG or normal USB is used.

@t0mm13b I'm not sure what you mean by "USB peripheral did come into presence until after Honeycomb which introduced it." Android has always supported acting as a USB peripheral.

No, it required a custom kernel - and it was iffy support depending on the chipset, it was in Honeycomb API that the USB support came into being and became more popular in ICS upwards

@t0mm13b Peripheral means, for example, being a USB mass storage device that you can plug into a PC. I think you're confusing that with host support, which was added in Honeycomb.

@Dan Hulme: So what does it mean when USB Host is mentioned in the specifications of a device, but there is no USB OTG? for example in Galaxy Note II.

@Omne If you have another question, please ask it by clicking the Ask Question button.

@Dan Hulme: I don't think it is a different question, thanks anyway.


text:
Samsung Knox For Non Pre-Installed Devices?
I heard about Samsung Knox recently. I have a simple question about it: how to download Samsung Knox and install it to my Samsung device which doesn't have Knox pre-installed? I believe the pre-installed Knox is only on Galaxy S4 device.

FYI it also comes on the Note 3, at least the UK version.

According to the official KNOX website, Samsung KNOX is tightly integrated into the operating system. It uses hardware support to verify the bootloader integrity, a custom bootloader to verify the OS integrity, and a custom kernel at runtime. It changes the layout of the device's filesystem to add separate encrypted storage for the business-related files. It also relies on hardware support through ARM's TrustZone technology.
Depending on how much of the hardware support already exists on other Samsung devices, it may be possible for Samsung to later backport the KNOX feature for older Samsung phones with a device update, but it's certainly not possible for anyone else to do so, not even by installing a custom ROM. (That wouldn't add the bootloader support to ensure the ROM isn't changed later.)


text:
What do the different coloured bars on the 1x1 widget in Better Battery Stats app mean?
I understand these are supposed to signify ratios of different phone states but I cannot get my head around which is supposed to be which.

Are you talking about this?

Source.

Perfect, thank you! My Google skills must be very poor today.... I'll accept shortly after forced delay.


text:
Galaxy S2 screen is black, but touch-screen still functional.
No idea what happened, last night it was working till it ran out of battery and turned off. Woke up this morning and kind of rolled over on it with my elbow, no big deal it seemed like though. A little while later after I charged it the phone would turn on, make the sound etc but nothing on the screen, I can still feel the vibration when I try to move an icon for example. And it the computer still recognized it when plugged in, any solutions? Or am I outta luck?

Did it crack when you rolled over it? Try taking out the battery for a few minutes, put it back in. See if that helps? If not, I suggest you take it to a service center.

Nope, and your solution didn't work. Guess I'll have to get it fixed, thanks for the help anyways :(

Coming from an off state, can you go into download mode (volume down + home + power combo) or recovery mode (volume up + home + power combo)?

@geffchang No unfortuantely not, nothing appears on-screen. Damn it lol

Based on the comments, this looks like a hardware issue, and not a software/Android issue. I would suggest sending it to a service center for repair.