Related
I have rooted my Vibrant but when i try to back up my apps, titanium back fc's anyone else having this issue?
Yes i'm having the same problem also...wonder if there's a possible fix for this.
Can anyone else confirm that titanium backup is not working?
I sent the developer my logcat. hopefully he can resolve this issue...
I am also having force close issues. Can usually restore an app or two then it force closes on me.
Broken for me too.
Sent from my SGH-T959 using XDA App
I was able to do a backup, but the odd thing is none of my apps showed up at all. Just system settings. But no FC's.
would one of you take a logcat and post it. I will then proceed to send to the developer to see if we can get this fixed.
i have been working w/ the dev, i can confirm this is fixed and i assume there will be an update soon.
EDIT: attached the patched 3.3.0 version.
Awesome news, I had the same problems!
Hi everyone,
I don't own a Samsung phone so thanks a lot for your help in solving this.
The bug-fixed version 3.3.1 is released on the Market, and backups should work fine now.
I'll be adding more Samsung love in the future
Have a great Sunday !
It now works but it still wont detect my user apps after the update.
I never had fc's, but Titanium hasn't been able to back up my apps. I'm assuming it isn't looking in the right place for them, but not sure if there is an option to change that.
Sent from my Vibrant using XDA App
Bschwartz40 said:
It now works but it still wont detect my user apps after the update.
Click to expand...
Click to collapse
I am no longer having any issues after update, i just tried a batch->backup user apps. and worked without a problem
T.I backup is awesome and Joel is great on support!
Can't wait for my Vibrant to get here!!
Ok I got it working, forgot about updating Busybox. App works great now! Thank you Joel!
hpz937 said:
I have rooted my Vibrant but when i try to back up my apps, titanium back fc's anyone else having this issue?
Click to expand...
Click to collapse
Wow... I installed the Modaco Froyo r5 with a2sd+, but right after installing it, it sends my Desire in a continuous boot loop. WTF!
Anyone else have this issue? I´m installing Titanium backup v3.2.1
all my apps and backups showed up but i cant manage to restore anything. it just kinda sits there. anyone figure out how to get things going? i used the apps busybox didnt help at all.
smellyfungus said:
all my apps and backups showed up but i cant manage to restore anything. it just kinda sits there. anyone figure out how to get things going? i used the apps busybox didnt help at all.
Click to expand...
Click to collapse
I do not have that issue. however depending on the size of the apps being installed it can take a bit of time to install. Does it say it is restoring or anything or nothing at all?
hpz937 said:
I do not have that issue. however depending on the size of the apps being installed it can take a bit of time to install. Does it say it is restoring or anything or nothing at all?
Click to expand...
Click to collapse
it just sits there at 0% on whatever app is first. if i close it out that first app manages to install but without data. the one time i did leave it on for around 10 mins it managed to install two apps.
is there any special thing i need to do before i do a restore?
note these apps are from chromatic 3.7 w/ my g1
edit: just tried new setting under restoration, although its not as fast as doing it on my g1 I managed to get things restored
I am slo having an issue where Titanium says its restoring, but just sits there doing nothing. SOmehow Ive managed to get it to restore once, but I had to wipe and now I cant get it to restore for the life of me. Tried w/ original busybox and the one that downloads inside titanium, both w/o success. Seems that titanium has some sort of issue w/ the Galaxy S.
Has anyone found a solution that allows you to restore your apps? Thanks!
EDIT: Whats really strange is if I try to hide titanium, relaunch it, and try and backup. It gives the message "backup already in progress" but for whatever reason it moves onto the next app...so strange
I was on 4.2.1, rooted, and with TWRP as recovery.
I wanted to get the OTA to 4.2.2 so I did full Titanium backup and then used the WugFresh toolkit to flash stock 4.2.1.
After flashing, I was offered the OTA which I allowed to install.
When finished, I got root back with Rootkeeper and restored all Apps and Data (not System data) with Titanium.
Everything was working, but on every reboot I got the message :
"System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I also found that My Phone Explorer would no longer connect via USB so I decided to go back to 4.2.1.
I again flashed it with the toolkit and did another restore with Titanium. Again, everything seems to be working, but I still get this message on every boot.
I thought using Titanium Backup was a standard way of restoring apps and data.
How do I get rid of this message without wiping and reinstalling all my Apps individually, which means losing all my game scores, etc?
I also see that in Bootloader there is a line
"Signing - not defined yet".
I do not know if that was there before flashing back to stock.
same problem
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
windwhisper said:
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
Click to expand...
Click to collapse
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
windwhisper said:
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
Click to expand...
Click to collapse
You can boot any recovery you want without hard-flashing it to the device (so long as the boot loader is unlocked).
With the device in bootloader/fastboot mode,
Code:
fastboot boot name-of-recovery-image-file.img
So download TWRP and give it a roll.
Hello,
I got the same "System UIDs Inconsistent" problem. I like to solve my problems myself but I've got no way out this time, so I'm asking for your kind help.
I'm on the SGS III, i9300, I rooted it then went to Omega ROM, and then to Paranoid Android. Everything went well until I got a battery problem (when charging the phone, it was not sufficient to bear with it functionning, so it powered out while charging). After that, the phone restarted and the UID problem appeared. Maybe it's just a coincidence.
So far, I : fixed permissions, did at least 10 factory resets with TWRP, changed ROM (went to CM and came back to PA as nothing changed).
I read the 6 first post about this in xda forum, and other forums too, but nothing came out as an evidence.
Last thing I did was upgrade my PA ROM : the phone couldn't even go beyond the booting process, failed to initiate the phone "first settings" app.
So I came back to the previous version of PA, and was able to use my phone again, but apps like Gmail, Color Note, won't work.
I want to get rid of that, and I wish someone told me, step by step, the things I could do to eradicate the problem. I will do what's necessary to achieve that, I only need someone who knows what to do, and how to do it. I saw some tricks that maybe could do the job but I don't have the knowledge to choose one.
That's my first message here so I hope I didn't break the rules of the forum ^^ If you want any informations about my device to help me, just ask
Thanks a lot, and I hope my english is not too bad ! Have a good day.
Thanks
I got this message too without having any other problem with this TWRP version or Hairy Bean 2.2
The message appeared after flashing the new 4.2.1 (?) modded bootloader for Hairy Bean and the ROM itself.
I'm not sure whether the ROM or bootloader are causing it but mine got fixed by fixing the permissions via TWRP.
Thanks for the tip! :good:
In my case only re-partitioning helped.
for me uninstalling quadrant did the trick
That did it
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
Quick and easy. Worked for me. Thanks
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
This worked for me, too. Thank you.
My situation was a little bit different:
- Flashed Paranoid Android 3.99
- everything was fine (for a few reboots) until I made a nandroid back up with CWM 6.0.3.6 ( which was surprisingly slow, almost 1,5h)
- rebooted
- UID consistency problem
- tried to boot temporary into TWRP - NOT POSSIBLE!
- flashed TWRP 2.6.0.0 permanently
- TWRP: advanced - fix permissions: SUCCESSFUL!
Maybe I'll keep TWRP, but I'm used to CWM for years now.
CWM has removed "fix permissions" since 6.0.3.5 (http://review.cyanogenmod.org/#/c/45945/ )
Fix Permissions
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
edbertin said:
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
Click to expand...
Click to collapse
Me too! TWRP on SlimRom 4.3
Thanks
I am also having this issue after I flashed SlimBean Beta 4 Weekly-409 on my i9300 (wipe data/cache/dalvik and clean install with gapps) and tried restoring a couple of apps like Any do and Temple Run 2 with Titanium Backup.
Is the TWRP being referred here mean the TWRP manager? I installed it from play store but I don't find 'fix permissions' option anywhere in it.
I remember of seeing it in SuperSU but I am unable to install that as well as it says the binary needs to updated.
Could someone please help me here?
Thanks!
--IH
Confirmed. Get into the TWRP n do a fix cache wipe/dalvik wipe/fix permission
Thank you for clarifying this fix
polarfrz said:
Quick and easy. Worked for me. Thanks
Click to expand...
Click to collapse
I just updated my S4 to 10.1 Hyperdrive and experienced this very same issue. Rebooting into safestrap and fixing permissions cleared up this very annoying issue on my phone.
I flashed gummy V4.4 yesterday works great. I went into rom toolbox and changed LCD density to 361 and rebooted, got the UID inconsistent message.
found this thread, fix permissions in TWRP, all fixed. bing bang boom.
thanks all, I also fixed with TWRP latest version, and try to roll back to CWM
I installed a new ROM and I got the System UIDs inconsistent error, then my S Planner FC. I went to find the txt file and it stated that the problem is related to Calendar Storage. I deleted the apk and placed a new one back in. Problem persists, I scratched my head for so long and then I found this thread.
THANK YOU, fixing permission for the Calendar Storage did the trick! Thank God I found this thread!
Hi guys,
Not sure wtf is going on here but just updated to I9505XXUBMEA and now I cant root! have tried via cwm more times that I care to mention! I also notice the phone is VERY slow, even when I run root checker it comes up with a warning that UI is running very slow.
Anyway I am booting into recovery and selecting install from sdcard and then selecting CWM-SuperSU-v0.99.zip. CWM reports all installed fine, yet when I reboot it's not installed, if I try any type of app that checks root the phone seems to go to almost a stop or just crashes, any ideas?
Its a I9505 BTW
germinus said:
Hi guys,
Not sure wtf is going on here but just updated to I9505XXUBMEA and now I cant root! have tried via cwm more times that I care to mention! I also notice the phone is VERY slow, even when I run root checker it comes up with a warning that UI is running very slow.
Anyway I am booting into recovery and selecting install from sdcard and then selecting CWM-SuperSU-v0.99.zip. CWM reports all installed fine, yet when I reboot it's not installed, if I try any type of app that checks root the phone seems to go to almost a stop or just crashes, any ideas?
Its a I9505 BTW
Click to expand...
Click to collapse
Hi,
You could try flashing a pre-rooted ROM.
Look HERE
It sounds like you should do a factory reset to clear your phone first.
yes I really wanted to avoid moving from stock but looks like I might not have a choice which is a shame
germinus said:
yes I really wanted to avoid moving from stock but looks like I might not have a choice which is a shame
Click to expand...
Click to collapse
Hi,
The ROM I suggested is pure stock.
Or there is a slimmed down version with some bloat removed.
But they are all fully functional,with all the Samsung goodies.
Yes thanks I am downloading that and also Omega rom aswell, many thanks:good:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
saison said:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
Click to expand...
Click to collapse
I'm not ENTIRELY sure, but from what I've heard 4.3 causes a lot of problems with root and only one superuser app even works. I'm not sure which one, but it's possible you're using a superuser apk that doesn't work on 4.3.
Try going to Developer Mode > Root Access and change it to Apps and ADB.
IDK about the rest but SuperSU works fine on stock 4.3
thanks, will try this stuff out
moffa~ said:
Try going to Developer Mode > Root Access and change it to Apps and ADB.
Click to expand...
Click to collapse
Does not appear to be a Root Access option.
3rdstring said:
IDK about the rest but SuperSU works fine on stock 4.3
Click to expand...
Click to collapse
OK, I've got that copied into the 'sdcard', but should I remove the old superuser app before installing this one? Not sure how to do it, as it won't delete from the apps menu, it will only give me the option to disable.
saison said:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
Click to expand...
Click to collapse
If you're on a JWR (Stock) ROM, flash this: http://d-h.st/sDt
If you're on a JSS (AOSP) one, flash this: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Good luck!
Tanmaynarang said:
If you're on a JWR (Stock) ROM, flash this: http://d-h.st/sDt
If you're on a JSS (AOSP) one, flash this: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Good luck!
Click to expand...
Click to collapse
Managed to get it with SuperSU 1.51 as mentioned above. Although I had to do it twice, lol. After flashing and rebooting, I started Titanium, and SU asked if i should grant permission. While thinking about this, the window timed out, and Titanium would not work, nor did the sytem appear rooted, until I reflashed SuperSU and started again. This time, I granted permission for Titanium, and all's well. For now. I guess.:silly:
Yeah for some reason Superuser and 4.3 don't mix very well. SuperSU works fine though, I had to flash it too to get PA 3.92 to work properly. I was really worried that I'd lost all my data since Titanium wasn't working and my CWM backup had failed but ultimately it all worked out.
I have always rooted and used Titanium Backup to set up a new phone but this time I want to leave it alone, more and more apps are checking for root and certified/uncertified, last week I could not even get a PizzaExpress app because it needs 6.0+ & unrooted (had to unroot my old S2 on Lineage), I have decided I want my banking apps back and other things I lost over the years, so no root or customising (yet! hehe).
With that in mind what is the best way to restore, obviously Google will take care of a lot of it but things like call logs, sms, bluetooth, some app data, in the past I would selectively use Titanium to restore anything I found missing but without root, what to use? Helium, mi mover or something else.
My S4 is rooted but stock right now so calls, SMS, rejection lists even wallpaper is synced with Samsung, I guess there will be no way to access these backups from the A1
You can root via Magisk. It doesn't break the SafetyNet. Moreover, you can hide it from certain apps. All the banking apps work if you root via Magisk.
Edit: Here's the link to the thread: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
darkpegasus said:
You can root via Magisk. It doesn't break the SafetyNet. Moreover, you can hide it from certain apps. All the banking apps work if you root via Magisk.
Edit: Here's the link to the thread: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Click to expand...
Click to collapse
I did see that and did think about it, it's been a bit cat and mouse hiding root for years now and I can only see it getting worse as android secuity ramps up, I thought I would keep this phone clean as long as I could resist
I might go with the root, I could always remove it again I guess.
You will not resist for a long time, you know that, all of us know that
I bought this phone today online and expect to receive it within days and I was thinking exactly like you, then log on to XDA 10 minutes ago searching for rooting threads to be ready when I receive it
darkpegasus said:
You can root via Magisk. It doesn't break the SafetyNet. Moreover, you can hide it from certain apps. All the banking apps work if you root via Magisk.
Edit: Here's the link to the thread: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Click to expand...
Click to collapse
When it arrives, it should come on N, so I guess I could root it with Magisk, get it up and running how I like it then restore the boot image, remove Magisk and allow the O OTA and everything will be 100% stock again?
kudos1uk said:
EDIT: When it arrives, it should come on N, so I guess I could root it with Magisk, get it up and running how I like it then restore the boot image, remove Magisk and allow the O OTA and everything will be 100% stock again?
Click to expand...
Click to collapse
Yup. Magisk does not touch system files. It will be 100% stock without any issues.
2363 said:
You will not resist for a long time, you know that, all of us know that
I bought this phone today online and expect to receive it within days and I was thinking exactly like you, then log on to XDA 10 minutes ago searching for rooting threads to be ready when I receive it
Click to expand...
Click to collapse
You are right there lol
I am starting to think we are beginning to lose more than we gain, I comes to something when a stupid pizza shop app checks for root!
darkpegasus said:
Yup. Magisk does not touch system files. It will be 100% stock without any issues.
Click to expand...
Click to collapse
Thinking about this and reading the thread, does Titanium not need Busybox installed? busybox installs to "system" and would stop OTA?
kudos1uk said:
Thinking about this and reading the thread, does Titanium not need Busybox installed? busybox installs to "system" and would stop OTA?
Click to expand...
Click to collapse
I just installed Titanium Backup without installing busybox and it works. (Busybox maybe included in the custom ROM I've installed, I dunno).
I think you are being unnecessarily cautious about Root. Almost all the banking apps work even when Magisk is installed. You can enjoy root without worrying about the safetynet.
darkpegasus said:
I just installed Titanium Backup without installing busybox and it works. (Busybox maybe included in the custom ROM I've installed, I dunno).
I think you are being unnecessarily cautious about Root. Almost all the banking apps work even when Magisk is installed. You can enjoy root without worrying about the safetynet.
Click to expand...
Click to collapse
Thanks for that.
I'm comfortable with root now after loads of reading of that thread but was just being cautious no to allow any app to change the system folder once root is running.
I also see this method of root cant be used on N so my idea of rooting / restoring / unrooting and upgrading to O will not work so I will just upgrade to Oreo / root / restore and then decide if I want to keep root or not.
kudos1uk said:
Thanks for that.
I'm comfortable with root now after loads of reading of that thread but was just being cautious no to allow any app to change the system folder once root is running.
I also see this method of root cant be used on N so my idea of rooting / restoring / unrooting and upgrading to O will not work so I will just upgrade to Oreo / root / restore and then decide if I want to keep root or not.
Click to expand...
Click to collapse
Yup, you can upgrade to Oreo, root, and restore.
Also, if there are any issues afterwards, you can always flash the official fastboot ROM by MiFlash Tool without wiping your internal storage.
IjazCI said:
Hi there, you could root with magisk , restore your data then flash stock rom through mi flash tool . Make sure to select the "save user data " option before flash. This way you will be 100 % stock and take ota's.
I suggest you to enable the camera 2 api using set prop method by flex1911 ( the one which doesn't uses magisk) before flashing stock rom.
Cheers
Edit : my advice is literally Same from the guy above. Didn't see that. . Saw your post , think that i can help and replayed
Click to expand...
Click to collapse
Thanks, I think I will just have to devote a good long time to this, at least I will have both phones side by side so I can keep trying all the restore methods known