Database Develop

cyanogenmod 4.1.99 support line for installation issues

ok due to the massive number of people clogging the offical thread im starting this thread just to help some of our newer members get working. anyone with a proper working install can help as well. let the issues begin.

i have no data connection at all i have installed 1.6 from htc and then 4.1.99. I even went back and wiped and reinstalled both rebooted and still no connection (3g or 2g).
any ideas

when you signed into google did it work or say cant connect?

Ok here's a question. I was running 4.1.11 which was running fine. I downloaded the recovery image & flashed it thru the recovery console (home + power) and then tried to flash 4.1.99 & now when i try going into the recovery console, I get the Exclamation point with the phone on its side. If i let it power thru it loads up, but like its stock.
I even tried terminal emulation & can't even get the SU command to work.
Any suggestions besides, re-rooting?

This is what I did
Okay, let me start off by saying I have had none of the lag a lot of the people are reporting. So I figured I would post how I installed step by step just incase it helps someone.
Step 1: Download the HTC rom and Cyanogen rom.
Step 2: Reboot into recovery.
Step 3: Flash the HTC update from recovery and let it finish ( it will do the radio as well) the phone will reboot back into recovery by itself.
Step 4: Wipe.
Step 5: Flash the Cyanogen update.
Step 6: Enjoy.
Don't think it would make any diff but just incase, I came from JACxHEROSkiv2.2 and cm 1.4 recovery.
Hope this helps in any way.

yes the same thing happened to me. its very simple too. just fastboot cyanogens recovery.img
http://forum.xda-developers.com/showthread.php?p=3915123
heres fastboot stuff
http://forum.xda-developers.com/showthread.php?t=502010
then flash newest cyanogens like normal and wipe afterwards.

Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition

Every time I try updating to 4.1.99 It stays on the g1 screen.

persiansown said:
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Click to expand...
Click to collapse
try wiping your ext3 however please note alot is going on first boot. i didnt have any issues with slow but i wiped my ext3 and data(wipe in recovery) slow downs are caused mostly by missing or incompatible issues. thats why wiping is recommended. try wiping ext3 and start from scratch. its worth it.

10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2

jeremycool said:
Every time I try updating to 4.1.99 It stays on the g1 screen.
Click to expand...
Click to collapse
did you flash the adp image first?

mormo said:
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
Click to expand...
Click to collapse
check your md5s on both and start from scratch.

Here's what I did:
1. Wipe.
2. Delete all your EXT partition stuff.
3. Reboot into recovery.
4. Flashed the HTC update from recovery. I did NOT reboot after this finished.
5. Flashed the Cyanogen update.
6. Rebooted and waited for the post flashing process to finish.
I had one single FC at the beginning but now it's all good.
If you are not clearing out your dalvik cache and all your other EXT stuff AND wiping, then it's only not working because you didn't do those things.

yes both ways work. however if you have issues try letting the radio install. ONLY if you have issues.

here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!

the reason some people have to let the radio flash is due to either a bad flash. corrupted install or some other reason. every new version come with a new radio and it will sometimes delete your recovery. this is because certain older setup are different and not very consistant. however things happen and some stuff gets messed up. every dream is the same and this software is the same. but you are the different part.

damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
wipe is to fix an issue with google apps. as well as if you had something before causing issues.

damngood98 said:
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Click to expand...
Click to collapse
Not sure if it is your only option, but it might help. And no you will not need to flash anything afterwards.

jokersax11 said:
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
Click to expand...
Click to collapse
damn! gonna go bed and maybe pout for a bit tomorrow before i do another wipe. I hate wiping!
thanks for help joker!

damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
Look at it this way...
You moved into a new place and the last tenant was evicted. He left all his crap lying around (mostly trash and dirty laundry.)
Do you sweep the rooms and take out the trash and call it a day? Or do you clean the whole house first? Technically, taking the trash should be enough (laundry included) but you never know what else is hiding in the house (maybe he had a pet tarrantula and it's walking around unbeknown to you. Eventually, you'll run into it and force close yourself in shock.

Important!

My phone isn't working again!
I was running ChromatcRom4.5 on my g1(its the first rom i used) and decide i wanted to try out another Rom in the process of doing that the new rom i wanted to try didn't work out and now I want to go back to my chromatcRom4.5.
I am so lost! My phone just reboots it self back in recovery mode everytime. It says Chromatc installed and when I hit "reboot system now", it reboots but it doesn't load the rom and just resets and goes back in recovery mode. What do I need to do so it will load the rom correctly? Am I missing files or am I not installing it right? Please I really need to my phone to be working.

sorry Im new to all this and still learning. Much help will be greatly appracaited.

probably you had a corrupted flash.
my best bet is that
1- you do a full system wipe "won't effect your sd card" using
"fastboot erase system -w"
2-reboot into recovery and do a full manual erase "system, cach, dalvik..." just to be sure
3-re download your desired rom and put it on SD
4-make sure that if you rom of choice needs DangerSPL that you meet the requirement.
5-flash away.
hope that helps.
p.s. please show or post your Phone specs so that anyone can help you more efficiently.

I am currenting useing The G1
I tired all the directions and still the same.
using clockworkMod Recovery v2.5.0.1
-wipe date/factory reset
-wipe cache partition
-advanced wipe dalvik cache/battery
Install zip from sdcard
-choose zip from sdcard
-apply: G1-radio-2_22_23_02.zip
then go back to menu and addvaced and hit reboot in recovery
-apply: spl-signed.zip (is that he danger-spl?)
and reboot in recovery
apply: wipedatacachesystem.zip
and then apply:chromatic4.5.zip
and reboot system
My phone reboots and when its at the G1 logo and reboots again and now its in recovery mode again. Iam not sure what I am doing wrong. Any help please?
and If their another Rom you guys think is better and stable, can you guys give me to link to how to flash it?

also how do you "fastboot erase system -w"

nevermind i found out the problem after millions of times i failed.
clockworkMod Recovery v2.5.0.1 never works for me i dont know why that is.
I had to downgrade to the older one in order to run Roms w/o any problems. Anyways the older one is way better!

clockwork tends to have problems with g1's. or rather, g1's tend to have problems with clockwork.
that's why i stick with the trusty Amon Ra. except a themed version of it

Tagged for a move to Q&A. Please post in Q&A/thread next time as this has nothing to do with development.

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

Stuck on bootloop, stock recovery, want to recover files.

So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.

eXtrimist said:
So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
Click to expand...
Click to collapse
Assuming that you haven't yet extended partitions, stock phone has 2 system partitions. So if you're using system 1, boot using system 2 and vice versa. AFAIK, if you flash stock miui using MiTools, it wouldn't erase the storage on the phone.

The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!

eXtrimist said:
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
Click to expand...
Click to collapse
Glad you could work it out. Don't be lazy next time

upgrading to Nougat, trouble replacing old kernel

Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.

The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.

zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?

jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.

jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?

Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.

Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip

jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.

Try reverting to stock
Install stock firmware using adb

TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.

jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.

jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.

Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?

jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here

Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?

jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.