Develop Bugs

[Q] Some Newb Questions on going from Rooted Stock to Cyanogen

hello,
I rooted back in 1/2011 using Unrevoked3.
From there I changed from clockwork to amon-ra, installed busybox v1.17.1, as well as ROM Manager
v3.0.0.7. At that time I did a Nandroid backup (selected: boot, system, data, recovery, wimax, & android_secure )
From there I left it as a stock ROM with the following:
Hboot 0.97.0000, Build # 3.29.651.5,
Android 2.2
Baseband Version: 2.15.00.09.01,
Kernel Version: 2.6.32.15-ge2fb08e [email protected] #11,
Software : 3.29.651.5,
Hardware Version 3,
pri version: 1.77_003
prl version: 60671
Now I haven't really followed all of the ROM tweaks, variants, and developments over the past year. The evo is starting to get a bit sluggish...so I figured an update and a change would be good...I plan on going from STOCK to current stable cyanogen.
I think that I could restore the apps and such with titanium (if I ensure that 'system data migration' is enabled) however I would think that it would be best to start off fresh....
I would like to keep my text messages.
I have been scouring cyanogen forums, xda, and such... there is alot of conflicting/not updated information. I am probably over analyzing, just being cautions.
Question 1: should I have to update ROM Manager, Busybox, or AmonRa? (they are same version from when I rooted) <my guess is no, but I am unsure if there is some major bug that was fixed, especially with respect to AmonRa>
General Order:
1) follow instructions per
http://forum.cyanogenmod.com/topic/...ated-07-august-2011-now-kernel-info-included/
(perform another nandroid backup, wimax keys backup > and make a full SDCARD backup to the PC > Flash Cyanogen > flash GAPPS > flash GPS fix > flash latest radio/wimax/pri/prls)
I have titanium pro, but there settings seem a bit overwhelming.
Once I flash cyanogen & radios...
Question 2: what is the best way to restore my texts?
I was thinking the following:
- First - delete all folders on sdcard except nandroid / TitaniumBackup
- Second - sync google contacts/calendar
- third - go to the market and install appbrain to re-sync applications that I like
- fourth- use titanium to restore text messages com.android.mms-FILENAME.properties (and .tar.gz)
Question 3: I am assuming that this is the only file required to restore my SMS/Text messages, am I correct?
or does cyanogen use a different application?
Question 4: is there anything critical that I am missing?
Thanks for your time
Qu1nn

I think that I could restore the apps and such with titanium (if I ensure that 'system data migration' is enabled) however I would think that it would be best to start off fresh....
Click to expand...
Click to collapse
Apps are fine to be restored with Titanium, that's what it was made for. System data, no. NEVER backup and restore system data between different roms.
I would like to keep my text messages.
Click to expand...
Click to collapse
SMS Backup and Restore from the market.
Question 1: should I have to update ROM Manager, Busybox, or AmonRa? (they are same version from when I rooted) <my guess is no, but I am unsure if there is some major bug that was fixed, especially with respect to AmonRa>
Click to expand...
Click to collapse
Always update is there are updates available. 99% of the time, updates only make things better.
(perform another nandroid backup, wimax keys backup > and make a full SDCARD backup to the PC > Flash Cyanogen > flash GAPPS > flash GPS fix > flash latest radio/wimax/pri/prls)
Click to expand...
Click to collapse
Pretty much. Put rom zip on root of sd card, boot into recovery, make a Nandroid Backup, wipe data/cache/dalvik, flash new rom, reboot. I'm almost positive the cm7 zip comes with gapps, you shouldnt have to flash those separately. Radios can be flashed anytime.
Question 2: what is the best way to restore my texts?
Click to expand...
Click to collapse
Again, SMS Backup and Restore. Simple app, one click to backup and one click to restore.
- First - delete all folders on sdcard except nandroid / TitaniumBackup
- Second - sync google contacts/calendar
- third - go to the market and install appbrain to re-sync applications that I like
- fourth- use titanium to restore text messages com.android.mms-FILENAME.properties (and .tar.gz)
Click to expand...
Click to collapse
You dont need to delete things off the sd card unless you need the space. And you can use Titanium to backup and restore texts, but not if you are switching from a Sense rom to an AOSP rom.

Just start off fresh and forget the messages. Latest amon-ra is 2.3 and get rid of rom manager
Sent From My Pocket

