T-Mobile Galaxy S4 - Resurrection REMIX ROM - Nandroid question - T-Mobile Samsung Galaxy S 4

Hey guys I have an interesting question and it appears that no one has had this questions after 3 days of searching.
As stated I have a Galaxy S4 which only updated up to 4.4.4.
I rooted my phone with SuperSU flashed TWRP made a TWRP backup (Which is a Nandroid backup as I understand it)
Downloaded and installed Resurrection Remix which I totally love by the way.
Took the time to get all the apps I want installed and configured "just right". Even using next launcher.
Did another TWRP backup. Saved it to my laptop external hard drive with step by steps instructions to restore in the future.
Then completely wiped my phone and did a TWRP restore and everything came back perfectly.
On first boot it did not go through the setup process, it booted using next launcher. It did not have to download any apps from google backup, all my screen widgets were there. Opened my chase app and my credentials were already there, opened waze and my home and work addresses were there. Shazam was there and I was already logged into it. You get the picture. This was a successful restore of the actual image.
That was then and this is now.
Had an issue with apps2sd and it totally f'd up my phone and I couldn't even reinstall waze even after all troubleshooting. Last night decided to do a restore. Followed the notes i made to the letter but on 1st boot after restore here is what happened:
Had to go through initial phone setup
all apps were downloaded from google backup (which took forever)
not all apps were downloaded.
next launcher didn't launch, just the default launcher.
widgets were gone
had to re-login into my chase app and it said it didn't recognize my phone (so the cookie it originally put on my phone (and was part of backup) was gone.
You get the idea.
So my question is, why would my 1st restore work perfectly but not the 2nd restore? It doesn't make sense to me and me being an IT guy. Is it an issue with TWRP or the process I went through? Maybe there is one minor (but crucial) step I missed.
Can anyone duplicate my issue?
Totally anxious to hear the results.
Thanks
Mike

Related

[Q] A couple of question before flashing Fresh EVO..

