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 .

This question might seem to be a duplicate of [this question](https://android.stackexchange.com/questions/24525/why-is-custom-recovery-a-prerequisite-for-flashing-a-custom-rom) but it is different. But I'd like to have a brief explanation on why we need a custom recovery to flash a ROM. My main points of confusion are: 1. In stock recovery we have a option to "*Install Update from SD card*". Why can't we directly flash a ROM from there? 2. If signature verification is the problem regarding the first point, then how can we root and flash custom recovery using update from SD card? Why doesn't any signing or verification problem occur while flashing root package or custom recovery package? Like any other custom ROM package they are also unsigned. Why is this?

My phone is currently stuck in a boot loop. I tried using minimal adb and fastboot but I can't seem to do it. I have also read in some forums that usb debugging should be enabled and the phone should be rooted. Is there a way to use adb commands without enabling the usb debugging('coz I can't). I tried all the choices in the recovery mode except the factory reset. Can somebody help me? I really need to recover the memos that I have saved. I have a Samsung galaxy V duos.

I am on a Fairphone 3 and run /e/os 1.9. # Background # I recently started to run out of disk space each time one of my apps (Signal messenger) started to create a new backup, as my free space was not large enough to accommodate a new backup file. Yesterday I turned off the phone when I saw that the "little storage left" notification came up and the backup was running, and put a brand new micro SD card in the phone that I had meant to set up since a while. After powering up the phone again, the notification for low storage was (non-surprisingly) still showing, alongside with one for the new SD card. When I opened the SD card I saw that a lot of empty folders had been creating, mirroring the ones in my internal storage. The phone also started to vibrate repeatedly and showed "No log (file) could be created" in a small popup on the bottom of the screen. I decided to ignore that and try to move some files from the internal storage to the SD card to free up some space. After a short while, the phone crashed and rebooted into recovery. # Problem # When I power up the phone, it boots into recovery, showing this screen: Recovery Version 1.9 () Active slot: a Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device. > Try again Factory data reset I can also navigate back into a recovery menu. When I select *try again*, the phone starts up as normal. I get then to unlock my SIM. However, as soon as try to unlock the normal lock screen for the first time, the phone will crash. If I just try to unlock the screen, an empty home screen will show for a moment, before my normal home screen loads (I use lawnchair as a launcher, which is not /e/os default). Then, sometimes a popup comes saying *??? launcher crashes all the time*, partially obscured by an other popup saying *Power off*. The phone will then reboot into the recovery. If I try to directly go to the settings page by swiping down and clicking the settings shortcut, that page is shown for a second or two before the phone also powers off and reboots into recovery. If I click on the "Out of storage" notification, the same thing happens. **I would really like to prevent losing my data.** # What I have tried so far # It appears like I can't do anything after unlocking my phone, as it will reboot directly. I have gone through the recovery and fastboot menus, trying to find anything that could be of help. I was able to activate ADB and browse around in the file system using

shell

, but none of my personal files where accessible and there was apparently a lot of space available on that partition. I was also able to *mount system* from an option in the recovery. Even this partition showed only 73% disk usage. It was also read-only, so I was not able to remove any files. The sdcard folder in both

/

and

/mnt/system/

was empty. The recovery also gives me the option to install an update, e.g. via adb sideload. I have not tried that, since I don't know how to do so and if it will give me access to my personal data. # What to do now? # If this would be a computer, I would use a live linux system to run

and similar tools to identify and repair the corrupted data and to free up some disk space. Is it possible to do something similar with my phone, for example using adb? Is there any way to access/recover and possibly back up my personal data?

My tablet is not rooted. I made a backup of it through console (in recovery mode): 1. boot my tablet in recovery mode 1. go down to menu "backup user data" After that, in my sdcard, I have three files: - userdata_20160211_092627.backup - userdata_20160211_092627.backup1 - userdata_20160211_092627.backup2) Then I moved the sdcard to another tablet (which is the same model), and recovered this backup there through recovery mode (steps as above, just selecting "restore user data"), but after about 10 seconds I get this error: "Checksum compare fail". Does any body know how to fix this error or how to disable the checksum in the .backup file? (this works if i recovered on the same tablet that i have made a backup in) Thanks

