I have a Xiaomi Redmi Note 8 Pro. It turned off, and the only way to turn it on is to force boot it, but it turns back off after around a minute. All adb permissions are enabled and the device is not rooted.

I'm running unpack_bootimg --format mkbootimg on a vendor_boot recovery image with header version 4, and it prints these arguments (among the others):

--ramdisk_type 1 --ramdisk_name '' --vendor_ramdisk_fragment out/vendor_ramdisk00 --ramdisk_type 2 --ramdisk_name recovery --vendor_ramdisk_fragment out/vendor_ramdisk01

What's the purpose of ramdisk_type 1 and 2? Why separate ramdisks this way? The recovery image in question is downloadable from here .

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.

A month ago, I used **Kingroot** to root my Sony Xperia Z1 running lollipop . Today, my dad called me on the phone and I picked up. 5 minutes later, the phone will not boot up. I thought that the battery is dead and tried to charge the phone using the original wall plug. The phone will not charge or boot up. It will show red blinking on my phone. I highly doubt that my phone has no battery at all because it is 40% when i last used it to call my dad. Also I have tried to power on the phone by pressing the on and power down/up button but it does not work. I have tried to reset the phone by pressing the small red button at the micro sim slot but is also does not work. I have also tried to use the Sony PC Companion but it does not detect my phone after i have download the installation for the update. I have also tried using Emma but it did not detect my phone at all. Now what I know is that my warranty is void because I rooted my phone and they are going to charge me to fix it. And before I send it down to repair, I would like to know what else can I do to boot up my phone.

I was playing with some **Xposed** modules on Galaxy S4 Mini phone and then after applying some changes, it stopped booting and stuck on boot logo screen. So, I tried to boot it up again in safe mode **by holding Home menu during startup**, as I did to solve earlier problems, but had no luck this time! Still stuck on logo. Then after a little bit of googling found another boot option that can be activated **by pressing power button multiple times immediately after starting the phone** until it vibrates by your keypress. Fortunately, it helped a lot and i could boot up the system and deactivate the problematic module and the problem got solved. :) Before this, I knew only one way of starting Android in Safe mode, which was by holding Home button during boot until you see *Safe Mode* label on the edge of your screen and then all of your downloaded applications would be temporary deactivated. (Although, key combination may differ on other brands.) But, when I booted up using this life-saving way by pressing power button multiple times, * All of my apps were loaded normally * There was no sign of *Safe Mode* label * And thankfully, Xposed framework seemed to be disabled * Although, I still got all other functionalities and even root access What is this type of booting called? Is it some kind of Safe Mode? What Changes does it make to system/services/apps? Is it a feature of Xposed framework or is a part of Android itself? I've done a lot of searching but found nothing technically well-documented about it.

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?

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?