The following has happened a couple of times:
- Flash latest stock using Nexus Root Toolkit (MMB29Q), then root + TWRP 3.0.0-0
- Run through startup, using the restore feature to get my apps back. Let that run until it's finished
- Enable development menu, set USB debugging
- Use Titanium Backup to restore data for a couple of crucial apps
- Start everything that needs to get started (like Tasker)
- Reboot to recovery, make nandroid
- Start using
Then after a one or two more nandroids, there comes a moment that reboot system gets me in a bootloop in the animation, sometimes getting as far as "Starting apps", but then bootlooping again.
The only thing that helps is restoring the previous nandroid and using Titatium Backup to get my setup back.
The only apps that got root access are AdAway, AFWall+, BetterBatteryStats, Greenify, Material Terminal, Wakelock Detector and Titanium Backup.
I don't mess around with build.props.
I've been doing stuff like this for years now, on multiple phones and the only phone that (in the end) gave me this exact same behaviour was my Nexus 5, but only after two years of faultless behaviour.
Any idea what it might be that always gets me back to bootloops? Anything obvious I'm doing wrong?
Any help would be appreciated, I'd like to avoid going back to unrooted stock and having to watch ads on the web all the time
Bump?
Related
Hi guys. Need some help.
This afternoon my phone began force closing random applications (widget locker, sms stuff, etc). When I got home, I attempted a restore using ROM manager and using my last (and only) saved restore.
Now when the phone attempts to reboot, it just goes back to ClockwordMod Recovery.
I've tried to use the "backup and restore" option in there as well, but aside from it saying sd-ext.img missing at the end of the process, the restore seems to go as planned.
I know this seems general, but I'm kind of at wit's end trying to figure this out.
Thanks in advance.
Fixed. 10 letter minimum.
Hi all, i really need help here. I search through forums but still cant get any solution.
I rooted my s3 earlier today and freezing some stuff using titanium backup. It work fine until suddenly it got restart automatically. After that, i got stuck on the "Samsung" logo. I do not install any custom rom as i'm noob to all these things. I froze those apps and some bloat stuff according to some list i got from the internet.
What i can do to get my phone running back without losing any data? I forgot to back up using clockwork after i root my phone.
Please help!!!!!!
abyss8 said:
Hi all, i really need help here. I search through forums but still cant get any solution.
I rooted my s3 earlier today and freezing some stuff using titanium backup. It work fine until suddenly it got restart automatically. After that, i got stuck on the "Samsung" logo. I do not install any custom rom as i'm noob to all these things. I froze those apps and some bloat stuff according to some list i got from the internet.
What i can do to get my phone running back without losing any data? I forgot to back up using clockwork after i root my phone.
Please help!!!!!!
Click to expand...
Click to collapse
You can still backup now (if you have a custom recovery installed. if you don't, then i think there are some clockworkmod Odin flashables available, no idea where). Then when you erase, and boot up next time, use titanium to open the nandroid backup (because it can do that, as long as you have the full version, which you can just find cracked versions of), and it will add the whole nandroid backup to part of the "backed up list" in titanium. All the data should be preserved too (I don't rememebr if it also takes the cache).
and just a question to devs, is it even possible to cause boot loops by freezing bloat? I have never had such issues. I even froze my browser, the calendar, file manager, clock, and nearly every app in a clean AOSP build (did that for a benchmark once), and it hasn't bootlooped. Think there is something else? Some other factor?
rmanne said:
You can still backup now (if you have a custom recovery installed. if you don't, then i think there are some clockworkmod Odin flashables available, no idea where). Then when you erase, and boot up next time, use titanium to open the nandroid backup (because it can do that, as long as you have the full version, which you can just find cracked versions of), and it will add the whole nandroid backup to part of the "backed up list" in titanium. All the data should be preserved too (I don't rememebr if it also takes the cache).
and just a question to devs, is it even possible to cause boot loops by freezing bloat? I have never had such issues. I even froze my browser, the calendar, file manager, clock, and nearly every app in a clean AOSP build (did that for a benchmark once), and it hasn't bootlooped. Think there is something else? Some other factor?
Click to expand...
Click to collapse
I have never seen or heard freezing bloat to cause boot loops. He froze something he shouldn't have. Try Odin back to stock then re-root or leave stock. Don't do things you don't understand.
It sounds like you froze something you shouldn't have like this poster said. Before freezing in titanium always make a nandroid backup and do a quick Google search to make sure it's safe to freeze.
I posted something similar in the general questions subforum but of course there was no response.
I'm on stock rooted 4.3. If it matters, I ALWAYS get a message about gapps crashing.
Basically, I'm sick of ****Wiz and its continuous bulkiness and slowness. Tried a few ROMs, settled on PacMan. Trouble is there just seems to be NO way to restore my apps.
Titanium is no good because it breaks push notifications for any app that uses them - unacceptable.
The Play Store just refuses to act right. At first it wouldn't restore anything at all, then on one of my million flashes, I started restoring from Titanium one-by-one, then got even MORE frustrated and stopped. Now that list of about six apps is what the Play Store tries to "restore".
I've flashed and Nandroided back so many times because of this. And no matter HOW many times I manually sync, or how long I leave my phone on Wi-Fi to do it itself, when I flash it's those same six apps restoring.
Today I thought to make an update.zip in Titanium before flashing. Flashed the ROM, then Gapps. Tried the update.zip and it wouldn't work. Booted, then tried it. It worked, but didn't "reboot in 5 seconds"... had to battery pull after 10 minutes. Then the apps didn't have data. Titanium restored them and recommended a reboot. When I did that, the menu button no longer worked. At all.
I'm really ****ing sick of this. What am I supposed to do? If I have to stay on TouchWiz I'm getting rid of this phone. It's counterproductive at this point.
Are the custom ROMs based on the stock Samsung kernel? If not, that may be why your apps are crashing after being restored.
audit13 said:
Are the custom ROMs based on the stock Samsung kernel? If not, that may be why your apps are crashing after being restored.
Click to expand...
Click to collapse
Well, they're not crashing. When I restore them with Titanium, everything works fine about them except push notifications and that just can't happen.
And the ROM I've chosen for now is PacMan. I don't think it is?
Hello everyone,
I was a noob when it came to rooting/custom rom flashing etc. and I always avoided doing it for my note 2. With the help of XDA and so many helpful threads, I was able to learn it easily(thanks to the contributing members). However, I am facing a bit of a problem with the restoration with the help of TWRP.
Initially, when I restored while using the stock 4.4.2 kitkat with root, it worked like a charm. After that I flashed CM-13 ROM made by Ivan. I was also able to recover app data for the google play signed in apps via wi-fi. I tried to restore after the new installation and there was no problem with the custom recovery, however when I booted up the phone, half my apps went missing and I was getting constant pop-ups that apps like settings, supersu, update have stopped working. I tried restoring again, but now I am not geting any display but just a greyish screen and the pop-ups just like before stating that the apps have stopped working.
Am I missing something? Do I need to do something else?
Thank you.
Hello and good evening,
you can't restore just data. Your device will miss some files in system partition and apps like SetupWizard will keep stopping.
The only thing, you can so is restoring the whole Backup.
The next time I suggest you to backup only Apps with Titanium-Backup and restore them after installing.
Kind regards
Trafalgar Square
Trafalgar Square said:
Hello and good evening,
you can't restore just data. Your device will miss some files in system partition and apps like SetupWizard will keep stopping.
The only thing, you can so is restoring the whole Backup.
The next time I suggest you to backup only Apps with Titanium-Backup and restore them after installing.
Kind regards
Trafalgar Square
Click to expand...
Click to collapse
Yes, I restored the whole thing, that is the whole backup which was generated by TWRP on my my sd-card. And then I am getting these pop-ups and a greyish screen on my phone. Only the options generated by holding the power button-i.e. power off, restart etc. is getting displayed after holding it. I can't see anything else.
Tab S 8.4 won't boot after having used "Bloatware Melter" in Titanium Backup
Hey everybody,
So yesterday I finally took my time to install the Android 6.0 official release by Samsung on my Galaxy Tab S 8.4.
Got the Image from a mirror found here on XDA, but I just can't manage to find the Thread right now...
It's basically the same image that Samsung rolled out for the Nordic Countrys, found on Sammobile for the SM-T705.
Anyway, so I was just about debloating my tab from all the google nonsense with Titanium Backup.
Froze all the unwanted Packages to see if I hit one too many, and in the end I made a Batch uninstall with Titanium Backup. All of these pesky Apps (the system ones) remained right where they were too, which was odd enough already. So I decided to go ahead and kill them off with the "Bloatware Melter" Function.
Selected all of the apps, put them in a filter, started the Action, which then told me to reboot my Tab for the changes to become active. But it never did.
The Bootloader partition is still working, but I can't boot into the system. I can tell the Bootloader is okay, because I can boot to download mode, the recovery and to the system. But whenever I boot to system the Initial Boot Logo turns off (the one you see first, no matter how you boot) and the screen goes black. Left it lying there for about 10 minutes, no reaction. Went into recovery, cleared the Cache, Dalvik and Internal Data (without /data/media) but that didn't have any effect.
I upgraded directly from 5.0.2, my Tab is and was rooted and I had Xposed installed. I'm using TWRP 3.0.0-0. But It did boot into Android the first few times, so it seems like the Bloatware Melter is the actual problem. Does anyone have an idea what may have caused this? Because else I'm just gonna go ahead and do it all again from scratch I guess...
Thanks in advance.
Ho yeah time to wipe and start again. This time, after flashing the stock rom, install TWRP with odin, then supersu and the debloating can begin. Don't use titanium, it doesn't work too well with a change from LP to MM6. There are tons of file managers and de-bloaters, once you're rooted.
First of all, thanks for the reply.
Yeah, semms like it. I was messing around with my Tab the last few days trying to figure out what actually caused the system to fail while booting. Seems like the pre installed Dictionary App is the villain. Which is kinda odd, since i really never use it, and why would something like that cause my system to freeze anyway?
To see if this actually was the cause I uninstalled the Dictionary App on my Samsung Galaxy S5 too (again with Titanium Backup, just as before) which then froze on boot as well. So, lesson learned: Freeze the Dictionary, don't remove it.
For now at least, until I find a reasonable app to go with in terms of debloating. I'll have a look into this problem in the next few days again, for now I'm pleased with Marshmallow.
Thanks for the tip.