I have an extra phone, i.e., Samsung SGH-i997, at home. A while back, I installed **Clockwork Recovery** and installed CyanogenMod ROM on it. Then somehow, out of stupidity or accident, it went back into recovery mode, and everything on the phone was wiped. It even deleted Clockwork Recovery, and I guess that even the factory firmware isn't there anymore. Now every time I turn on the phone, it automatically goes to the default recovery mode with 4 options - reboot system now - apply update from SD card - wipe data factory reset - wipe cache partition I have tried switching it to **download mode** and connecting it with my laptop, but the drivers are not recognized. I also tried installing kies, which I thought would help with the driver issue, but it didn't. I guess there isn't any firmware inside that the driver would connect to. Now the only way left to somehow copy something to the phone is via an SD card. I tried copying several different Android firmware and mods to the SD card, but I think the default recovery mode doesn't use the external SD card but the phone's internal SD storage, which i why everybody is using Clockwork Recovery instead of default. I am really tired of searching for a solution to this issue. If anyone out there has done something similar or can somehow show me how to go into the shell, I might be able to find my way. Thanks in advance.

I am trying to root my Samsung Galaxy Ch@t GT-B5330 (4.1.2) following this guide. I have reached the point when I am intended to use the recovery mode menu (that is reached by holding volume-up when turning the phone on) but here am I stuck: whatever I choose gives me the error icon I am still able to boot the phone the normal way (though it has became a little bit slower than it was before flashing and starts Firefox on itself occasionally). How do I finish the rooting process?

It happened when Google Play was automatically updating apps. I guess, something went wrong and the phone suddenly restarted and was not able to turn on again. It always gets stuck on "Starting apps" screen and then restarts again (bootloop). I figured out, that if I can delete the app causing bootloop it should be just fine. However, I don't know how I could do it.

My phone is nexus 4 running Android Marshmallow. Also, I have a custom recovery (cwm 6.0.4.7). So, I tried to connect through adb to the phone in recovery mode and delete the app, however, I can't use any adb command, because "device unauthorized". I assume, as soon as I can get access through adb, I can delete the app.

After surfing many forums for the past several hours I couldn't able to find any solution which preserves data the phone has. Any ideas how I can delete/fix the app without loosing any data? (nexus 4 doesn't have SD card slot). Thanks. P.S. wipe cache partition didn't help.

I have just bought a second-hand Oppo Find X6 Pro and it has a global ROM on it. I don't know how they did it because there's no global version of the phone. I think they might have tweaked the firmware because everything seems valid, except it hasn't got any updates and its security patch is of June which is pretty behind for this device. This is the version on it: PGEM10_13.1.1.144(EX01). The (EX01) OPPO Reno 10 Pro 5G has it and it stands for a European version, I think. That's why I say they might have tweaked something because even Google recognizes the device as OPPO Reno 10 Pro 5G. > **Check your Oppo Reno10 Pro 5G** > > Google sent a notification to your Oppo Reno10 Pro 5G. Tap **Yes** on the notification, then tap **17** on your phone to verify that it's you. So I wanted to roll back to stock firmware. I downloaded different stock ROMs, but there wasn't any way to flash them on the device. Can someone help me and go back to the stock ROM? - I tried https://oppostockrom.com/oppo-find-x6-pro-pgem10 but didn't figure it out. - I also used the QPST Flash Tool, but the firmware didn't contain anything to open it inside QPST like .hex or .mbn. It just had .elf for the programmer which when I chose it to flash the ROM, it said error FireHose. - The recovery mode also doesn't have a local update and online update. - When I reboot to EDL using adb, it just shows a black screen, but the computer does recognize Qualcomm 9008. I think the recovery is also not stock. I will attach the system information:

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 have OnePlus 3 (A3003). I installed a custom ROM. Since then, I can't get to recovery mode. If I try booting into it, my phone gets stuck on the OnePlus logo. I tried flashing it with fastboot,

C:\...\Android\android-sdk\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 442499072 bytes
sending 'recovery' (18964 KB)...
OKAY [  0.580s]
writing 'recovery'...
OKAY [  0.144s]
finished. total time: 0.726s

And also I tried flashing it with the TWRP app, it gave me an error telling me that I have already installed it. What is the problem?