sitlet said:
Apps are fine to be restored with Titanium, that's what it was made for. System data, no. NEVER backup and restore system data between different roms.
Click to expand...
Click to collapse
+1
sitlet said:
SMS Backup and Restore from the market.
Click to expand...
Click to collapse
+1
sitlet said:
Always update is there are updates available. 99% of the time, updates only make things better.
Click to expand...
Click to collapse
+1
sitlet said:
Pretty much. Put rom zip on root of sd card, boot into recovery, make a Nandroid Backup, wipe data/cache/dalvik, flash new rom, reboot. I'm almost positive the cm7 zip comes with gapps, you shouldnt have to flash those separately. Radios can be flashed anytime.
Click to expand...
Click to collapse
None of the CM zip files, atleast none that I have ever flashed, come with gapps already bundled together. I've always had to flash them separately. Also, reflash your kernel after flashing your radio. Some people say this is a must and some people say its all hoopla. I always do it just to be on the safe side.
sitlet said:
Again, SMS Backup and Restore. Simple app, one click to backup and one click to restore.
Click to expand...
Click to collapse
sitlet said:
You dont need to delete things off the sd card unless you need the space. And you can use Titanium to backup and restore texts, but not if you are switching from a Sense rom to an AOSP rom.
Click to expand...
Click to collapse
You don't need to delete anything off of the SD card but you do need to make a backup of your SD card beforehand. The very first time I rooted and flashed a custom ROM my entire SD card got wiped out somehow. I'm still not sure why since flashing a ROM doesnt write to the SD card. Either way, I lost everything that I had on there before. I've been doing incremental backups of my SD card ever since. Again, better safe than sorry.

[Q] Restoring backups after Lollipop upgrade and TWRP 2.8.6.0

After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.

khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
Click to expand...
Click to collapse
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.

najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Thats true - I did read about that. And that would definitely explain being unable to restore a kitkat rom.
However, I cant even restore a lollipop backup after flashing a different lollipop rom! Even if they are both derived from the same FOB6 base! That is what is even more confusing. Try it - backup, wipe all the partitions except int and ext sd of course and then try to restore... it just doesnt work!

Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0

I've had no problem restoring from a TWRP Backup on Lollipop numerous times.

najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
I noticed that in every folder in /data/app/ there is an apk called base and a folder lib, can i backup just the apk? Or when i need to share an apk or take an apk i need to take also rhe lib?

dugryce said:
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
Click to expand...
Click to collapse
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!.
Click to expand...
Click to collapse
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.

senozlu1 said:
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
Click to expand...
Click to collapse
Oh I'll try this and report back. Thanks
Sent from my SM-N900T using XDA Free mobile app

yummymango said:
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
Click to expand...
Click to collapse
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Sent from my SM-N900T using XDA Free mobile app

khanam said:
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Click to expand...
Click to collapse
One of the devs, who runs the Lollipop ROM I've been using, warned against restoring data. He suggested backing up apps + data through Titanium Backup instead. Maybe it depends on the ROM?

najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Hi
I have a rooted S4 running Carbon. Im using TWRP 2.8.5.0 and can backup and restore any
KK rom with no issues. I can flash Lollipop and backup but it will not restore this backup.
Its says restore successful but then just boots back into recovery. If someone could resolve
this it would be great

Hello all,
TB doesn't seem to pick up the apk file when backing up which is quite frustrating. Does anyone have a solution?

i had backup using TWRP 2.8.7.0 my stock TW lollipop rom...Now i had flashed Dirty Unicorns v9.5...If i wanted to goto stock rom that nandroid backup wont work??? thats what people are complaining over here??

Problem with restoring twrp backup

Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?

mr.banana said:
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
Click to expand...
Click to collapse
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.

indian84 said:
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
Click to expand...
Click to collapse
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff

mr.banana said:
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
Click to expand...
Click to collapse
Backing up all the partitions was the mistake.
Getting your stuff back looks difficult.
If you flash ROM using TWRP, your media files and anything stored on your phone won't be deleted.
But all your apps and stuff will be lost.

Error while backing up Stock OS using twrp

I'm not able to create backup of Stock ROM through TWRP. The error says "Failed to mount /system". While in the Mount menu, the "system" is unmounted by default. When I select "Mount system partition read only" option, I'm able to mount it. And the size of the system is shown abnormally large(check SS).
Any solution for this? And can anyone explain what that "Mount system partition read only" option meant for? Will there be any risk if I create backup keeping mount system partition read only?

Kailash Choudhary said:
I'm not able to create backup of Stock ROM through TWRP. The error says "Failed to mount /system". While in the Mount menu, the "system" is unmounted by default. When I select "Mount system partition read only" option, I'm able to mount it. And the size of the system is shown abnormally large(check SS).
Any solution for this? And can anyone explain what that "Mount system partition read only" option meant for? Will there be any risk if I create backup keeping mount system partition read only?
Click to expand...
Click to collapse
I am betting your device is encrypted. If that is the case backups will not work.

