Downloading coming from the list of devices allows to download a .img image which can be transferred via MTP-USB connection and installed after selecting Images in the Install file browser. When asked to select between boot and recovery partition select the recovery partition (selecting the boot partition has at least no effect and might be harmful).
I succeded adding the -k and --user options to the pm command, e.g.:
pm uninstall -k --user 0 com.android.service
The command was issued as root, no need to remount /system as rw. Android on the phone is 6.0 and the package is a system app. Without the extra option I get the error:
To my knowledge, TWRP does a nandroid backup. As you can read in the tag wikis of the mentioned tags (nandroid, backup), a Nandroid backup takes images of your partitions. It's not a backup on the file level, but on partition level. So it includes everything stored on those partitions. Doing a full Nandroid backup of your system thus includes the entire ...
These /data-related errors are likely because TWRP can't decrypt the current /data partition. This often happens with stock ROMs, since TWRP is only made to handle the encryption method of AOSP.
To work around it, in TWRP, choose Wipe - Format Data. This will wipe all data from the device, but at the same time remove encryption and allow you to start off ...
cat data.ext4.win??? | tar xvfi -
What this does is concatenate each file matching the pattern data.ext4.win??? and then pipe the concatenated files to tar for extraction. the - as the filename tells tar to extract from stdin. The i option ignores zero blocks which will be in between each archive file concatenated.
In this example I used the ext4 ...
Basically the Zip File Signature Verification flag will enable flashing only if the zip file is signed properly by the developer. This is (almost) the same method used signing Jar files in Java.
Basically, before executing any third-party program you want to make sure that it hasn't been tampered with (integrity) and that it was actually ...
Download and untar
After this, just copy the extracted executable "adb" over old one in /usr/bin.
Rename the system.ext4.win file to system.ext4.tarand extract it.
TWRP backup is not in compression method, you will directly get to the /system folder or if your TWRP backup is in compression method, you will get a file named system.ext4 which you'll have to just rename it to system.ext4.tar and extract it to /system folder
Looking at the installation instructions of the ROM you flashed, I am guessing in the TWRP/ CWM options, under Advanced Wipe , one of the options " Wipe Dalvik Cache, Cache, System and Data " (likely data) was missed out leading to the current situation.
Thanks to OP for confirming that wiping data was missed out by him while installing CM. A ...
Not a full-fledged answer, as even an excerpt would make it a rather long post, but here are some things you could try:
An XDA article describes How To Backup and Restore using tar on adb shell. The article holds complete scripts for both. Still you should not execute them straight ahead as they are, but first use e.g. the mount command (without parameters) ...
Some stock ROM's may replace the custom recovery with the stock recovery. To solve it you should install the custom recovery with fastboot and reboot to recovery and don't reboot to system. That will prevent the stock ROM from replacing the custom recovery.
The low level implementation of a system which can be used to flash software onto your phone's partitions. Often used to flash root privileges or Stock Roms.
The recovery is another system used to manage/wipe/reformat your partitions. TWRP refers to a custom Recovery which allows you to install custom roms in a zip format. The ...
Boot into TWRP, select Install and follow the screenshots for the rest.
(Click image to enlarge)
It's not a problem for TWRP to which ROM your particular kernel belongs. The size should not be greater than the partition. That's all.
If the kernel is not good for the ROM, your device would not boot into the ROM or would cause some other instability, so ...
Can I mount directly from TWRP's mount screen?
Yes. Under the category Mount you would see a range of partitions available to be mounted. Selecting an entry (check-mark) would automatically mount the corresponding partition and deselecting the entry would unmount that partition. You can mount/unmount multiple partitions.
You can verify the said method by ...
try removing these files also
Instead of removing files, appending the filenames with some random extension would be better. So, if anything goes wrong we can revert the changes.
eg: user.db -> user.db.xyz or xyx_user.db
I faced the same error too and this worked for me.
The files created by TWRP with a *.win or *.win??? extension are tar archives. If a partition gets split across multiple files, each is a tar archive in its own right. Simply rename each file, giving it a .tar extension, and open it in your favorite archive tool (Engrampa on Ubuntu MATE has worked well for this).
As you mentioned you're using Magisk for root, I'm assuming you're running on Android 5 or up.
The answer would be no. You can safely ignore the "Wipe Dalvik Cache" after OTA updating and re-rooting.
Dalvik cache is compiled binary code (optimized DEX) for your installed applications, so it usually makes sense to wipe them if you removed/replaced your apps ...
SELinux is a security mechanism which stops unauthorized access of processes to other processes, actions and filesystems (UNIX's "file" includes all regular files, directories, block devices, character devices, sockets etc.). Every process, file, directory and action is labeled with an SELinux context, then a policy is defined what a context can do to other ...
I ended up looking at Cyanongenmod's source code and figured out how they did it.
Here is my working .sh script:
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/sdcard/update.zip' >> /cache/recovery/command
with android JellyBean [4.1] and later versions, the sdcard data is located now at /sdcard/0,...
The "device not supported" message means that you probably downloaded the recovery image for a different device (AT&T's LG G2 "d802", or International LG G2 "d800".) You can override this check, but it's not recommended, as the devices might be different enough that you could cause irreparable damage to it (a.k.a. "bricking".)
The most current TWRP ...
I think your best bet is to unroot your device and restore it to stock. This means stock ROM, recovery and kernel, and you will be unrooted. This is often referred to as "flashing a factory image", sometimes incorrectly. But that's what we're going to do!
Note: This process will wipe your phone completely. Backup your storage before you continue.
I am ...
Another option, without wiping any data, is to
when an OTA update is available, get the direct link and download the zip file to your PC,
download the latest image version of your custom recovery (eg TWRP) and the latest SuperSU zip to your PC
connect your device to your PC and reboot into bootloader mode
then dirty flash the stock boot, recovery & ...
The answer is the update won't push through if you have a custom recovery like TWRP. I had to restore the stock recovery using the Nexus Root Toolkit. Then the update showed again, and it went through flawlessly. Even the re-rooting part (again using NRT) was perfect.
Yes, your earlier ROM will be fully restored as long as you backup system partition as well since that's where the ROM resides. If you wants your apps and apps' data, then you should back up data partition.
Note: Backup feature doesn't backup SDcard's content. If you delete all the data of the SDcard you will not be able to restore it.
One user reported a method to do this on the CyanogenMod forums back in January, but it isn't exactly detailed.
Similarly, my path has three main steps, with varying levels of detail:
Install a custom recovery. I used TWRP.
Wipe the device.
Note that I did not root the device. This is because I used Odin to install ...
A nandroid backup is a full device backup – so you could ask the same question about a full backup of your PC: After restoring the backup, you'd be at exactly the state the device was in when you performed that backup – all changes done between making the backup and restoring it are lost.
Reading between the lines of your question, you're rather asking how ...
EXTRACTING BOOT.IMG FROM STOCK ROM or OTHER IMG LIKE RECOVERY ETC.
1. Download adb required tools.
3. Phone Drivers (for other phones google it out)
for spreadtrum phones: SCI-Usb-Jungo v4 (download here) or
SCI-USB2Serial v188.8.131.52 (download here)
4. Android Phone + Usb cables
OPEN cmd window in adb ...