After entering wm size 1920x1080 in terminal I was unable to reset this setting. Now I have TWRP running and no information about how wm store its parameters in memory. Using adb is not possible (for adb shell wm size reset) as I cannot unlock phone (nor with usb keyboard nor with usb mouse) So the quiestion is: how to reset changes of wm command or unlock a phone with usb keyboard or mouse (graphical key)?

My Alcatel Android decided not to boot. It starts and says "Alcatel" then just flashes "enjoy now" about 60 times until Android Recovery. TCL/5003D_EEA/Curie 8.1.0/0PM2.171019.012/5003D_ALGB_V2.3 If I click "try again" I get Android Error and it then starts the reboot process again. I can access Android Recovery by removing and reinserting the battery, holding down Power Button, both Volume Up and Volume Down all together, once it says "Alcatel" releasing all of them, it then enters Android Recovery. I have tried "reboot now, I have tried Wipe Cache partition". What is my next move please? Are the recovery logs useful for anyone to help me?

So I was going to root this (previsouly healthy) BQ A4.5. Unlocked the bootloader and flashed [TWRP from here](https://twrp.me/bq/bqaquarisa45.html) :

$ fastboot oem unlock
(bootloader) Start unlock flow

OKAY [ 32.954s]
Finished. Total time: 32.960s
$ fastboot flash recovery downloads/twrp-3.3.1-0-dendeone.img
target reported max download size of 134217728 bytes
Sending 'recovery' (11342 KB)...
OKAY [  0.378s]
Writing 'recovery'...
OKAY [  0.335s]
Finished. Total time: 0.727s
$ fastboot reboot bootloader
rebooting into bootloader
OKAY [  0.003s]
Finished. Total time: 0.058s
$ fastboot reboot
Rebooting...

Finished. Total time: 0.058s

The first reboot to bootloader didn't do anything. Now it's on a bootloop which states:

Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

Pressing _Volume Up + PowerOn_ used to work for recovery (that's how I got into fastboot mode). Now, pressing _Volume Up/Down/Up+Down + PowerOn_ doesn't do anything, fastboot stands indefinitely `, and adb always responds with error: no devices/emulators found` regardless of when it's run. If I press _Volume Up+Down_ it turns off. Plugging in USB it turns on. Nothing else seems to respond. dmesg states:

[32774.364937] usb 2-7: new high-speed USB device number 59 using xhci_hcd
[32774.514434] cdc_acm 2-7:1.0: Zero length descriptor references
[32774.514450] cdc_acm: probe of 2-7:1.0 failed with error -22
[32774.554519] cdc_acm 2-7:1.1: ttyACM0: USB ACM device
[32777.142205] usb 2-7: USB disconnect, device number 59

The disconnect happens before the bq logo appears. Trash bin time?

I have Xiaomi Redmi Note 8T (ginkgo). I was installing a new ROM, wiped the device, and from TWRP, flashed the recommended recovery from the CrDroid device page - SHRP (SkyHawk Recovery Project). After flashing, it said it was going to reboot to recovery, but it didn't, and it seems to be stuck in a loop. - Holding Power and Volume down - Vibrates and just flashes. - Holding Power and Volume down - Orange Fastboot logo flashes on and off. - When the buttons are released, it goes blank, i.e., the phone stays turned off. - If connected by USB to a laptop, it keeps flashing every second. - adb fastboot does not recognize the device: - using adb devices = just says: List of devices attached - adb reboot bootloader = error: no devices / emulators found - fastboot reboot = Any way out of this?

For the purpose of flashing custom ROM I flashed Lenovo Tab M10 FHD Plus (X606F) with Android 9 ROM. I used SP Flash Tool. Now the tablet won't power on. Pressing buttons does nothing. Can't invoke fastboot nor recovery mode. Red LED indicating charging is the only thing the tablet is giving me now. I've tried to restore the device using official Lenovo's Rescue Tool. Process of restoring gets stuck on 40% and won't go on. Hard reset (pressing and holding volume buttons + power button for few secs) isn't doing anything. What else I can try ? I've followed the steps outlined and I got to the point where Windows doesn't recognize the tablet:

I have Samsung Galaxy M11 (SM-M115F/DS). I want to install TWRP in it. But I can't unlock the bootloader or go to download mode. I already enabled OEM Unlock. I saw on some sites that on this device I have to press both volumes up and down to go to download mode or unlock the bootloader but actually, nothing happens. It only goes to recovery mode with power and volume up. There it has a "Reboot to Bootloader" option. When I go there, I get this When I give the options to start, I return to recovery mode.

My phone screen broke. I can't see anything, and the touch screen doesn't work. I can't buy a new phone, so I'm not looking into backing up my data. I want to be able to use it from my pc. I have a Motorola Moto G2 running LineageOS 14.1 and TWRP custom recovery. Until now, I have been able to use my phone from my PC using [Vysor](https://vysor.io) , because I previously had USB debugging activated. However, **I accidentally deactivated it and now I'm stuck out**. I can access via ADB through recovery and **already have investigated how to activate USB debugging** again from the shell using these sources: - https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock - https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb - https://android.stackexchange.com/questions/12834/broken-screen-while-debug-mode-was-disabled-how-can-i-re-enable-adb - [Enable USB debugging through Clockworkmod with adb ](https://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb/13332721#13332721) - https://android.stackexchange.com/questions/55674/how-can-i-enable-adbd-during-boot-on-cyanogenmod - [Manually enable adb debugging from recovery](https://forum.xda-developers.com/showthread.php?t=2335799) - [How to authorize adb service from boot](https://groups.google.com/forum/#!topic/mozilla.dev.b2g/epQ6qhIFZ50) But **none of these solutions have worked for me.** Here's a brief summary of everything I've tried: - I've set the content of /data/property/persist.sys.usb.config to mtp,adb - I've edited /data/system/users/0/settings_global.xml, setting adb_enabled, verifier_verify_adb_installs and development_settings_enabled to 1 - I've added these lines to /system/build.prop: `persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb` - I've used the following setprop commands: `setprop persist.service.adb.enable 1 setprop persist.service.debuggable 1 setprop persist.sys.usb.config mtp,adb` But when I reboot, I still can't see my device when I run adb devices Not only that, but then **everytime I reboot to TWRP recovery again, I notice that some changes are reversed:** - /data/property/persist.sys.usb.config content only says adb - /data/system/users/0/settings_global.xml remains almost intact but adb_enabled is back to 0 again - When I run getprop to all of the properties I've set before using setprop, it returns an empty string (which makes me suspect that the changes I've been making to /system/build.prop are being completely ignored) **It's as if everytime the phone boots, the system loads some default configuration and reverses some of the changes I've made and USB debugging remains deactivated**. Am I missing something? I really not know what else to do.

I have a full phone backup of a LineageOS 21 (Android 14) install containing all partitions copied to my Linux PC. I can mount several partitions, such as /system. However, the /data partition /dev/block/sda19 is of course encrypted. I have the full phone backup. I know my Android PIN. How do I manually decrypt and mount the /data partition?

I am following this guide: [\[GUIDE\] Unlock/Root/Flash for Nexus 6P][1] The bootloader is already unlocked. Now I'm trying to flash the **TWRP recovery**. (Section 2). As the device runs Android N, I first flashed the modified boot.img (like in the guide, also tried it with stock boot.img) and then I flashed the **TWRP recovery** like this: username@my_pc:~/Android/Sdk/platform-tools$ ./fastboot flash boot '/home/username/Downloads/boot.img' target reported max download size of 494927872 bytes sending 'boot' (12272 KB)... OKAY [ 0.333s] writing 'boot'... OKAY [ 0.185s] finished. total time: 0.518s username@my_pc:~/Android/Sdk/platform-tools$ ./fastboot flash recovery '/home/username/Downloads/twrp.img' target reported max download size of 494927872 bytes sending 'recovery' (16932 KB)... OKAY [ 0.453s] writing 'recovery'... OKAY [ 0.251s] finished. total time: 0.704s Then I rebooted to the **bootloader** again, and then booted to the **recovery mode**, like explained in the guide: >Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable. However, it just hangs at the TWRP splash screen: The phone still works and can successfully boot to Android N. I know the bootloader is unlocked because of the unlock symbol at boot logo, and I rooted it (same guide) on Android Marshmallow. About phone (click for larger image):