zelendel said:
I am betting your device is encrypted. If that is the case backups will not work.
Click to expand...
Click to collapse
It's not encrypted. I always remove all the passwords before creating a nandroid backup.

Kailash Choudhary said:
It's not encrypted. I always remove all the passwords before creating a nandroid backup.
Click to expand...
Click to collapse
Removing passwords doesnt encrypt the device. That happens on the very first boot. unecrypting the device wipes it.
To be honest I wouldnt worry about it too much. Even when backed up stock roms dont like to be restored and people that do normally just end up flashing the stock os due to the issues that popup.

zelendel said:
Removing passwords doesnt encrypt the device. That happens on the very first boot. unecrypting the device wipes it.
To be honest I wouldnt worry about it too much. Even when backed up stock roms dont like to be restored and people that do normally just end up flashing the stock os due to the issues that popup.
Click to expand...
Click to collapse
Do you mean removing passwords do not decrypt the device?
Do you know what that option "Mount system partition read only" is meant for? What changes will it make to my backup when I restore it in future.

Kailash Choudhary said:
Do you mean removing passwords do not decrypt the device?
Do you know what that option "Mount system partition read only" is meant for? What changes will it make to my backup when I restore it in future.
Click to expand...
Click to collapse
Yes that is exactly what I mean. That just means That the system is read only. It cant be modified. Too be honest I gave up on backing up my device years ago due to restores never going well and having to reflash full stock anyway

So now you've to flash stock ROM and start as a fresh device everytime when you want to revert back?
Actually this issue wasn't there before zlendel. I've created a backup 1½ month ago. Then I've flashed a custom ROM, didn't liked it so I restored the backup. Since then, I haven't did any modifications to the device.

Kailash Choudhary said:
So now you've to flash stock ROM and start as a fresh device everytime when you want to revert back?
Actually this issue wasn't there before zlendel. I've created a backup 1½ month ago. Then I've flashed a custom ROM, didn't liked it so I restored the backup. Since then, I haven't did any modifications to the device.
Click to expand...
Click to collapse
I always flash a pure clean flash. Mostly because dirty flashing always causes issues.
What rom did you flash? Not all roms are made some same.

zelendel said:
I always flash a pure clean flash. Mostly because dirty flashing always causes issues.
What rom did you flash? Not all roms are made some same.
Click to expand...
Click to collapse
zelendel I'm on OOS 4.1.6, trying to create it's backup. I wanted to flash Paranoid Android after creating the backup.

Kailash Choudhary said:
zelendel I'm on OOS 4.1.6, trying to create it's backup. I wanted to flash Paranoid Android after creating the backup.
Click to expand...
Click to collapse
At this point I am not sure. I dont use either and never have. If I recall right You will have to change the file system to ext4 for PA which will wipe your device. I could be wrong.
I would ask in the OOS thread.

I do a clean install everytime. At any rom. Never have any problems, conflicts.
I notice problems with restoring twrp backup, made, like 2 hours ago..

Kailash Choudhary said:
zelendel I'm on OOS 4.1.6, trying to create it's backup. I wanted to flash Paranoid Android after creating the backup.
Click to expand...
Click to collapse
It's not mandatory to change the file system to ext4 for AOSPA, but it works better rather than on f2fs and they aren't supporting possible problems on f2fs.
Also, If you're going to flash AOSPA, I suggest a clean flash to avoid possible problems with battery drain or other bugs that have been reported in that thread.
Cheers!

dugi9991 said:
It's not mandatory to change the file system to ext4 for AOSPA, but it works better rather than on f2fs and they aren't supporting possible problems on f2fs.
Also, If you're going to flash AOSPA, I suggest a clean flash to avoid possible problems with battery drain or other bugs that have been reported in that thread.
Cheers!
Click to expand...
Click to collapse
Yeah, I did a clean flash. IDK which file system it is. Battery life has improved a bit and no heating issues. Gaming performance have improved a lot.

what version of TWRP are u using? having complete Stock OS should not cause issues, i have never decrypted my device and no issues backing up, also u may not want to back up every single thing, try doing it without the System Image, i would just back up System, Data, and Boot, maybe EFS too but i don't

Suggests that there is an error in the /system partition. Have you modified the system partition? If not, you don't really need a back up of it.

What should I backup with TWRP?

So I'm still learning how this device works with a/b partitioning and such. I'm wondering what I should backup in TWRP in order to be able to fully restore my ROM, apps, and settings without backing up mg entire system image.

dave31g said:
So I'm still learning how this device works with a/b partitioning and such. I'm wondering what I should backup in TWRP in order to be able to fully restore my ROM, apps, and settings without backing up mg entire system image.
Click to expand...
Click to collapse
Just back up user data. Last I knew, TWRP had issues with backups and I think it hasn't been fixed yet