Database Info

How do I get all my apps after flashing CM7

Hi,
Soooo.. I flashed CM7 for the first time ever..... woo hoo. but now all my apps, and everything from the stock are gone. Is there a way to load everything from stock onto the CM7? I tried doing a restore from NVFLASH but that just brought back the stock so how do I just keep everything the same but running the CM7.
Thanks guys

johnnyp500 said:
Hi,
Soooo.. I flashed CM7 for the first time ever..... woo hoo. but now all my apps, and everything from the stock are gone. Is there a way to load everything from stock onto the CM7? I tried doing a restore from NVFLASH but that just brought back the stock so how do I just keep everything the same but running the CM7.
Thanks guys
Click to expand...
Click to collapse
Well, if you had made a nandroid before you flashed, and could restore it (not sure when you did with NVflash), you would have everything back on your last ROM (you did not specify what ROM you were on).
You could then try just wiping dalvek and cache and formatting /system and flashing the ROM over it. That works OK most of the time. as you are clearing out the System partition but retaining your date (make sure you flash gapps also).
Another option is to wipe everything, and then flash the ROM, gapps, and then date only with advanced recovery.
Depending on what ROM you are coming from, that could carryover some issues - but most of the time it works OK.
If you did not have a backup of your data, then you will have to rebuild it from scratch in any case, so you might just as well do it on a clean install of CM7.

Well I did make a backup but when I restore its not cm 7 anymore so using nv flash how can I restore all the apps and messages, etc onto the cm7?
Sent from my LG-P999 using XDA Premium App

johnnyp500 said:
Well I did make a backup but when I restore its not cm 7 anymore so using nv flash how can I restore all the apps and messages, etc onto the cm7?
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Have you tried titanium backup? Restore your old Rom with the apps. Back them up using TI to the external sd card. Do the usual stuff to load a new rom and restore your apps using TI. That's how I do it.
Some also like google restore, but I like having a hard copy for myself.

jcbofkc said:
Have you tried titanium backup? Restore your old Rom with the apps. Back them up using TI to the external sd card. Do the usual stuff to load a new rom and restore your apps using TI. That's how I do it.
Some also like google restore, but I like having a hard copy for myself.
Click to expand...
Click to collapse
I downloaded titanium backup but it says the device is not rooted. I have the nvflash CWM on there but I assume its still not rooted. Now that I have the NVFLASH CWM and i can boot into recovery how do I root the G2X with the latest gingerbread update?

johnnyp500 said:
I downloaded titanium backup but it says the device is not rooted. I have the nvflash CWM on there but I assume its still not rooted. Now that I have the NVFLASH CWM and i can boot into recovery how do I root the G2X with the latest gingerbread update?
Click to expand...
Click to collapse
Restore your original stock rom with all the apps. Root using the one-click-method. Install TI. Backup your apps to the sd card. Now flash your favorite rom. Install TI on the new rom. Restore your apps from the TI backup you made on your sd card.
It should work.
Although on CM7 I had a couple of issues restoring certain apps. I think it has something to do with how CM7 names different partitions.

jcbofkc said:
Restore your original stock rom with all the apps. Root using the one-click-method. Install TI. Backup your apps to the sd card. Now flash your favorite rom. Install TI on the new rom. Restore your apps from the TI backup you made on your sd card.
It should work.
Although on CM7 I had a couple of issues restoring certain apps. I think it has something to do with how CM7 names different partitions.
Click to expand...
Click to collapse
The problem is one-click method doesnt work on 2.3.3.

johnnyp500 said:
The problem is one-click method doesnt work on 2.3.3.
Click to expand...
Click to collapse
Install a rooted version of 2.3.3 from the dev section.

jcbofkc said:
Install a rooted version of 2.3.3 from the dev section.
Click to expand...
Click to collapse
Yea but then I have to wipe the device before I install it which brings me back to how not having all my apps backed up on titanium

Sounds like your options are wipe or stay stock.
Sent from my LG-P999 using XDA App

