My Samsung Galaxy A32 restarted itself and now is stuck at this 'Phone is starting...'. I googled ways to resolve this but none work, The last option\resort is to factory wipe, but I have images on here that I have not yet copied to the SD card or cloud stuff setup (yes, I know I should). I tried to see if I could see the data via the ADB debugging option but it's all 'empty', I suppose it's not allowing me to view it until it 'loads'? I tried the wipe cache partition, restarting multiple times, turning off and waiting then powering back on, and rebooting in safe mode, somewhere mentioned to turn battery saver mode off but it was already off + the toggle didn't work but I managed to get to it via the Settings menu (the only thing I can access) and thought I'll turn it on then off... now it won't turn off, entering the 'download mode', then exit and reboot. Anything else I can try, all these applications to download to repair the phone seem dodgy or not what I need. I thought about downloading Odin and the firmware from somewhere to reinstall, but that would wipe all my data right? What about rooting it would that give me any functionality to access the data? Can I even root it if I can't install apps?

Running a rooted Galaxy S2 with DarkyROM2 2.3.5 & SuperCore kernel. I have a 32 GB microSD card in addition to the 16 GB internal storage, and it takes ages to scan both when the phone boots. At times when I connect USB mass storage mode and later turn off, it goes into an infinite reboot loop. Have tried [this](https://market.android.com/details?id=com.addz.mediascannerroot) , but it doesn't appear to work. Any other workarounds?

I am trying to install latest Lineageos for mata on Essential ph-1. It is stuck at fastboot flash boot boot.img with the warning about avb, boot partition size of 0. Boot image size: 33673216 and fastboot getvar partition-size:boot returns partition-size:boot: 0201d000. The boot image is larger than the partition. The boot image (33673216 bytes) is larger than the reported boot partition size (33671168 bytes, which appears as '0' in the fastboot warning due to an error). How do I fix this and get lineage OS installed on Essential ph-1?

I have a problem with booting my Lenovo A1000, so I decided to flash a new firmware. I have tried it many times, but every time the phone finished flashing, and the SPD Factory Tool passed with 100%, the phone couldn't boot. I have already tried 5 flashable ROMs, but the same thing happens every time. So I decided to check its recovery, and there I found > E: Can't mount/cache/recovery/log What can I do?

I need to force a selected application to start up each time my Android-based device is (re)started. Is there anything I can use (configuration setting, external application etc.) to accomplish this task? Or is this kind of behavior limited to home screen managers only?

I have an issue with my LG K10 (K430, MT6753). I was experimenting with it to learn the adb function. I accidentally erased the whole boot partition using rm, and then my phone is not booting anymore. It is showing the LG boot logo, but not starting up, keeps rebooting. I tried to: 1. Repair it through LG Bridge, to flash the stock ROM through LG UP and LG Flash Tool. But the phone is not staying in Flash mode or Download mode, and can't boot into Fastboot. The only thing that apparently works is the Factory Reset mode, but it only shows the interface. It only reboots the phone and nothing else. 2. Flash the boot image through SP Flash Tool, but have no luck. The phone is detected by Windows, but only for 3 seconds, then it disconnects. No matter what I do, when I connect the phone to my PC, it quickly disconnects, even with Driver Enforcement deactivated. I tried LG drivers and some other drivers for Mediatek, but still have no luck. Is there any other way to recover the boot partition's data or to unbrick my phone?

I have a Cloud Mobile Stratus C7 and the device at first was dead so I plugged it up before powering it on. Once I did, it began showing a screen saying "Select boot mode" with the options recovery mode, fastboot mode, and normal mode. It tells me to use the volume keys to select, but the arrow is moving on its own and the screen keeps turning on and off. I've searched online but nothing seems to be helping. Any advice?

## Situation I have an old phone, it's been replaced, but it still has some photos on I want to recover. From the symptoms I presume it must be a hardware fault, and I am wondering what options are available to me. I have a friend who works as an embedded engineer who is willing to help me try get the photos off of it. The current possibilities they could think of are: - Buy a cheap new screen to connect to the phone to see if we can get the UI back - Attempt to connect via the JTAG pins and execute a script to extract the data Are there other options? Or should we go with one of these? ## More information If it's relevant, the phone is a Pixel XL. A possible silver lining is I was running LineageOS, so I unlocked the bootloader and was never able to re-lock it. The symptoms at the time of death were: - Phone would randomly restart every few weeks - This got more and more frequent - One day the phone restarted and never turned back on - If I held the power button to turn it back on, the phone vibrated yet the screen never turned on - When plugged in the red light didn't appear even though it was drawing Watts - Forced resets (holding power and volume down button for 30+ seconds) sometimes caused a vibration but nothing ever appeared - Plugging it into a laptop resulted in no devices being visible to the laptop (presumably I needed to enable file transfer via the UI which wasn't possible) It's since sat in a box for 2 years and now there is no vibration whatsoever, but it does still draw current when charging. (I contacted multiple places about data recovery in the last couple of years but never received a response.)

My Allwinner Android KitKat 4.4 tablet has been displaying this when powered on but remains on this display. How can I get the tablet to pass this display? What could be wrong, and how to resolve it?

I'm trying to solve a problem that is affecting a **Moto G 2014 XT1069** device. What has happened is that the device did shutdown, then when trying to power it up again, it stayed stuck on the Motorola logo for some time. Another person trying to help, said that it was needed to format the cellphone and rebooted into recovery mode. The point is that when trying to factory reset an error appeared. This person then said that the device was bricked and needed to do something to correct it. Then using fastboot through a computer, I don't know what she did but the situation got somehow worse. The first thing is that she unlocked the bootloader. But after all the procedure what happens is that when the device powered up, it just got stuck in a screen with a message **WARNING BOOTLOADER UNLOCKED** and it *doesn't progress any further*. On that same screen it is possible, by pressing **PWR** + **VOL DWN** to access the bootloader, but even if we select "Normal Powerup" or "Recovery", the device just gets back to the screen **WARNING BOOTLOADER UNLOCKED** and nothing more happens. Furthermore, it seems that the battery became somehow "mad". After a *quite long* time interval charging, the device got to 29% of battery and after just a few minutes trying to correct all this mess, the battery got to 6%. I don't know what they did and how all of this happened. How can I fix this mess? How can I make the cellphone boot and make everything right again? If possible I want to avoid flashing the factory image for the reason that I don't have access to the image from the official source and I feel quite uneasy to get from one untrusted source, since it might compromise confidential data. What can I do to solve this? I believe there has to be a way to correct all of this.

How to start Android and bypass the SIM PIN? I'm asking myself why it is not possible to start/boot Android without entering the PIN for the SIM card. The smartphone is a computer, with it's own authorization mechanism (device pin, finger print, ...) that I could easily use without access to the SIM and therefore the mobile network. (It is not about the screen lock pin). Why does Android not allow to start without this SIM card PIN and later enter the PIN? (E.g when I looked it up in my password manager in the phone)? I'm using a Google Pixel 4a - Android 13 (not rooted). I've not found a way in the settings about this. Is there any way (removing the SIM is not a real solution)? To add more context / explenation: - The smartphone is protected with the device PIN (or finger print, ...). This is required on "login" after a reboot or to remove the screen lock. - The SIM card is protected with the SIM PIN. This pin is required when the SIM functions are accessed - usually the smartphone keeps its authenticated access to the SIM functions once accessed for the first time as long as it is running. (This is not a permanent unlocking of the SIM, I don't know if this is even possible) - The problem is that on startup/boot of Android is accessing the SIM card forcing to enter the SIM PIN. This can not be skipped. This shall not be needed, as the Smartphone would work fine without the SIM as well (e.g. if physically removed).

I can't find a good reason that this application must always be running on my phone. However, it starts at boot and I'm constantly getting error traces in Logcat about the Ebay application. Why does this application start at boot?

Just like iPhones are pretty hard to get into once they are locked, due to USB being completely disabled, is there something similar for Samsung, or any Android at all? This prevents many exploits from being applied to a locked device. What about prevent from entering DFU mode or any similar mode?

I have a SviCloud TV Box. The box boots up to be stuck on the loading screen. It kept going "copy/write template file". I went to recovery and erased data/cache/reset/reboot. Great, it passes that point and even goes through all the initial setup steps, but afterward, it's stuck with wallpaper and no GUI. I'm guessing something in the OS broke, now it's not loading the launcher or something. It's not the first time something like this happened, the last time I had to bring my box back to my seller for repair. So now I'm thinking, is there a way, for the future, that I can rip out the firmware from the box? Either whatever the box has as is (NAND copy?), or maybe rip out any OTA downloaded firmware. Which then I can use the image to reflash my box (which I figured should fix most of the problem unless it's a flash memory chip going bad). Any pointers would be appreciated.

If we install our TWRP in ramdisk, which button combination do we need to boot again into the TWRP? In Xiaomi Poco M4 Pro 4G, there is no recovery partition, but there is a recovery software which we can access with the default button combination. I don't know in which partition the default recovery is stored.

I'm trying to mount the directory of an app to a folder in storage. I've put a script called custom.sh inside "/data/adb/service.d". The contents of the script are:

#!/system/bin/sh

sleep 30

mount -o bind /data/data/is.xyz.mpv /storage/emulated/0/Test

It just doesn't work. Can anyone point me in the right direction please?

I see [stackoverflow.com/revisions/20060853/1](https://stackoverflow.com/revisions/20060853/1) (paraphrased unmdermentioned), which appears to answer a similar question, although the answer that it provides causes me to believe that the services are *hardcoded* inside a user-inaccessible (even with standard adb access) POSIX Shell Script:

The statement "Service declarations only serve to describe services, they do not actually start anything" is correct. The native daemons are actually started in init.rc by lines 371-372 in [android.googlesource.com/platform/system/core/+/master/rootdir/init.rc](https://android.googlesource.com/platform/system/core/+/master/rootdir/init.rc) : - class_start core - class_start main ...where all daemons that belong to class *core* and class *main* are started respectively.

[Another answer, from *this* forum](https://android.stackexchange.com/revisions/6559/1#:~:text=/data/init.sh%20runs%20at%20boot%2C%20if%20you%20have%20root%20you%20can%20edit%20it%20as%20you%20like.) , to a similar question, mentions a near-duplicate file that acts identically (although it doesn't elaborate much – it, too, is paraphrased undermentioned): > /data/init.sh runs at boot. If you have root, you can edit it as you like. Inherently, their formats don't render them application-unmodifiable, but the sole alternative example of a user-modifiable shell script configuration file that I've seen is GRUB2's /etc/default/grub, which I was under the impression was a *singularly* exceptional circumstance, especially because modifying it necessitates superuser permissions. Relevantly, the security reduction that would arise from permitting applications to add arbitrary shell commands to that script would be obvious enough that I do not envisage this being the method by which services are added and configured. Consequently, does AOSP include an initialisation system that applications can add to? ##### Rationale The reason I ask here is because I'm asking as a user instead of a developer. That may appear nonsensical, but hopefully situations like [github.com/TacoTheDank/Scoop/issues/65#issuecomment-2571309312](https://github.com/TacoTheDank/Scoop/issues/65#issuecomment-2571309312) , in which users must utilize development tools to bypass platform restrictions, provide adequate rationale.

By battery insertion I mean current flowing on the battery pins, **not** the micro USB port. **Description** The phone in question is a Samsung Galaxy Xcover 4, the **bootloader** is **unlocked**, and I have **root access**. Its intended purpose is as a kiosk device that will be sealed inside an external hard plastic enclosure. This means that the power button is unavailable for booting the phone. The phone is powered directly from the wall by means of a custom-made battery eliminator PCB, and I need the micro USB port for host mode UART communication, which means it will never be charged/powered via the micro USB port. **What has been attempted so far** As mentioned, the device is rooted, so I've tried modifying the BOOT partition image and flashing an updated one. The modifications I've been looking at pertains to the program /init in the root directory. and its associated /init.rc /init.samsungexynos7570.rc /... files. For example, I was able to make the phone boot upon receiving charge via the USB port by overwriting the contents of the file /system/bin/lpm with the script #!/system/bin/sh echo b > /proc/sysrq-trigger because /system/bin/lpm is referenced in a service specified in the charging section of /init.rc. I was also able to make it boot via USB port charging by removing the existing "on charge" triggers in the init.*.rc files, and simply adding on property:ro.bootmode=charger: trigger late-init For more details about what I did, see this link . But this is **not a solution for me** because I want to make it boot simply by powering the battery pins, not the micro USB port (which is preoccupied with being in host mode, so it definitely can't be charged). **Further thoughts** However, since modifying the /init.rc file changed its behaviour even while "off" (i.e. it now boots upon micro USB charging as opposed to not), this seems to tell me that the phone is never really completely off when "off", and that the /init program is constantly running as long as there is enough charge on the battery pins (please derail this thought train asap if this is completely wrong). Which would mean the kernel and the /init program should start automatically when there's sufficient charge on the battery pins. So my thinking was to simply add something along the lines of trigger late-init or start (where *my_service* for example could be the lpm script I mentioned above) in an early init trigger stage, so that it would boot simply by virtue of the /init program running. But so far I've had no luck. Does anyone know whether something like this would possible? Thanks for your time.

**Rationale** I have approximately 15 devices with AOSP distributions installed. These are mostly OEM derivatives, with Google Mobile Services (GMS), installed onto bare metal (via the bootloader's recovery). I also have some BlissOS installations, operable via WayDroid (installed on Fedora 41, postmarketOS, and openSUSE Tumbleweed, although this shouldn't matter). Initialising all of these devices can be tiresome. Additionally, sometimes I want to compare hardware capabilities, like boot time. This means that I want them to commence OS initialisation simultaneously. Consequently, I want to know whether these devices’ and hypervisor(-abstracted)s’ installations can be initialised via a WOL (wake-on-LAN) packet. **Potential Solutions** I've located [chromium.googlesource.com/aosp/platform/system/connectivity/shill/+/57a957e8112a42ce0cf16fbe94f6a482b937db42/bin/set_wake_on_lan](https://chromium.googlesource.com/aosp/platform/system/connectivity/shill/+/57a957e8112a42ce0cf16fbe94f6a482b937db42/bin/set_wake_on_lan) , but I don't know whether this is what I'm looking for, because I'm no POSIX shell script savant. [reddit.com/r/AndroidTV/comments/zcpqf6/comment/iyycefy](https://www.reddit.com/r/AndroidTV/comments/zcpqf6/comment/iyycefy/) appears to indicate that this is included by some Android TV OEMs.

We all have heard of fastboot boot xxxx command. How does it work when you use it for the kernel (fastboot boot boot.img)? 1. Does it boot Android with that kernel if possible, or does it make that kernel permanent? If not, how does it work? 2. Does it just put the kernel you specified in RAM instead of one in internal memory? 3. Also, what happens if the kernel can't boot for some reason? Does it soft-brick the device or just boot the existing kernel? 4. And if the kernel is ok and it boots, how to get back to using the kernel from internal memory?