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
Related
Tried ROM Manager backup of factory ROM.
Now, I power on and get CWM recovery. Choosing reboot always returns me
to CWM recov. I read every thread in this forum that refers to
loop, brick, etc. I have various backups, but I don't know what they
are worth, best way to use them. How to get out of the boot loop?
Best outcome would be to recover my last stable state. Factory reset
would be ok. Hardbrick would be a drag.
* Bought factory unlocked G-ST6500D (no vendor) in Spain.
* Have current non-root backups of contacts, sms, media, calendar, etc. on
laptop.
* Installed CWM v5.0.2.8 with Odin (three yellow boxes appeared in odin,
FWIW), and rooted. Froze bloatware listed by some people as safe, but
did not delete any factory installed software.
* Wanted to have a stock ROM backup before I did anything else. It's
not clear to me whether it is best/possible to download one or create
an image from my device. Started reading/trying backup apps, but I
don't really know what each one does.
* Did a full backup, apps + data, to extSD, and copy to laptop with Titanium
backup (free). This wrote >1000 files.
* Did most complete (as best I could tell) backup to extSD and laptop
with Online Nandroid app. This wrote boot.img, cache.ext4.tar,
data.ext4.tar, nandroid.md5, recovery.img, system.ext4.tar. Can these
be used to restore ?
* Tried to backup the ROM with ROM Manager app, but could not find an
option to backup to ext SD, only int SD. There was only 200MB free, so
I knew this would fail. I choose this anyway, hoping it would realize
there is not enough space and offer to change the path. The phone
rebooted into CWM and began a backup. After a few minutes, it printed
an error message and told me where a log was written, and rebooted
into CWM recovery. I tried rebooting, holding buttons, removing
battery, etc. Always returns to CWM recovery. Tried the 'backup and
restore' menu hoping it would give info on the backup. Instead, it
immediately started another backup, this time showing 1GB intSD
free. This backup reported success, then reboot into CWM recov.
* Since then, from CWM, I did 'wipe cache partition' and 'wipe davlik
cache'. Did not yet try factory reset.
* Show log ends with
"skipping exectuion of extendedcommand, file not found"
I read that sometimes it is possible to exit a boot loop without
flashing anything. If that is not possible, I guess I should do
factory reset. If that does not work, then I guess I should try
restoring something somehow: Use CWM recovery to recover nandroid
backup from extSD? Or install something via Odin ? For any solutions,
I am more comfortable doing things from linux than MSWin, but I think
that is not possible. Do I have to race to solve this before the
battery runs out?
Thank you for reading.
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
midzan21 said:
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
Click to expand...
Click to collapse
Thanks. I just figured that out after a several hours of reading. Finally saw stories on the thread
introducing CWM 6.0.3.3 of people who never flashed a ROM and still had boot loops.
I was on the wrong track because I assumed it was the filled up int. SD causing the
problem. I still have to fix that, but my phone is running. It would be nice if ROM Manager or CWM calculated the space
needed and refused to start if insufficient. But, I understand that there are few good devs and much to do.
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.
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?
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.
So I rooted (or tried to anyway) my Note 4 for the first time (Knox was 0x0 before today). Here's what I did:
1. Downloaded twrp-3.2.3-0-trlte.img.tar directly from twrp.me.
2. Flashed it with Odin.
3. Rebooted into TWRP, no problems.
4. Rebooted into system, no problems.
5. Rebooted into recovery again, and for some reason, TWRP was gone. Seemed like booting into system overwrote TWRP with stock recovery??
6. Reflashed TWRP, booted into it, no problems.
7. Downloaded UPDATE-SuperSU-v2.37.zip from http://downloadandroidrom.com/file/tools/SuperSU/UPDATE-SuperSU-v2.37.zip
8. Flashed it with TWRP.
9. Reboot into system - doesn't get past "Galaxy Note 4 powered by Android" screen.
Here's the thing, I do NOT want to wipe and reflash ROM. My kids use this app called Tik Tok (formerly known as Musical.ly) where they make cute music videos. The app stores their creations god-knows-where in the phone's internal storage, and it is a major PITA to get them off. So naturally the phone fills up pretty quickly. This is the main reason I rooted the phone, so I would be able to more easily copy these videos to my PC and free up internal storage. If I do a wipe, they'll all be gone.
I am still able to boot into TWRP, and in fact I did so and did a backup of /data. However, TWRP reminds me that it doesn't back up stuff in the phone's "internal storage" so idk if I have the videos in the backup or not.
Suggestions greatly appreciated. There may even be a bounty if someone can help me save my data.
Oh FWIW it's a Tmo SM-N910T and is running 6.0.1 (latest OTA update from about a year ago)
Update: I used osm0sis's unSU script
https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Saved my bacon! I'm going to send him a few bucks.
kydar said:
So I rooted (or tried to anyway) my Note 4 for the first time (Knox was 0x0 before today). Here's what I did:
1. Downloaded twrp-3.2.3-0-trlte.img.tar directly from twrp.me.
2. Flashed it with Odin.
3. Rebooted into TWRP, no problems.
4. Rebooted into system, no problems.
5. Rebooted into recovery again, and for some reason, TWRP was gone. Seemed like booting into system overwrote TWRP with stock recovery??
6. Reflashed TWRP, booted into it, no problems.
7. Downloaded UPDATE-SuperSU-v2.37.zip from http://downloadandroidrom.com/file/tools/SuperSU/UPDATE-SuperSU-v2.37.zip
8. Flashed it with TWRP.
9. Reboot into system - doesn't get past "Galaxy Note 4 powered by Android" screen.
Here's the thing, I do NOT want to wipe and reflash ROM. My kids use this app called Tik Tok (formerly known as Musical.ly) where they make cute music videos. The app stores their creations god-knows-where in the phone's internal storage, and it is a major PITA to get them off. So naturally the phone fills up pretty quickly. This is the main reason I rooted the phone, so I would be able to more easily copy these videos to my PC and free up internal storage. If I do a wipe, they'll all be gone.
I am still able to boot into TWRP, and in fact I did so and did a backup of /data. However, TWRP reminds me that it doesn't back up stuff in the phone's "internal storage" so idk if I have the videos in the backup or not.
Suggestions greatly appreciated. There may even be a bounty if someone can help me save my data.
Click to expand...
Click to collapse
...... you can wipe it just don't wipe internal storage
As I mentioned, unSU solved my problem. Thanks for your input though.