I don't think this is a Moto X (XT1096) specific problem, but more so with TWRP. Phone works fine, just can't backup or restore
I'll try to get a log as soon as I can, just need to figure out how
Problem
I can't backup or restore (and maybe can't delete via TWRP?) from TWRP, getting errors at the start (can't access .../data/cmthemes and can't access .../data/motogallery) and then at the end TarFork() process ended with ERROR=255
Tried Solutions
Reflash TWRP (broke, had to use TWRP app to fix)
Upgrade TWRP (says it failed, but worked)
Enable Compression (no real difference that I can tell)
Cause?
I was on CM13 (2/2 ?), upgraded to most recent (2/6), didn't like it so wiped and flashed to original (1/29 ?) then restored backup (2/2). Probably wasn't the best way to do that, oops. Since then I have wiped and reflashed 2/2 and upgraded to 2/7, haven't done anything since (besides mess with TWRP)
Any help or ideas would be appreciated!
Please lock/delete
Solution: Factory reset, only method that worked for me
Be sure to clear cache
Solution: There is a file on the phone that is preventing the backup. Not sure what is creating it. It could be an artifact of a TWRP backup restoration, which is the first time I had the problem.
Look in the TWRP log ([SDCard]/recovery.log) and scroll near the end - you will find the culprit there, almost always in the [root]/SYSTEM folder but sometimes in multiple folders. It has many names. I've seen it called, simply "999". On my Moto G4, it was "d.addon". Delete the folder and you're good to go.
Hi,
May I please humbly request some help with my issue?
I have an N910T, Rooted, w/MM 6.0.1 Samsung OEM ROM.
I started with TWRP 3.0.2.0 and it was working fine, except that for some reason, my NanDroid Backups would just disappear. I mean even the TWRP folder was gone!
When I would then boot into Recovery, it would say something about a "Systemless Recovery" and then ask me if I wanted it to Write to the System. I would say "Yes" (it's the only way you can even save the options you choose).
All would be well for a bit and then it would happen again.
So I tried replacing TWRP with PhilZ Touch Recovery 6.59.0 and it was working fine, until it just happened again. Except when I booted into PhilZ Recovery, it didn't ask me about the Systemless Recovery.
I have tried both my Internal & External Storages and it makes no difference.
Obviously this is not good! Does anyone have any idea what's going on and how to make it stop deleting my NanDroid Backups please?
Thank You!!!
TTYL
Hi,
I figured out what this was. For some reason with MM, when you run "Corpse Finder" in SD Maid, it sees the folder with the NanDroid Backups (Recovery app irrelevant) as not being tied to an installed app (i.e., data from an app, but the app is no longer present) and therefore something that's just taking up space.
I just used a "Global Exclusion" in the apps' "Explorer" mode. But the app has since been updated to handle this and not delete them.
TTYL
I installed TWRP 3.1.0 on my XT1096 and everything went fine. I got the mismatched partition size error in fastboot but it still worked. I booted into TWRP directly from fastboot after flashing TWRP. It asks me it I wanted to modify my system so TWRP wouldn't keep getting written over on boot so I had TWRP modify my system so it doesn't happen. I thought okay cool my recovery flash went through fine and went to boot back into the system. Before I booted back into the system TWRP made me aware I had no root access and asked If I wanted to install the SuperSU script, which I did. The script finished with no issue and my phone rebooted. I went into my app drawer and finished setting up SuperSU by downloading the GUI from the Play Store and then I downloaded TitanBackup so I could backup my apps in between switching ROMs. The first hint of my issue was with TitanBackup when I tried to make a backup of my user apps. Titan errored out after backing up the first app and left me with an insufficient space error. I thought that was weird and figured maybe the app just was not compatible with my device for some odd reason. Next I booted back into TWRP to try and do a nandroid backup. When I did the backup I got the same error, saying I did not have enough space available. I booted back up into the system and unrooted my device through the "permanent unroot" option in SuperSU thinking maybe it did something weird to the filesystem by some chance, booted back into TWRP and still got the same not enough space error trying to do a backup. Can anyone help me out with this issue. I am completely new to the device, I just got it yesterday so there is barely anything on it. Any help would be greatly appreciated. Thanks
It sounds to me like you're out of space... If you go to Settings > Storage how much do you have and what is taking it all up?
xKroniK13x said:
It sounds to me like you're out of space... If you go to Settings > Storage how much do you have and what is taking it all up?
Click to expand...
Click to collapse
I got this phone off eBay so this may be something sketchy but. It says I have 10.33gb total in storage available (purchased 16 gb model) to use with user data. Apps is taking up 3.70gb of that and I have 3.96gb of space free. Is that not enough?
Hi!
!! This is quite serious! I need to get my data (pictures, videos) out of my phone, which is possibly soft-bricked.
I did the following in hope of more usage opportunities with my new phone:
[Unlocked bootloader + Rooted it]
1. installed TWRP following this guide https://forum.xda-developers.com/p10/development/testers-twrp-t3585256;
2. rooted following this guide https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946;
3. installed few apps like greenify, wi-fi hacking apps etc, and everything was good.
BUT then 1 app (don't remember which) requested that it needs SuperSU and not the one root permission app that I had. So it asked whether I want to install it. I thought - yes, why not. Then it said that before it can install SuperSU it needs to uninstall previous permission app - I clicked OK. Then it kind of started, but then failed the installation. Ok, I kind of closed it and there were no problems. But after next restart of the phone it was stuck on boot process..
I dont really care about the phone, but data on it is so important. I tried sme fast hend methrods to boot it, like wiping catch, dalvik catch, but it did not work out.
Next I looked for possobilities to rescue data, but I didn't succeed.
Easiest mentioned option - to enter twrp and connect via usb seemed promising, BUT data are shown encrypted.
Please see the picture - I tried to be as precise as I could, so that you can understand the situation.
! I can beckup all data to micro sd card, but would it decrypt after new install of stock rom (e.g. from eRecovery that Huawei provides) and allow access or not?
Please help me. I am willing to have 1-on-1 skype chat and give some donations for this as it is so important.
To mention: Rescue apps like EaseUS seems to be useless, because they state to recover data from bricked device, but then after installing soft it askes to allow usb-debbuging, but c'mon, it's not booting up.. .
So,
1. Is there a chance to recover data?
2. Is it a good sign that 16GB of data are showing even if files are shown encrypted?
3. data are also showing on pc, when connected on twrp, but also encrypted.
Any help will be appreciated!
Additionally quite important question: at this state (possible soft brick + encrypted files), is there a chance that if I make a backup to MicroSd card of all the data and then take it our to reinstall rooted stock version of my android that later puting backup in will show my files that were backuped? Could ir be so that phone luckiliy decrypt them itself because it is the same phone? Hope this is clear what I mean.
OK, hopefully all is not lost.
First things first, be REALLY careful. If you start applying factory images, wiping things and generally messing about, if you don't know what you're doing you're putting your data in a lot of danger - Huawei devices do things in weird ways, so be super sure you know the consequences of what you're doing.
Now that's out of the way... it sounds like you haven't done anything to wipe the data. Also, you've already previously unlocked the bootloader which should put you in a good situation. You need to discount TWRP as a potential solution - there is no working decryption for TWRP yet on the Kirin 960 devices and from conversations I've had, it doesn't sound like that is imminent.
What it sounds like has happened is that messing about with root has messed up something on your system partition. Which should be fixable!
As a first step, this is what I'd do.
- Check which version your phone is on if you don't know already (you should be able to find this in ' /version/special_cust/VTR-L09/hw/eu/prop/local.prop')
- Find a full dload zip for the appropriate version (use FirmwareFinder if needed)
- Download the zip an extract the dload app
- Use splitupdate to split the images out of the dload
- Boot the device to bootloader ('adb reboot bootloader' or power on with cable connected and volume down pressed) then do 'fastboot flash system SYSTEM.img'
- Flash BOOT.img too
- Try booting
Hopefully this will fix it, but at the very least it'll get your system partition back to a stock state.
Let me know how it goes. Good luck!
P
I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.
I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.
A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.
TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.
What works for me:
OOS 4.1.6
Franco Kernel r25
TWRP 3.1.1-0 (official)
Magisk v13.2
Magisk Manager 5.0.6
No issues whatsoever (for me)...
Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.
I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.
It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.
Will look for solutions to this problem and report back here.
I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
JMB2K said:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
Click to expand...
Click to collapse
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
mobilityguy said:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
Click to expand...
Click to collapse
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember
Problem solved. The more I looked at the symptoms, the more I realized that the OTA I took after unrooting with SuperSU corrupted the system partition somehow. The first time I tried applying the OTA with the stock recovery it failed, but I was able to reboot and apply 4.1.6. That's when the trouble began - I was unable to reapply SuperSU. Fortunately I had done a nandroid backup between the upgrade and the attempt to re-root, and after the SuperSU script failed I was able to restore the backup (made and restored using TWRP 3.0.4-1) and continue working. It was either at that point or earlier, during the OTA itself, that /system was damaged - not badly enough to prevent the phone from working perfectly well, but enough to keep TWRP from mounting /system read/write. From that point on I was doomed. None of my other attempts to fix the problem had a chance as long as TWRP was restricted to mounting /system read-only. Then it got worse.
After a semi-failed attempt to install Magisk (rooted applications worked as long as they didn't try writing to /system) I restored my pre-root 4.1.6 backup one more time. After that, TWRP wouldn't mount /system at all, which prevented me from making any more nandroid backups.
It was time to act. I could keep using the phone unrooted, but the longer I went on the more work would be required to put things completely right. The risk would increase because I couldn't take any more snapshots of the phone to fall back to if I munged the device again. I also had a positive reason to fix things - during the two days the phone was rooted but couldn't access /system, Titanium Backup kicked in and did a full backup of all my software and settings.
With a damaged file system and full backups, there was no reason for halfway measures. I copied all my user data off the phone and used LloydSmallwood's unbrick tool to flash the phone back to its original OOS 3.5.4 state. That took care of rebuilding all file structures. As soon as I rebooted, OOS upgraded to 4.1.6 in one step, taking care of the system upgrade. Unlocked the bootloader, installed TWRP 3.1.1-0 (not 3.1.1-2, which has a serious bug for the 3T as someone posted above). I was able to mount and unmount /system from TWRP's mount screen, no problem. Ran Magisk 13.3 script without a problem, installed Titanium Backup, and tested an app restore. No problem. I'm now in the midst of copying all my stuff back onto the phone, after which I'll restore all missing apps and be back in business (I hope).
It's possible I could have done something tricky like reformatting /system and restoring the partition from my last good nandroid backup. But I always would have been concerned that problems would have popped up later, maybe during the Android O upgrade, when it would be way too late to recover my then-current setup. After seeing virtually every combination of working and non-working features, it just made sense to build from a clean system.
So thanks have been given to LloydSmallwood for his absolutely indispensable unbrick tool (this is the second time it has saved my phone). I should also thank my Galaxy S3, running the current build of LineageOS, which has gotten me through the two days it took to set my OnePlus straight. The Galaxy has performed better than a five year old phone running brand-new software should ever be expected to - if it supported LTE I could consider using it as a daily driver. This has been an education, and a reminder of how important it is to keep good backups at every step throughout an upgrade - and routinely during production use.
Thanks to all who gave advice in this thread.