Yo. If I want to re-flash the same rom I'm currently running to make a singel change, lets say, change the boot animaton/disable fsync/choose different apps/change from deodex to odex/so on, do I simply boot to recovery and flash it again and make thoose changes? Something I should do before/after?
I'm running 4.2.1, CROMi-X 4.6.9 - 10.6.1.14.8/WW DEODEX.
Auca said:
Yo. If I want to re-flash the same rom I'm currently running to make a singel change, lets say, change the boot animaton/disable fsync/choose different apps/change from deodex to odex/so on, do I simply boot to recovery and flash it again and make thoose changes? Something I should do before/after?
I'm running 4.2.1, CROMi-X 4.6.9 - 10.6.1.14.8/WW DEODEX.
Click to expand...
Click to collapse
You need to backup your current system first if something is going wrong. Since you are coming in the same rom, you want to wipe dalvik and cache and you should be fine. Good luck.. :fingers-crossed:
Auca said:
Yo. If I want to re-flash the same rom I'm currently running to make a singel change, lets say, change the boot animaton/disable fsync/choose different apps/change from deodex to odex/so on, do I simply boot to recovery and flash it again and make thoose changes? Something I should do before/after?
I'm running 4.2.1, CROMi-X 4.6.9 - 10.6.1.14.8/WW DEODEX.
Click to expand...
Click to collapse
I've done this before too. Very easy, but the backup is imperative just in case something awry happens. Make sure the battery is charged enough also IMO!
Just to be sure, when you say backup, what do you mean? I have backed up everything with titanium backup and uploaded it to dropbox, plus I made a backup in TWRP. Also known as nandroid... right?
Auca said:
Just to be sure, when you say backup, what do you mean? I have backed up everything with titanium backup and uploaded it to dropbox, plus I made a backup in TWRP. Also known as nandroid... right?
Click to expand...
Click to collapse
Yes, you are correct.. :good:
Just flash liver the top no wipes required but you can do dalvik if you want to keep it clean.
I do a backup when updating but no harm having a recent nandroid to restore just in case.
Related
ok since we getting more roms and have hellraiser over there opening the door. i have ALOT of nandroid back ups.
now having never had to actually use one of these i wanted to know somethings.
is a nandroid like a Rom, i just have to flash over another rom, or from stock and boom i have that Rom back with all my apps and info.
or do i need to load up the rom then nandroid on top of that for it work??
just have never had a use, but i would like to go back to some of my prior setups.
A nandroid is a system restore basically. If you fubar something and can get into recovery you can restore that nandroid to exactly where the phone was before. You don't need to flash anything just be able to get into recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
Thanks am, flashing one now just to see....
the2rrell said:
ok since we getting more roms and have hellraiser over there opening the door. i have ALOT of nandroid back ups.
now having never had to actually use one of these i wanted to know somethings.
is a nandroid like a Rom, i just have to flash over another rom, or from stock and boom i have that Rom back with all my apps and info.
or do i need to load up the rom then nandroid on top of that for it work??
just have never had a use, but i would like to go back to some of my prior setups.
Click to expand...
Click to collapse
A nandroid will reflash system, data, cache - everything. The only thing a Nandroid won't flash is a kernel if you're doing a major change (e.g. Froyo to Gingerbread or either of those to CM7 - while it's also GB, it requires special kernels.)
Entropy512 said:
A nandroid will reflash system, data, cache - everything. The only thing a Nandroid won't flash is a kernel if you're doing a major change (e.g. Froyo to Gingerbread or either of those to CM7 - while it's also GB, it requires special kernels.)
Click to expand...
Click to collapse
ok with that said, you should flash the Kernel before the nandroid to make sure there is a compatible kernel there for the nandroid to use??
basically match up froyo roms and kernels and visa versa for BG before i decide to flash a Nandroid?
the2rrell said:
ok with that said, you should flash the Kernel before the nandroid to make sure there is a compatible kernel there for the nandroid to use??
basically match up froyo roms and kernels and visa versa for BG before i decide to flash a Nandroid?
Click to expand...
Click to collapse
Yup, that would be a good idea - since if you restore the nandroid on an incompatible kernel, you'll have the phone be very unhappy. (Will refuse to boot.)
Much thanks E.........appreciate the time bruh.
this can be closed.
I completely failed here E, i tried to restore a nandroid. i loaded the Infusion GB Kernel then proceeded to restore the nandroid and just get boot loops no matter how i do it.
any thoughts??
Hmm I think I need to look at this later in the week. Starting to sound like Nandroid might be broken in red CWM.
i got it, but i had to load the Kernel - Rom - then do the nandroid. but that kinda of defeats the purpose in my eyes....lol
but yea, if you find something that would be cool to know E.
Hi,
i am using CWM.
currently, i am under Cyanogen.
i want to try AOKP.
my question is
i have followed the steps below
a backup
Wipe data
Wipe system
Install AOKp
Till now am i right?
and after to come back to my backup
step 1
Should i Wipe Data?
step 2
Should i wipe system ?
Restore CWM of Cyanogen
are the steps 1 and 2 necessary?
is it a bad practice?
do it let gremlim?
moreover can i restore a back up made under TWRP from CWM?
Can i restore a back up made under CWM from TWRP?
how do you restore the back up?
am i missing steps? Fix permissions?
do i need to recalibrate my battery each time?
Thanks
Heniki
You can only restore CWM backups with CWM and TWRP backups with TWRP. As of now CWM 6's backup function is broken but it is being worked on. So make sure your Backups are from either TWRP or CMW 5 if you want them to work.
To restore a backup I wipe data/factory reset and wipe system. Then choose the backup I want to restore. No need to fix permissions unless things start to act funny after the restore. As far as battery calibration goes it's a myth.
hechoen said:
You can only restore CWM backups with CWM and TWRP backups with TWRP. As of now CWM 6's backup function is broken but it is being worked on. So make sure your Backups are from either TWRP or CMW 5 if you want them to work.
To restore a backup I wipe data/factory reset and wipe system. Then choose the backup I want to restore. No need to fix permissions unless things start to act funny after the restore. As far as battery calibration goes it's a myth.
Click to expand...
Click to collapse
With R6, Bryan said he fixed the backup and restore issues with CWM6. Idk about the rest of the features
When you say "Cyanogen" I think many assume you mean CM9 (ICS).
If you are running CM7 (GB), be very careful how you restore. Most system data (and perhaps some user data) from GB is not compatible with ICS.
jeffsf said:
When you say "Cyanogen" I think many assume you mean CM9 (ICS).
If you are running CM7 (GB), be very careful how you restore. Most system data (and perhaps some user data) from GB is not compatible with ICS.
Click to expand...
Click to collapse
Right, i am under CM9
Thanks guys
How i Can move from TWRP To CWM?
i found this one to move from CWM to TWRP http://forum.xda-developers.com/showthread.php?t=1721489.
i want really to understand what are the bad practices which will create gremlims
heniki said:
Thanks guys
How i Can move from TWRP To CWM?
i found this one to move from CWM to TWRP http://forum.xda-developers.com/showthread.php?t=1721489.
i want really to understand what are the bad practices which will create gremlims
Click to expand...
Click to collapse
As Fb said in the post you linked you flash the boot.img that came with your rom or reflash the rom.
The more times you flash roms the more issues you could have with "gremlins". Read more about it in the link.
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my SGH-T959V using xda premium
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Hey there!
I am quite new on this but am getting really tired of my tf700 being sluggish and slow, so I decided to flash a new rom and try to make a NVflash backup first just to be safe. But before doing all this I wanted to make a backup of all my app data which I can do easily with a rooted tablet and a backup app. Problem is, I am on 10.6.1.14.10 right now and I need 10.6.1.14.8 to be able to root it. So I decided that I should root it before making a backup, so here's my question, does a downgrade of stock rom require a clean wipe or wipe data at all? Or is it safe for me to downgrade, install a backup app for app data and then unlock make NVflash-blob and so on?
tl;dr Does downgrading from 10.6.1.14.10->10.6.1.14.8 require a data wipe?
kotidoti said:
Hey there!
I am quite new on this but am getting really tired of my tf700 being sluggish and slow, so I decided to flash a new rom and try to make a NVflash backup first just to be safe. But before doing all this I wanted to make a backup of all my app data which I can do easily with a rooted tablet and a backup app. Problem is, I am on 10.6.1.14.10 right now and I need 10.6.1.14.8 to be able to root it. So I decided that I should root it before making a backup, so here's my question, does a downgrade of stock rom require a clean wipe or wipe data at all? Or is it safe for me to downgrade, install a backup app for app data and then unlock make NVflash-blob and so on?
tl;dr Does downgrading from 10.6.1.14.10->10.6.1.14.8 require a data wipe?
Click to expand...
Click to collapse
This is easy: No
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
kotidoti said:
Hey there!
I am quite new on this but am getting really tired of my tf700 being sluggish and slow, so I decided to flash a new rom and try to make a NVflash backup first just to be safe. But before doing all this I wanted to make a backup of all my app data which I can do easily with a rooted tablet and a backup app. Problem is, I am on 10.6.1.14.10 right now and I need 10.6.1.14.8 to be able to root it. So I decided that I should root it before making a backup, so here's my question, does a downgrade of stock rom require a clean wipe or wipe data at all? Or is it safe for me to downgrade, install a backup app for app data and then unlock make NVflash-blob and so on?
tl;dr Does downgrading from 10.6.1.14.10->10.6.1.14.8 require a data wipe?
Click to expand...
Click to collapse
When you install the full firmware from Asus, it will wipe everything on you sd before installing. In another word, you will loose your personal data if you downgrade your firmware. Backup everything that you need before downgrading. I am very sure that is the case...
LetMeKnow said:
When you install the full firmware from Asus, it will wipe everything on you sd before installing. In another word, you will your personal data if you downgrade your firmware. Backup everything that you need before downgrading. I am very sure that is the case...
Click to expand...
Click to collapse
That's why he/she doesn't need to wipe anything - the firmware flash will do it
But you make a very good point there....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
That's why he/she doesn't need to wipe anything - the firmware flash will do it
But you make a very good point there....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
How are you? I have been busy lately and don't have time to help out new users, ah I don't know much any way, hahaha.. I do remember that you helped me out a lot when I first got here.. greatly appreciated... :good:
LetMeKnow said:
When you install the full firmware from Asus, it will wipe everything on you sd before installing. In another word, you will loose your personal data if you downgrade your firmware. Backup everything that you need before downgrading. I am very sure that is the case...
Click to expand...
Click to collapse
Ah okay, thanks. That means that I can't do a backup after downgrading. Does an unlock of the tablet wipe data though? The problem I'm having is that I want to save app data before doing anything and the only way to do that without root that I've found is through helium (aka carbon) but I have yet to make Helium work, I've done a backup but not succeeded to restore the app data that I did a backup on.
Is it possible to unlock and install TWRP and do a backup that way? Or does that involve a wipe in any of the steps too?
kotidoti said:
Ah okay, thanks. That means that I can't do a backup after downgrading. Does an unlock of the tablet wipe data though? The problem I'm having is that I want to save app data before doing anything and the only way to do that without root that I've found is through helium (aka carbon) but I have yet to make Helium work, I've done a backup but not succeeded to restore the app data that I did a backup on.
Is it possible to unlock and install TWRP and do a backup that way? Or does that involve a wipe in any of the steps too?
Click to expand...
Click to collapse
Unlock is only touched your bootloader and do not wipe your system or data. You are safe on that case..
Since you are on the latest firmware, you can unlock first and try to learn fastboot to install the latest TWRP. When you have TWRP installed, you can backup your apps from there. Good luck. :fingers-crossed:
LetMeKnow said:
How are you? I have been busy lately and don't have time to help out new users, ah I don't know much any way, hahaha.. I do remember that you helped me out a lot when I first got here.. greatly appreciated... :good:
Click to expand...
Click to collapse
Yes, I noticed you have been busy with your ETs. Good work! And don't hide your light - you know plenty! Finally I have time and leisure and to flash 504
LetMeKnow said:
Unlock is only touched your bootloader and do not wipe your system or data. You are safe on that case..
Since you are on the latest firmware, you can unlock first and try to learn fastboot to install the latest TWRP. When you have TWRP installed, you can backup your apps from there. Good luck. :fingers-crossed:
Click to expand...
Click to collapse
Thank you so much for this information, I'll use Scotts tool (or something like that?) to install twrp without root and then backup and then flash Cromi-x :victory:
LetMeKnow said:
Unlock is only touched your bootloader and do not wipe your system or data. You are safe on that case..
Since you are on the latest firmware, you can unlock first and try to learn fastboot to install the latest TWRP. When you have TWRP installed, you can backup your apps from there. Good luck. :fingers-crossed:
Click to expand...
Click to collapse
Ahem... LMK - what do you mean by backing up apps in TWRP? Making a nandroid? A little different than what he was asking about - no?
---------- Post added at 12:21 AM ---------- Previous post was at 12:05 AM ----------
kotidoti said:
Thank you so much for this information, I'll use Scotts tool (or something like that?) to install twrp without root and then backup and then flash Cromi-x :victory:
Click to expand...
Click to collapse
I do not know what kind of app data you want to back up.
Without using TiBu (for which you would need root) I got a pretty seamless transition by just copying everything in my "/storage/emulated/0" directory to my PC and copying it back after wiping/formatting the data partition and installing the same apps I had before.
Don't know what firmware you are coming from, but if you are on JB 4.2 already and follow the steps you mentioned in your last post, and you do not format your data partition, your app data should be intact anyway even after flashing CROMi-X.
berndblb said:
Ahem... LMK - what do you mean by backing up apps in TWRP? Making a nandroid? A little different than what he was asking about - no?
Click to expand...
Click to collapse
Yes, it works on the same rom but I don't know if you nandroid from stock and restore them on cromi x... Are we talking on the same things? Maybe I misunderstand what is the definition of app data... Any way, if you know a better way, he/she will be more than happy to follow your helps.. That is all know and I will follow this post to learn a better method... thanks..
Use the backup app from ASUS
kotidoti said:
Thank you so much for this information, I'll use Scotts tool (or something like that?) to install twrp without root and then backup and then flash Cromi-x :victory:
Click to expand...
Click to collapse
I just did this last week after the OTA update to 10.6.1.14.10 so I had to downgrade to .08.
I made a app+data backup with the stock backup and moved the backup folder to my microSD card, then used another microSD card to do the downgrade, your card must be formatted fat32, after downgrade restore your backup, all apps and data was fine. Then I unlocked and used Scotts tool to install TWRP, goomanager dose not work, and follow the info in "ASUS TF700T unlock and root JB 4.2.1 stock" the CromiX install went smooth as silk. There are a lot of choices to make during the install I chose the default the first time.
Hope this helps, good luck.
Earlier, I was on the Elix-R ROM. I was going to upgrade to the newest version of it and made a nandroid backup but forgot to make a TiBu of all my apps. Would it be safe and possible for me to restore all of my app data from the nandroid backup by doing an advanced restore of my data?
you were upgrading the rom that you were using.. why would you wipe data?? if you are upgrading a rom, you never have to wipe anything. all you do is flash the updated rom(and gapps) on top of what youre running without wiping anything.
simms22 said:
you were upgrading the rom that you were using.. why would you wipe data?? if you are upgrading a rom, you never have to wipe anything. all you do is flash the updated rom(and gapps) on top of what youre running without wiping anything.
Click to expand...
Click to collapse
I always prefer doing clean flashes of all of the ROMs I run.
absoluterebirth said:
I always prefer doing clean flashes of all of the ROMs I run.
Click to expand...
Click to collapse
cool, your choice it is
i dont remember the last time i actually wiped my n5, if i ever did. lol
simms22 said:
cool, your choice it is
i dont remember the last time i actually wiped my n5, if i ever did. lol
Click to expand...
Click to collapse
also, another question: should making a TiBu and then erasing the system to flash a new ROM affect the backup of apps or no?
You could practice restoring your nandroid backup, then 'dirty' flashing the ROM upgrade straight over the top.
Once you get used to it, dirty flashing isn't so bad. Saves a ton of time. Plus you have the nandroid just in case .
In answer to your query though, you can extract apps and app data using the appropriately named Nandroid Manager. I used it before on a now sold Nexus 7 when it decided to not boot up but could get to recovery and make a backup.
absoluterebirth said:
Earlier, I was on the Elix-R ROM. I was going to upgrade to the newest version of it and made a nandroid backup but forgot to make a TiBu of all my apps. Would it be safe and possible for me to restore all of my app data from the nandroid backup by doing an advanced restore of my data?
Click to expand...
Click to collapse
Yes. Its the same as having never wiped in the first place
absoluterebirth said:
also, another question: should making a TiBu and then erasing the system to flash a new ROM affect the backup of apps or no?
Click to expand...
Click to collapse
Eh? I don't understand the problem
Sent from my Nexus 5 using Tapatalk