Hi,
I have upgraded my MZ604 to Team EOS latest stable ROM (EOS 3 JB).
Everything went fine since I have followed the instructions posted in this forum, like making a nandroid backup (just in case) and backing up my apps with CWM.
I have also done a factory reset and cleaned the Dalvik's cache.
The new ROM is really fast!!! Thanks to team EOS.
The problem started when I tried to recover my apps.
When I tried to reinstall them with TIB, it freezed.
I tried many times with different options and none of them worked.
Finally I reinstalled everything from the market, and my tablet is up and running again.
Since I intend to try the nitgly versions from now on, I would like to understand what I am doing wrong, since it takes a long time to download and configure all the apps I have installed.
Any help?
Thank you.
I hear ya there mine installed 28 of 31 apps and froze! Any help on this?
I had something similar a while back and in my case, the apps that would not restore with TB were in the data/app-asec directory, as opposed to data/app....
app-asec was introduced in Jellybean (I think) and is where a lot of paid apps may now reside. It's an anti-piracy measure I think and for me, TB would struggle to install them here.
My solution was to amend my TB prefs to force all restores to go to Internal Storage. It was previously set to "where backup was taken from". Forcing it to internal restores them to data/app and that has worked fine for me since....
Related
I've got JF 1.41 and the apps/caches on my SD card, and would like to apply the update. I have JF Auto Updater, and it found and downloaded - but I got the continuous loop after the update.
When I moved to 1.41, I had the same issue, and basically wiped the phone. I then reinstalled all of the apps one-by-one, which was somewhat painful since I have so many. I did back up my SMS prior to the wipe, but just for archival purposes (not that I needed most of them, but it'd have been nice to restore after the wipe).
For those who wipe their phone before an update - are you doing any backing up/restoring after the update? I know there's a couple of apps that do the backups, but I'm not sure how well they work with the apps on SD, or how well they can be applied after a wipe.
Sorry if this is the wrong forum - I posted here instead of apps because I figured people who find themselves wiping their phones more often would probably be here more than in the app forum.
giantcrazy said:
I've got JF 1.41 and the apps/caches on my SD card, and would like to apply the update. I have JF Auto Updater, and it found and downloaded - but I got the continuous loop after the update.
When I moved to 1.41, I had the same issue, and basically wiped the phone. I then reinstalled all of the apps one-by-one, which was somewhat painful since I have so many. I did back up my SMS prior to the wipe, but just for archival purposes (not that I needed most of them, but it'd have been nice to restore after the wipe).
For those who wipe their phone before an update - are you doing any backing up/restoring after the update? I know there's a couple of apps that do the backups, but I'm not sure how well they work with the apps on SD, or how well they can be applied after a wipe.
Sorry if this is the wrong forum - I posted here instead of apps because I figured people who find themselves wiping their phones more often would probably be here more than in the app forum.
Click to expand...
Click to collapse
the reason is that JFs update negates the link you created to your apps .. therefore your apps are essentially missing
http://forum.xda-developers.com/showthread.php?t=480582
using the modified update to v1.42 you maintain the link and no more flashing android laughing at you .. if you stay on the RC29-RC30-RC33 path you should not need to wipe your phone .. at all
Thanks LR! Didn't realize that - going to give it a quick backup using Nandroid and then follow the instructions on your link!
Edit - worked like a charm! Even better, being able to just slap on an upgrade and run a couple of scripts. Thanks again LR!
IF you do need to restore here is a post that might be able to help you. It might look complicated at first but if you can do LR steps then you should have no trouble following this. It's actually really easy however it'll only help you if you already have a backup of your apps.
I received my G Tab yesterday and within 4-5 hours last night I had installed 4 different ROMs, installed multiple kernels, and tested a ton of apps on each. I even got in to a boot loop, couldn't get the standard market fix to work, when installing at one point it FCd and then said it couldn't install more, etc, but I worked them all out. A few things that I learned that may help people (All instructions are with TNT 4.4 but work with other ROMs in different directories)
Market fix:
The standard market fix that is floating around is not always sufficient. To be sure that it will work, you need Titanium Backup installed.
Steps
1. Settings->Applications->System applications->Market then Clear Cache (if any) then Force Stop
2. Go back one and then Google Services Framework then clear data then Force Stop
3. Go to home and open Titanium Backup
4. Select Backup/Restore tab
5. Select Google Services Framework
6. Select Wipe Data
7. Go to home and open market (it will error and close)
8. Reboot your tablet
9. Open Market and you will have full market (I can't find anything I don't have)
----------------------------
For me, my boot loop came after installing 4 ROMS and on TNT 4.4 it crashed while using an app and went in to a loop. I had cleared everything in between all the installs but something must have been left over. I needed to repartition my sd card in CW. It worked great, but remember, select 2048, and for the second option select 0 or it won't work http://forum.xda-developers.com/showthread.php?t=865245
Also, remember to back up the titanium backup folder and anything else to your computer before doing this. It will wipe everything.
-----------------------------
The last issue was when I was installing a few apps the market FCd and then when I went back in it wouldn't let me install the apps that were going to install. I tried all the regular things like wiping data and cache but it didn't work. What worked was removing the corresponding asec files within the .android_secure folder at root.
-----------------------------
Almost every single app I have installed works great. The only major problem so far? The Grooveshark app. TinyShark works though.
I just got my Gtab too. I installed VEGAn and the kernel to go with it with the latest ClockWorkMod. When I installed Titanium I got an error saying 'ROM is not rooted' or something similar to this.
Hi!
Apologies in advance, I don't know much about the workings of android, I just follow guides!
I'm trying out my first custom rom, namely gingerclone, and am having trouble getting all my apps back up and running...
Before installing the rom, I backed up all my apps and settings with titanium backup, so I could restore them much easier after the rom change.
Although when I tried restoring them, I had lots of force closes with titanium backup itself, and about half of my apps would immediately FC on opening and didn't have icons. I then uninstalled the problem apps manually in settings>applications, and tried installing via the market. For some apps, it worked fine, but for others, whenever I try to install from the market, my phone reboots when the download is done and it tries installing. Sometimes it won't even download and just gives me errors, and for some they will install, but will not launch, just force close. I've tried cleaning the dalvik cache with titanium backup, and deleting settings files for the problem apps from my sd card, so that as far as I can see, there is no trace of them. But still, random reboots whenever I try installing, or unopenable if I manage to get them to install.
Any idea what could be going on? Plenty of other apps have installed and are working fine, so I'm stumped.
Had the same exact problem trying to install apps with titanium backup.
what i did was just slow down and install each app one by one and wait for each app to completely install before trying to install the next.
trying to download all of them all and once always made my phone reboot like it does to yours.
well hope this helps!
Wel I ended up uninstalling them all and trying to install again from the market, but I can't even get them to install individually now. It seems like trying to restore the backup has put some rogue files somewhere and is messing it up when I try to install the apps...
I have no idea why, but everything has started working again, so problem solved :/
I don't know. That never happened with me
*****I'm a beginner ROM Developer, so don't forget to thank and donate*****
Phone: Sidekick 4G
ROM: FreshBlood ROM - Beta
Kernel: Bali 2.2 /w Voodoo
As per my title, I'm getting this error message constantly after restoring my most recent backup of CM9 RC2. This was shortly before I started testing other ROM's (Hydro and CleanROM). The message comes back every single second, and I can barely get taps inbetween. Shutting the tablet off is a chore.
There are numerous threads on this error but they are all problems occurring on phones, not tablets, so I felt it appropriate to re-post. Any ideas to get this to go away? I don't have another recent backup so I'd like to be able to fix this without having to re-do all my work
Pertinent information:
Was using TF300T with CM9RC2 beforehand. Made nandroid backups, began testing other ROM's that required me to revert back to stock a few times. Have already tried restoring backup after factory reset, with cache and dalvik wiped. Pushing files to tablet on a Windows 7 PC using ADB, and everything on that end works fine. Also, if I dismiss the com.android.phone error, there are a number of other processes that have stopped working in the background as well, so the tablet is unusable.
Thanks,
Opethfan89
I've got a minor update to this issue, in that I decided to poke around in one of the backups that I know is a working backup, and found where the com.android.phone process is located (the /data partition, I guess).
So my question becomes, is there a way for me to manually load a nandroid backup and select/choose which files I restore from which folder? So if I get a com.android.phone folder from one backup and combine it into the backup that is messing me up, would that potentially work?
Also, how do I get access to the /data, /cache and other partitions on my tablet? Can I browse them through Windows Explorer or do I have to use Root Explorer on the tablet?
It's been four days, *BUMP*? Any responses?
My suggestion is do a clean install of the rom you want, forget about the backups and see if it works with a fresh install
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
While installing different roms on my device i learned to always do a full delete of cache, delvick cache, factory and last system. Always did it in that order. Maybe there is not very much logic to it since system will do all of it but that's what i did. I'm not sure what kind of recovery your using but I would recommend TWRP, but i doubt that's the issue.
Hope this helped
Thanks for the responses, guys.
I was not able to find a resolution to this error code or why it pops up, but I was able to salvage my install. My titanium backup from the 29th (before this error message was on my nandroid backups) was able to save all my apps, the layout, etc. I had to sit there for 3 hours manually allowing each and every app to install, but thats much better than trying to piece together which apps I had and what order they were in.
That being said, I'm now in the habit of making almost daily nandroid backups and titanium backups, as well as backing up any/all settings at every opportunity.
In response to the last post, I use CWM and I thought I clarified that in my original post. Not sure how/why the backups got corrupted, but I don't blame the recovery.
i get this fc when i change my sim with any other network sim card,maybe the phone has network lock?
I installed B145 with the kat 80b kernel and the v3 battery patch and everything looks good. I had to swipe as I was using build 81 before. Quite honestly, since I'm not running any synthetic benchmarks nor overclocking the proc, I'm hard pressed to find any difference in performance from EOS 3. Mind you, the buttery feel on this ROM (and EOS 3, for that matter) is day and night when compared to Asus's stock code. So if you're like me and waited this long to root your Transformer (I popped its cherry just a month ago, after having it for 1 year), don't be afraid to try this ROM... the best thing to have happenned to the og transformer.
One question I have is, what are you guys using to constantly restore your apps and/or settings after repeatedly flashing new ROMs? It's a pain in the neck having to reinstall all the apps and setting them up! Thank you and special thanks to Timduru and his minions This thing is awesome...
Sent from my Transformer TF101 using Tapatalk HD
I use Titanium Backup, but I let Google install all my apps, then restore the data.
There are a few apps I have to install using Titanium (from Amazon) that I have to restore using Titanium. Those apps I have to tap the Install button and Done for each one.
I tried using the App Backup in the ROM Toolbox by Jrummy, but it did not restore all the data correctly (mainly thumb keyboard).
I also make nandroid backups using TWRP so I can quickly restore a working ROM without having to reinstall stuff if something goes south.
I also use Titanium Backup but with some reservations. If you're going to go back to the ROM you're running, you're much better off with a nandroid backup. TB is cool for a few reasons: batch backup/restore, system apps or just apps, etc... however you have to be careful with it.
- Make sure you always verify your backups (often). Never assume "they'll work", cause they most likely won't - that's a known issue that it fails to parse its own packages once in a while, so batch restores just lock up the entire operation and you have to forcibly kill it to start where it left off.
- Always keep a copy of the backups elsewhere than on the tablet
- Just because it backs up a system app or an app doesn't mean it can restore it, even on the same rom.
- Some stuff like contacts need to be exported then imported back especially if you're upgrading to another android version.
- System apps will almost always fail to install on another android version unless they were "hacked" to make them work.
So yeah it's a really good and powerful tool but to use with caution. Always redo full backups and verify them before you wipe/flash and always have a complete nandroid backup to restore in case of issues, like Frederuco said.
Edit: Once you're on Team EOS's roms, I dount think you have to do a full wipe anymore. I just wipe cache, dalvik and system, then flash the new rom, that way all my apps are still there. I only do a full reset if I experience issues after doing this, to make sure it's the rom and not apps, and to report to Tim from a fresh flash.
Thank you both. I'll give Titanium a try whenever I try another ROM. In the meantime I decided to go back to EOS3 build 81. I *really* don't like the new status bar on top. It specially bugs me when browsing the web since it's eating up screen real estate.
[Edit]
This is probably a known issue, but for those going back from EOS 4 to EOS 3: the directory /sdcard was copied to /sdcard/0 after installing EOS 4; so, when I restored EOS 3 from nandroid backup, the system wasn't responding as it should and some apps were very slow (I guess expecting to find their data under /sdcard). Copying /sdcard/0 back to /sdcard and rebooting made everything work much better. Thanks.
landous said:
[Edit]
This is probably a known issue, but for those going back from EOS 4 to EOS 3: the directory /sdcard was copied to /sdcard/0 after installing EOS 4; so, when I restored EOS 3 from nandroid backup, the system wasn't responding as it should and some apps were very slow (I guess expecting to find their data under /sdcard). Copying /sdcard/0 back to /sdcard and rebooting made everything work much better. Thanks.
Click to expand...
Click to collapse
From what I've read this is an issue with CWM. I saw frederuco mention it on the EOS 4 thread.
I had the same problem, went from build 92 to preview 145 and Titanium Backup couldn't find anything. I was pulling my hair out until I saw his post
If you use TWRP 2.3.2.3 the /0 directory issue goes away.
Also, TWRP IMO is much better than any CWM to date.