I might have an idea but you'll have to do the research.
Boot into CWM and connect USB to your computer. You may be able to copy your /data/app folder to your computer using ADB commands, then restore them the same way. Might work, might not. Never done it that way. And this will probably only backup the apps, not the data (savegames, etc.).

As I said earlier, you can restore data only with recovery/advanced restore.
Sent from my LG-P999 using XDA Premium App

gaww said:
As I said earlier, you can restore data only with recovery/advanced restore.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Yes, restoring /data only from the advanced restore menu in CWM may work. But I think that will restore all system data as well which may cause FC frenzy. Definitely worth a shot!

r4d14n7 said:
I might have an idea but you'll have to do the research.
Boot into CWM and connect USB to your computer. You may be able to copy your /data/app folder to your computer using ADB commands, then restore them the same way. Might work, might not. Never done it that way. And this will probably only backup the apps, not the data (savegames, etc.).
Click to expand...
Click to collapse
I think ill just wait until gingerbreak or superoneclick are available on the update then I'll root it, back up with titanium, and restore after i flash cm7.
btw. If I do a wipe, and then go d/l the apps i paid for again will it recognize that ive already paid for em or would i have to pay again?

r4d14n7 said:
Yes, restoring /data only from the advanced restore menu in CWM may work. But I think that will restore all system data as well which may cause FC frenzy. Definitely worth a shot!
Click to expand...
Click to collapse
So far only issue is turning it off. Everything else works.
Sent from my LG-P999 using XDA Premium App

johnnyp500 said:
I think ill just wait until gingerbreak or superoneclick are available on the update then I'll root it, back up with titanium, and restore after i flash cm7.
btw. If I do a wipe, and then go d/l the apps i paid for again will it recognize that ive already paid for em or would i have to pay again?
Click to expand...
Click to collapse
All of your purchases are remembered. As long as you sign in with the same google account you bought them with you can download them again for free.
G2X CM7

Well so I took screen shots of all my screens and app drawer and just downloaded all my apps again. Then I restored the SMS from the SMS Backup and now everything is the same just running CM7. First time Ive flashed a rom woo hoo.

us my backup from the market. back up everything, then wipe, flash new rom, then download my backup from market, then restore your stuff.

need a real quick answer about rooting

So sorry guys, I couldnt find an answer through search. I rooted using Noxious Ninja's Windows program. Then unlocked bootloader, then flashed to CWM 6.0.1. I downloaded Beans Touchwiz ROM and I copied it to Root, now I rebooted in Recovery to install the ROM from zip but there is no Root folder, but I still have the Bean ROM in my Downloads folder as well. Can I install it from there or do I HAVE TO install it from Root directory?
So sorry guys, Ive been at this for hours LOL and have a terrible headache.

You do not have to flash from your "root" folder.
You may do so from your downloads folder perfectly fine.
Sent from my Droid using xda app-developers app

thanks, now only if i can delete this thread.

I dont know if your still here, but immediately after installing the ROM from .zip the directions say to restore... I just click restore and it like wiped out the ROM I just installed and put my phone the way it was before!!! Do I not restore from Recovery after I install a ROM?

No you make a back up before you name any modification to your device. And if you bork it you can restore then. Don't restore unless your not happy with new rom or you messed something up
Sent from my SGH-T999 using Tapatalk 2

Quick? Along these lines...... if I just backup my data, could I flash a new rom then flash data, would that restore all my data, and settings, or would It not be compatable from rom to rom
Sent from my LG-VM670 using xda app-developers app

jaredw444 said:
Quick? Along these lines...... if I just backup my data, could I flash a new rom then flash data, would that restore all my data, and settings, or would It not be compatable from rom to rom
Sent from my LG-VM670 using xda app-developers app
Click to expand...
Click to collapse
Don't do that.
The data's not compatible, yes.
Edit: Sometimes the data is compatible, e.g. if the dev says so, in which case you can dirty flash over without wiping the data.

