[Q] Titanium backup not restoring on stock - Galaxy S III Q&A, Help & Troubleshooting

I am on SGS3 int i9300 stock rom from sammobile, RECENTLY flashed and rooted it with CF auto root.
All root apps, except Titanium backup, are able to get root access.
For some mysterious reason, Tit backup cannot get root access.
I tried reflashing 2 times again, following the same procedure of philz recovery phone wipe, rom flash, and cf auto root.
No luck. Rebooted countless times.
What do I do?
EDIT: Sometime back, like for 5 minutes, it worked fine, but again on app restart, it failed to get root access.
EDIT 2: Now it is back in business! at 6 46 pm IST.
Now I know it is not a prob with the flashing or rooting part.

Related

[Q] Phone freezes 10 secs after reboot following rooting and installation of ROM-Mana

I'm using a Samsung Galaxy S3 GT-I9300, Baseband I9300XXLH1 running Android 4.04, Build IMM76D.I9300XXBLG8
I used Samsung Galaxy S3 ToolKit to root the phone, choosing Build BLG9 and choosing Rooting Option 3.
Everything went fine and I used my phone for a week like this, before deciding to investigate custom ROMs.
I installed ROMManger through Google Play, but got no futher than this - I then switched my phone off.
On restart, the phone lasted 10 secs before it froze - I rebooted many times, but every time it froze after the same period of time.
I attempted to use ApplicationManager to uninstall ROMManager, but this was unsuccessful.
I then rebooted into CWM, backed up the phone and then wiped it (wipe data/factory reset) - rebooting resulted in a working phone, allbeit with all my data/apps gone.
I can restore the phone using KIES but I hadn't backed up since before rooting so this backup is out of date (doh!).
Restoring through CWM resulted in the original problem returning.
1) Is there a way to perform a partial restore the phone without the ROMManager app through CWM as I suspect it is this (the last added application) which is causing the problem. If not, then I'll just manually rebuild it.
2) What state is my phone currently in - I'm assuming it's still rooted and has CWM and Busybox installed. The wipe didn't erase all data though, folders created my apps still exist in my root, e.g. chessbase, deezer. If I wanted to go right back to a completely clean factory build, what would I have to do?
3) What is the difference between rooting and installing a custom ROM - doesn't rooting involve flashing an insecure ROM? Are they different kind of ROMs?
4) I've heard I need to backup my EFS folder (which I can do through the toolkit) prior to flashing any custom ROMS. Should I have backed up something prior to rooting (other than the standard backup through KIES which I did)?
Apologies for all these questions - I'm completely new to android, although I do have a programming background.
3) What is the difference between rooting
Rooting is gaining system access only
I know zero about your method used to root .
But do know that Rom Manager is not compatible with CF Root .
) I've heard I need to backup my EFS folder (which I can do through the toolkit) prior to flashing any custom ROMS. Should I have backed up something prior to rooting (other than the standard backup through KIES which I did)?
EFS folder .
jje

[Q] Reboot returns me to stock recovery

Hey there, I'm trying to root my S3 and a first step I wanted to make a nandroid backup, so i downloaded Odin and I used it to install recovery-clockwork-touch-6.0.1.0-i9300 onto my device, i rebooted into the recovery screen and I found myself in the stock recovery menu.
So i tried it once more, to no change in my situation, so I looked through the forums for a while and I found a thread by mskip about installing CWM and thankfully it had this
Stock Recovery being reflashed after a reboot?
There is an auto recovery restore system on stock roms that will reflash the Stock Recovery on a Stock Rom. If the restore files are renamed then CWM Recovery should not be overwritten after a reboot.
You need to be rooted and then delete or rename the following files:
Quote:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
You can then flash recovery without it being overwritten.
You can also do all this through the S3 ToolKit
**All credit goes to to Koush and anyone else responsible for ClockworkMod**
Click to expand...
Click to collapse
My problem being that I can't rename said files bacause my phone isn't rooted and the S3 toolkit requires rooting to do backups and such, and I can't root it because (unless I misunderstood) I need CWM installed.
So my question is : What can I do now? Can I root my phone in any other way ? Is there a way to get past this Stock recovery screen onto CWM?
Already thanks for reading and sorry for it being this long
Also I have a Samsung Galaxy S3 GT-I9300 I have Android 4.1.1 And I run Windows 7 on my PC
Ok, so I looked around a bit and I just rooted it without a backup, it seemed safe enough.
Root went well, I backed up right after just in case.
Use cf root and flash via Odin that will give you root and flash cwm. Then you can continue with your nandroid backup. All though you can do the full root procedure using that toolkit, its one of the options. Hope I could help
Sent From My Omega'd Galaxy S3 ...

[Q] Was rooted, now it's not

(SOLVED)
Hey guys, first time root here. HTC One AT&T 32gb
I was succesfully through the process, used a guide on htconeroot.com to go through all of the steps. Everything went just as expected and I had root access through superSU (was able to install and use root apps, such as Titanium Backup and AdFree). I used Root Manager to flash Clockworkmod because I saw a ROM I'd like to use in the future that only supported that custom recovery. After succesfully flashing that, I then made a backup using Root Manager. Everything was successful and expected, but upon reboot into my stock ROM from the original unrooted phone I had apparently lost SU binaries and root access. Also, ROM Manager (v5.5.3.0) cannot find any backups.
I tried reflashing superSU from the original rooting guide (UPDATE-SuperSU-v1.65.zip), and while it was successfully rooted, I still did not gain root access. I had read through some forums that using the stock ROM that came with the phone might lose root because of the stock recovery, but not sure if that is what happened. I have not installed a custom ROM on this phone yet.
Any help would be appreciated.
UPDATE: Solved, had to select "No" when rebooting from CWM on stock recovery option

[Q] Phone unrooted and I can't get it to root again

My phone unrooted and for the life of me I can't get it rooted again. I'm using the Omnirom nightlies on a Galaxy S3 GTI-9300 (4.4.4 KitKat). A couple days ago it started popping up some errors on boot (First error was something about Keyguard and then the next were about android.system crashing, every time I clicked OK the same error would reappear not letting me do anything on the device), so I went into recovery and installed the newest Omnirom nightly. It fixed the problem but I lost supersu and root access, so I tried recovery again and reflashed supersu, the mod, gapps and root still didn't take even though all flashes were supposedly successful. I also downloaded the .tar file from here galax ys3root. com/cwmtwrp-recovery/ and flashed it with Odin and even though it said it did it successfully the phone is still not rooted. After the .tar I retried flashing supersu from recovery but still no root. Oh and idk if this is relevant because it did it before I lost root access, but whenever I flash supersu with CWM it says I might have lost root access and asks if I want it to try and fix it, giving me No/Yes options. I've tried both but they don't seem to affect anything. I didn't try factory restore because I have apps with valuable data that I don't want to lose until I can back them up, but Titanium won't do it without root access.
Framework is corrupt, full wipe and reflash firmware. Use a nandroid to restore your app data with titanium.
boomboomer said:
Framework is corrupt, full wipe and reflash firmware. Use a nandroid to restore your app data with titanium.
Click to expand...
Click to collapse
Restoring it isn't the problem though, getting it backed is. My current backup isn't up to date and I can't make a new one without root
Nandroid happens in recovery.

Can't fix root. Do I need to flash recovery again?

So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.

Categories

Resources