I've decided go give Fresh EVO a try (thanks to all those who recommended it), and have installed ROM Manager to help simplify it as much as possible. But I'd like to ask a few, perhaps noob questions, before I roll with it.
I have the zips for the ROM and the latest Radio/PRI on the sd card, and I think ROM Manager will let me flash both from there (if not, I'd appreciate any thoughts).
I've backed-up the phone, both with AmonRa and ClockworkMod (as well as with Titanium Backup), and copied everything to my PC. Now my primary hesitation is about reinstalling apps, etc. afterward.
1) After I flash the ROM et al, does this give me a basic stock-ish ROM and then I simply reinstall Titanium and reinstall my apps?
2) Do I need to worry about reinstalling data, or any of the various .img files that were backed-up previously? All my contacts and phone numbers, do they come from the 'cloud' when the phone connects to Sprint, or do I have to reload them somehow?
Anything that might be helpful to know, feel free to point it out.
Thanks in advance..
-JTT
1) Yes, all you need is to restore your apps via market OR from TB (if you need to get like your high scores or alarm settings, TB is the way to go)
2) No, once you log on to your google account your contacts, calendar and google email will be sync with your phone. Any other email accounts should be set manually afterwards.
Installed Fresh EVO just now...and good to go.
I'm following up on my earlier post to relay my experience after flashing Fresh EVO and the Radio/PRI that were recommended with it.
Perfect! That about covers it in a short version. Longer explanation below.
I had a stock EVO that was fully rooted but had not been updated to 2.2..see my first post. For all others nervous like I was, I read everything I could and obviously posted a few questions to get a feel for any problems that might arise. I decided to pay for ROM Manager since it seemed highly recommended, and then ran everything from ROM Manager. It worked well for backups, flashing ClockworkMOD and AmonRa recovery back and forth to do the backups. No problems. (Caveat: It would not automatically download the Fresh EVO ROM from the entry in it's list for some reason. I had to move it to my SD card after downloading it to my PC. But no worries there.)
From there it was a breeze. Go to ROM Manager, choose to flash from the SD card, pick the Fresh zip (select to backup the ROM -and- wipe), and let it run. It took a few minutes, rebooted, and came up perfectly. (PS..the boot screen and the audible 'freshhh..' was a nice touch).
Now, you can easily go back to Android Market and download ROM Manager again (and the Premium upgrade, which seems to auto-detect that you had already purchased it..sweet.)
Open ROM Manager and the flash the Radio/PRI zip from the SD card.
I reloaded Titanium Backup (the license, if you bought it, should still be on the SD Card), and selected to reinstall any apps I wanted back.
I've checked my settings, and everything looks pristine. I turned on 4G, Bluetooth, WiFI, and went to settings and looked at the hardware MAC address for each and they all show up fine. 4G turns on fine, but at the moment I live in a 3G only area so will double check it tomorrow when I hit a 4G locale.
All in all, it was absolutely painless, once my nerves settled But for anyone who cares, I highly recommend ROM Manager, Fresh EVO, and Titanium Backup...they made this a smooth process and I'm back in business.
Thanks to all who answered my questions, and all you brilliant developers.
-JTT

[Q] TWRP problem with Copilot & Whatsapp

I made a nandroid backup with TWRP, it backed up fine and restores fine, but 2 of my apps Copilot and Whatsapp don't work properly after the restore, I have to re-verify Whatsapp because it thinks it's on another device, a message says that it can only be installed on 1 device per phone number, and Copilot just tries to start up and then dies, the only way I can fix it is to delete it's sd card folder first, then it opens and has to be set up and maps downloaded again as if it were a new install, so it looks like that also thinks it's on another device.
When restoring I clean/delete everything first, (factory reset/system/cache/dalvik cache), as I have always done, had no problem with doing this on my last phone (Galaxy Nexus), also using TWRP, and with 2 other phones (Galaxy S2 and HTC Desire), both with CWM.
Has anyone else expereienced this ?, I suspect there's other apps out there that will do it as well, it seems to me that the device id is changing, but then Titanium backup would recognize that and offer to restore it, so there must be something else that's either not getting backed up or not getting restored or both.
I was thinking of switching to CWM and trying that but thought I'd ask on here first, because I don't want to switch unless I really have to, so any idea's comments would be much appreciated.
Thanks, Dave.

[Q] My SGS3 stuck in bootloop

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.

[Q] Installed my first rom today (Jedi), went well except for issue with G apps.

So today I installed the latest Jedi rom onto my note 2. This is my first rom install, so excuse me if this is a newbish question. I used Rom Manager to backup, wipe, clear caches, and flash the rom. I let the phone sit for 10 minutes after the install, and when I started using it, data worked and everything. I installed Titanium Backup and restored my apps, and everything went pretty great. I had my old desktop and everything.
The only issue I have is with my google apps. Google+ and messenger will not open. It says no connection, couldn't connect to server. When I hit okay, it asks me to select an account, but upon doing so, the same error just comes up. Gmail works, but curiously, I have to update it manually to see if/when I get new emails, contrary to my settings in the application. Google now appears to work, at least when I load it up, but I don't know if it'd update on its own in the background like it normally does. I also just discovered that I can't install apps from the play store on my PC.
I tried uninstalling google+ with titanium, then reinstalling it in the market, but that didn't work. I also deleted my google account, then re added it and re synced everything, but that didn't fix it either. I tried searching the Jedi thread for "gmail" and a few other things, but didn't find any relevant info.
cjmodiano said:
So today I installed the latest Jedi rom onto my note 2. This is my first rom install, so excuse me if this is a newbish question. I used Rom Manager to backup, wipe, clear caches, and flash the rom. I let the phone sit for 10 minutes after the install, and when I started using it, data worked and everything. I installed Titanium Backup and restored my apps, and everything went pretty great. I had my old desktop and everything.
The only issue I have is with my google apps. Google+ and messenger will not open. It says no connection, couldn't connect to server. When I hit okay, it asks me to select an account, but upon doing so, the same error just comes up. Gmail works, but curiously, I have to update it manually to see if/when I get new emails, contrary to my settings in the application. Google now appears to work, at least when I load it up, but I don't know if it'd update on its own in the background like it normally does. I also just discovered that I can't install apps from the play store on my PC.
I tried uninstalling google+ with titanium, then reinstalling it in the market, but that didn't work. I also deleted my google account, then re added it and re synced everything, but that didn't fix it either. I tried searching the Jedi thread for "gmail" and a few other things, but didn't find any relevant info.
Click to expand...
Click to collapse
When you restored with TIBu did you restore apps and data or??? Did you ensure to follow the exact steps in the post?
Original Tester for Jedi ROM!
Jedi Council
I'd also flash manually...not using ROM Manager. Sounds like you may need to start over and make sure you don't restore any system apps or system data.
johnnywhojr said:
When you restored with TIBu did you restore apps and data or??? Did you ensure to follow the exact steps in the post?
Original Tester for Jedi ROM!
Jedi Council
Click to expand...
Click to collapse
I flashed with rom manager, and I did restore app data when I restored my apps. Is there any way I can clear the particular trouble apps (g apps, and facebook I discovered as well will not give me notifications) and reinstall, or do I have to flash again?
Best thing to do is fresh install everything. I know its a pain in the ass but ive been the original tester of the jedi rom for i317/m and have yet too have any issues. Restoring through tibu does work but making sure to restore apps only.
Original Tester for THIS ROM!
johnnywhojr said:
Best thing to do is fresh install everything. I know its a pain in the ass but ive been the original tester of the jedi rom for i317/m and have yet too have any issues. Restoring through tibu does work but making sure to restore apps only.
Original Tester for THIS ROM!
Click to expand...
Click to collapse
Hmm okay, do you know what it is that I restored that screwed things up? I thought all I restored was apps. I just did one operation along the lines of 'restore all apps and app data'
I think also when I restored, it asked if i wanted to restore the device's ID or something like that, maybe that had something to do with it. It said if I restored the device ID to the original one, it would help with restored apps functioning properly.
cjmodiano said:
Hmm okay, do you know what it is that I restored that screwed things up? I thought all I restored was apps. I just did one operation along the lines of 'restore all apps and app data'
I think also when I restored, it asked if i wanted to restore the device's ID or something like that, maybe that had something to do with it. It said if I restored the device ID to the original one, it would help with restored apps functioning properly.
Click to expand...
Click to collapse
Best thing is start from scratch! Install your apps direct from play. If you follow the directions perfectly, you should have no issues
Original Tester for THIS ROM!

Tab S 8.4 won't boot after having used "Bloatware Melter" in Titanium Backup

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.

Categories

Resources