thebobp said:
Don't do that.
The data's not compatible, yes.
Edit: Sometimes the data is compatible, e.g. if the dev says so, in which case you can dirty flash over without wiping the data.
Click to expand...
Click to collapse
Thanks, I was just was wondering,
Sent from my LG-VM670 using xda app-developers app

Basic TWRP Backup Question...Why Cant I Find This??

I have what seems like a very basic question on backing up using TWRP, and yet I havent been able to find this anywhere in the help threads.
When I am creating a backup it asks for what I want to backup: System, Data, Boot, Recovery, Cache, .android_secure.
Which of these do I want to make sure are checked? The first backup I did I left the default (which was only System and Data) and now I am unable to restore to that backup (I just get a blank, dark screen). Looking through the forums it seems I may need to flash boot.img in order to restore?
So does that mean in the future I should make sure to also check the Book option when I create backups? Any others?
Thanks.

system, data, boot
leave the other 3 unchecked

vincom said:
system, data, boot
leave the other 3 unchecked
Click to expand...
Click to collapse
Thanks again for all of your help over the last few days!
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? And is this fixable by flashing "boot.img" if I can find it somewhere?

Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? > yes
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier

vincom said:
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
Click to expand...
Click to collapse
You could probably just flash the same ROM you made the backup from and then just restore the data from that backup through TWRP. Then you'd be back to the same setup you tried to backup originally, right?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.

Jack_R1 said:
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Click to expand...
Click to collapse
My initial backup was made just with the default - first two boxes ticked. Unfortunately I now cannot get that backup to recover and boot, which is why I am asking. What else might be the cause or how would you suggest I try to solve?
Also, apologies but I dont understand what you mean when you say "Backing up recovery in recovery is useless, though." Do you mean this isnt the best way to make a backup/nandroid to recover to?

Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.

Jack_R1 said:
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Click to expand...
Click to collapse
Thanks. I think I misunderstood your initial post. When you said "system, data, boot" advice might fail me, I thought you meant NOT to backup boot. But I think you meant to ALSO backup .android_secure, not to avoid backing up boot.

When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?

lirong said:
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
Click to expand...
Click to collapse
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...

mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Click to expand...
Click to collapse
LOL. Can't we all just get along.
Since I'm not one to speak for others I'll only guess that what he was trying to get at is restoring only erases the boot.img. It then restores boot.img, system, data, android.secure, and cache. So in theory it doesn't actually erase any of the remaining partitions. It just writes over them. Whether or not this leaves any residual parts of any of the partitions has been a source of debate for quite some time. If it does format the partitions before restore there is no indication textually that I have seen.
Carry on.
EDIT: I might as well point this out before some one else does. The restores I stated above where done from CWM not TWRP. I forget what the thread was originally about. For that I apologize. The logic behind the post stands for either recovery though.

mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Maybe. But a couple of points. First, I've never had any issues. Second, have you watched what happens when you restore?
Wiping system.....
Formatting system....
Restoring system....
Wiping data....
Formatting data....
Restoring data....
Restoring boot...
This is on twrp 2.3.3.0 and 2.4.0.0. So technically it does the wipes for you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mahanddeem said:
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So basically you have no idea what you're saying. I guess I'll go back to my being concise point
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
You're obviously a CWM guy. I'm a TWRP guy. Both are good recoveries and used by many. So use what you're comfortable with and you know works.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Details of a rom from Nandriod Backup

Hello
All XDA members
I have a problem that made me raise a question an that is an we know the name of a rom from a nanriod backup either on PC or on Andriod.??
Ideally PC would be good !!
Thanks

Most ( not all) recovery apps let you name the file. Are you asking how to find the file? If so, it likely is in a folder named backups. You can move the file to your pc and keep it there if you are out of storage space.
Sent from my CROM-i X powered TF700T using tapatalk

stevens243 said:
Most ( not all) recovery apps let you name the file. Are you asking how to find the file? If so, it likely is in a folder named backups. You can move the file to your pc and keep it there if you are out of storage space.
Sent from my CROM-i X powered TF700T using tapatalk
Click to expand...
Click to collapse
Sorry if I wasn't clear please consider the following situation :
I have around 12 backups of different roms and I dont want to restore each n every backup for sake of simple file or simple thing. So any tool which can read the name of Rom? Probably the buildprop or about phone info will help
Sent from my A110 using Tapatalk

Well, if you gave a single boot system, your recovery should "see" all of those files. If so, you can usb them or copy to a sd card and move them. Just move them back when you need to.
Sent from my CROM-i X powered TF700T using tapatalk

Can someone explain nandroid backup to me? Does it mean I can make a backup my current rom and save it? Sorry for the dumb question.

Yep
TPS_Reports said:
Can someone explain nandroid backup to me? Does it mean I can make a backup my current rom and save it? Sorry for the dumb question.
Click to expand...
Click to collapse
Simply,it is a backup of your OS and settings. It is extremely valuable if you flash a new ROM that doesn't/won't function. Then, you can use your recovery to, well, recover your previous WORKING OS.
When/if you begin to flash new ROMs (and other tools that may corrupt your OS) you should always.first.backup.your.files.

Can I assume I would need to wipe data/factory reset, etc. before I restore the backup?
Sent from my VS980 4G using Tapatalk

No assumptions
TPS_Reports said:
Can I assume I would need to wipe data/factory reset, etc. before I restore the backup?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
So, that depends on what your starting config is, what you upgraded to.
For instance, if you are stock and flash a ROM using the stock recovery, then likely yes. You should and you would use the stock bootloader to wipe with.
If you have loaded a new recovery (TWRP, CWM) then read(!) the instructions on the developers page. My example is that on my tablet, once I upgraded to TWRP, I SHOULD NOT use the factory wipe option as that would wipe both TWRP and the backup files. That would cause lots of problems so, don't assume.
Typically, you do need to data/reset/wipe prior to flashing a new or recovering to an old ROM, just be careful what/how you do it.

I have a CWM recovery installed and installed custom Rome before. I have always redid everything again. So a backup would save me a lot of time.
Sent from my VS980 4G using Tapatalk

TPS_Reports said:
I have a CWM recovery installed and installed custom Rome before. I have always redid everything again. So a backup would save me a lot of time.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Then, unless the ROM developer states otherwise, you should make backups, wipe data, install ROMs and recover your device using the Nandroid backup.
You likely shouldn't use the "factory" wipe data as that would cause issues.
Larry

[Q] TWRP Backup from one Nexus 5 to another?

Does anyone know, if I create a TWRP backup, can I restore it to a different Nexus 5? Both phones have been unlocked, rooted and with custom recovery installed in exactly the same way.
Just got a replacement phone, and would rather not have to spend the time to set it all up to my liking again!
Thanks

kev_gordon said:
Does anyone know, if I create a TWRP backup, can I restore it to a different Nexus 5? Both phones have been unlocked, rooted and with custom recovery installed in exactly the same way.
Just got a replacement phone, and would rather not have to spend the time to set it all up to my liking again!
Thanks
Click to expand...
Click to collapse
Yes you can. But DO NOT backup and restore the efs partition. That will make your new device useless. Only backup and restore system and data. That's twrp's default backup.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes you can. But DO NOT backup and restore the efs partition. That will make your new device useless. Only backup and restore system and data. That's twrp's default backup.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That has made my day! Thank you :victory:

jd1639 said:
Yes you can. But DO NOT backup and restore the efs partition. That will make your new device useless. Only backup and restore system and data. That's twrp's default backup.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Oh... just checked and in TWRP, System, Data and Boot are ticked by default. Should I untick Boot as well then?

kev_gordon said:
Oh... just checked and in TWRP, System, Data and Boot are ticked by default. Should I untick Boot as well then?
Click to expand...
Click to collapse
Boot's ok, especially if you have a custom kernel
Sent from my Nexus 5 using XDA Free mobile app

kev_gordon said:
Oh... just checked and in TWRP, System, Data and Boot are ticked by default. Should I untick Boot as well then?
Click to expand...
Click to collapse
It should be fine, it's the kernel.
ANYTHING BUT EFS.