Pardon my ignorance on the subject, i have not dealt with nandroid to much in the past. I have been pushed the new monthly update, and I am rooted. (I Know I cannot update while rooted! and am fully prepared to flash the files) My question is this, I have made a nandroid backup using TWRP, it is obviously for a different going to be for build, after I flash the updated files. I get that I can flash that and can go back to the previous build, but is there anyway to just restore apps from a nandroid backup, and not have to go back to the previous build? Or would I have better luck using something like Titanium w/ a pro key?
Thanks
FireMedic1234 said:
Pardon my ignorance on the subject, i have not dealt with nandroid to much in the past. I have been pushed the new monthly update, and I am rooted. (I Know I cannot update while rooted! and am fully prepared to flash the files) My question is this, I have made a nandroid backup using TWRP, it is obviously for a different going to be for build, after I flash the updated files. I get that I can flash that and can go back to the previous build, but is there anyway to just restore apps from a nandroid backup, and not have to go back to the previous build? Or would I have better luck using something like Titanium w/ a pro key?
Thanks
Click to expand...
Click to collapse
You can flash just your data from backup. On the restore screen uncheck system and boot so that only data is checked. Will work on minor updates. Wouldn't do it if updating builds such as L to M where they don't have the same base.
Ok so going from Lollipop to Marshmallow is a no but how about being on LMY48I and going to LMY48M. I'm sorry I just want to make sure I know what I am doing before I mess it up.
FireMedic1234 said:
Ok so going from Lollipop to Marshmallow is a no but how about being on LMY48I and going to LMY48M. I'm sorry I just want to make sure I know what I am doing before I mess it up.
Click to expand...
Click to collapse
It's fine. LMY48M is just a security update and not a base change.
Related
I'm Currently running android revolution hd 7.1, I notice a huge signal degradation so I guess I need to go back to stock.
Is there any an go back to fully stock?
I've searched for RUU, but they do not have 1.29.707 WWE, and mandrels doesn't seems to work on me (it just restored to default setting for ARHD)
Any help is appreciated
Friedtofux said:
I'm Currently running android revolution hd 7.1, I notice a huge signal degradation so I guess I need to go back to stock.
Is there any an go back to fully stock?
I've searched for RUU, but they do not have 1.29.707 WWE, and mandrels doesn't seems to work on me (it just restored to default setting for ARHD)
Any help is appreciated
Click to expand...
Click to collapse
You mean you didn't create a nandroid backup of your device before flashing a custom ROM? You should always do that. I think you'll have to wait until a RUU is released, or if someone is willing to post a nandroid of their device
I know theres a stock zip found here http://forum.xda-developers.com/showthread.php?t=2224752. Just flash it and you'd be back to stock. Your bootloader would still show as tampered. I did it and went back to stock as well.
Rumball said:
You mean you didn't create a nandroid backup of your device before flashing a custom ROM? You should always do that. I think you'll have to wait until a RUU is released, or if someone is willing to post a nandroid of their device
Click to expand...
Click to collapse
I am still new to android, I thought a simple backup of apps and data is sufficient. Do you have any idea how long will it be released?
Totally regretted...
shief24 said:
I know theres a stock zip found here http://forum.xda-developers.com/showthread.php?t=2224752. Just flash it and you'd be back to stock. Your bootloader would still show as tampered. I did it and went back to stock as well.
Click to expand...
Click to collapse
Hey thanks for your help, but this is for build 1.29.401.13 which is not for my region, which is 1.29.707.3...
Friedtofux said:
I am still new to android, I thought a simple backup of apps and data is sufficient. Do you have any idea how long will it be released?
Totally regretted...
Click to expand...
Click to collapse
Ya, a Nandroid takes a complete mirror copy of your device (excluding any files on your internal storage like music, pictures, and videos) and saves it in a single file. You'll want to get in the habit of making these before flashing custom ROMs. The backup apps just saves the apps you've installed from the Google Play Store as well as SOME of it's configuration data.
I would post a request to see if someone with the same regional device as yours could upload a nandroid. Give your country and operator details...maybe someone has a nandroid you can restore to.
Rumball said:
Ya, a Nandroid takes a complete mirror copy of your device (excluding any files on your internal storage like music, pictures, and videos) and saves it in a single file. You'll want to get in the habit of making these before flashing custom ROMs. The backup apps just saves the apps you've installed from the Google Play Store as well as SOME of it's configuration data.
I would post a request to see if someone with the same regional device as yours could upload a nandroid. Give your country and operator details...maybe someone has a nandroid you can restore to.
Click to expand...
Click to collapse
Singapore, Singtel. I wouldn't expect to find any nandroid from my country given the small number of users.
I guess my my region for HTC Build is 1.29.707.X
Thanks for your help. I have learnt from my experience...:crying:
Does anyone know about HTC's warning about the DRM keys being lost when you flash custom roms? I'm thinking about getting the Dev edition but is anything lost when you flash back to stock or another rom? I know with the Xperia Z, if you unlock the bootloader you'll lose the Bravia engine.
Singapore Stock backup is here -> http://forums.hardwarezone.com.sg/h...ot-recovery-htc-one-1-29-707-3-a-4188771.html
I created using TWRP so you have to switch to it instead of CWM first
v-b-n said:
Singapore Stock backup is here -> http://forums.hardwarezone.com.sg/h...ot-recovery-htc-one-1-29-707-3-a-4188771.html
I created using TWRP so you have to switch to it instead of CWM first
Click to expand...
Click to collapse
Is it for singtel?
When should you do a full wipe when installing a custom rom and when is it ok to dirty flash? Can someone please explain?
Sent from my HTC One using xda app-developers app
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
lampel said:
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
easyrabbit said:
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
Click to expand...
Click to collapse
What rom are you using?
CYNiCAL2KX said:
What rom are you using?
Click to expand...
Click to collapse
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
Click to expand...
Click to collapse
Sorry I meant ViperOne...
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
Sorry I meant ViperOne...
Click to expand...
Click to collapse
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
Thank you very much for the info. So now I understand what the base is. Aside from time or laziness I would think that doing a full wipe is the way to go. Maybe I am wrong but I would rather not take chances.
Right now Iam currently having some issues. I basically did a dirty flash of the same version I am on to clear the theme and it went wrong. It never came back up after an hour in the "starting applications" state. After that I got back in to recovery (TWRP) and did full wipes and installs. They seem to go OK but then the android setup crashes right after the "name your device" part and the launcher wont start (chose Nova). Everything just hangs. I reboot but then it just hangs. I just did my nandroid restore and I am back up and running but not sure what is going wrong. I tried the install a few times with different options but everytime the setup part crashes. So my simple question is now another full blown issue haha.
I love this board tho, everyone is so helpful. One day I hope to be the one giving the advice.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
easyrabbit said:
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
Click to expand...
Click to collapse
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
CYNiCAL2KX said:
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
Click to expand...
Click to collapse
Thank you very much. I have heard back and forth on wiping the system but had never done it till now. I am still not sure what was happening. in my initial installs I allways removed sense and used Nova. The last time I left Sense and most off the apps. I also 're-downloaded the zip. it worked like a charm. soon I will start investigating kernals and updating firmwae and antennas. Will play with the basics for a while first tho. eventually I would like to try my own. However the bar is set high with venomone.
I am now dealing with sense which is ok bit for me Nova is as close to perfect a launcher for me. still investigating battery lifevetc but will probably do another flash removing sense. venomone fixed everything I didnt like about it for the most part but I love to be able to swipe up or down anywhere to get quickbar and app drawer... still testing tho, I have a full life but definitely want to contribute here... my new obsession.
Ok so I took the OTA lollipop update, rooted and the phone was rocking. Installed TWRP backed up including cache and boot. I did factory reset and restored from backup file and I couldn't get past the boot animation. I downloaded these files http://forum.xda-developers.com/mot...g-lxe22-39-6-pure-edition-stock-boot-t2940437 and ran these commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Then, I lost the boot animation, only had the boot image. Then a lot of mfastboot stuff and I am back at on a fresh unrooted KK...... Any ideas wtf happened? Was it TWRP, restoring the cache or what? This is my fist no Sammy device so it's a learning experience.
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
dobbs3x said:
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
TWRP has been horribly quirky for me on my Moto X. I can't even get it to boot into recovery half the time, among other things.
Sent from my iPhone 6 using Tapatalk
cam30era said:
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
Click to expand...
Click to collapse
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
dobbs3x said:
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
Click to expand...
Click to collapse
Aahh. Good point. I've made a backup and flashed .zips. But have not tried to restore a backup. Thanks for the heads up.
I now know the restore of TWRP backups is what did it. I have successfully recreated the issue twice with the exact same results.
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
Currently what I have done is just:
- unlocked the bootloader via moto site.
- fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
- installed/updated SuperSU via Playstore
- installed updated Binary via SuperSU
Back when I had the Nexus 5, I would change the DPI with DPI changer, but on some ROMs, flashing an updated GAPPS/etc would break the ROM, because of the DPI Changer... (I would just do a NAND restore/TWRP restore) How can I full-proof my current setup so that when I mess up I can always have something to fall back on?
From what I read above flashing TWRP is no ideal yet as NAND backups don't restore? is that right?
I'm just running stock Bootloader/Recovery right now, and I'm not sure how to fail-proof myself.
If I stick to default bootloader/recovery can I just flash default KitKat/Lollipop image to restore/fix any issues?
Lastly, on boot, that "Unlocked Bootloader" message comes up, it's not the worst, but from what I understand people flash a bootloader/recovery that removes that warning?
Thanks for help.
Shemploo said:
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
.
Click to expand...
Click to collapse
Edit build.prop :good:
TigerDNA said:
Edit build.prop :good:
Click to expand...
Click to collapse
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Shemploo said:
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Click to expand...
Click to collapse
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
TigerDNA said:
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
Click to expand...
Click to collapse
Maybe someday, but right now I do not have time to learn, and the few times I tried to learn to program was a long time ago and it did not go well.
I would certainty like to go into Android programming, but for my short time needs, I guess I'm wondering how, if anything.. one can do to have an easy fix to breaking the OS/ROM, since TWRP back-ups don't seem to work for this device right now.
What is hard brick?, can anything I mess up software wise be restored via flashing factory images?
So I'm currently trying to flash Liquidsmooth to my TMO N4, already rooted it and got TWRP. I went to install in recovery mode after wiping the partitions and chose the LS-LP-v4.0-2015-01-24-liquid_trltetmo.zip file but it hasn't been doing anything. It says its flashing the file but its been like this for a few hours and there's no progress on the download bar, was just checking to see if I could get any assistance.
I don't wanna risk turning off the phone during the flash to try and get back into recovery mode to run my nandroid backup unless absolutely necessary.
What exactly did you wipe.
BAD ASS NOTE 4
I wiped the cache, dalvik, data and system partitions like most guides say to.
Won't hurt anything to pull battery and try again. Just rewipe and try flashing again.
If it fails again. My suggestion would be to restore your nandroid, and verify the MD5 of the file you downloaded.
Sent from my SM-N910T using XDA Free mobile app
I was hesitant in pulling the battery to avoid bricking the phone but if that's the only way. I was told the download might have been bad but I don't see how considering it downloaded fine and the size fits. I might try a different rom and see if that changes anything.
I would odin back to stock and start over. Make sure reactivation lock is not checked off .
BAD ASS NOTE 4
Alright, I'll probably try that once my phone finishes restoring my backup. Just to be sure since I seemed to have gotten some mixed info, does the latest LiquidSmooth ROM support Lollipop 5.0.1 or is the latest download on the forums still for KitKat? I was thinking I might have to switch to the CMremix ROM instead.
Thanks for all the help so far by the way.
I be honest I don't know anyone who flashed that rom . I think it is still in beta side of things. Best bet would be to ask in the thread about flashing issues.
BAD ASS NOTE 4
---------- Post added at 10:13 AM ---------- Previous post was at 10:07 AM ----------
Enilo said:
Alright, I'll probably try that once my phone finishes restoring my backup. Just to be sure since I seemed to have gotten some mixed info, does the latest LiquidSmooth ROM support Lollipop 5.0.1 or is the latest download on the forums still for KitKat? I was thinking I might have to switch to the CMremix ROM instead.
Thanks for all the help so far by the way.
Click to expand...
Click to collapse
Ok so that is running on 4.4.4. If u already updated ur baseband and firmware that won't work. Stick with offical stock and check and use it. Make sure ur good then flash but not that rom. U would have to revert. My 2 cents it not worth it going all the back and forth.
BAD ASS NOTE 4
Thanks, a least now I know what the issue most likely was. Finished the restore and checked my system, gonna rewipe the partitions then try and flash CMremix since its said to be supported.
Hey everyone thanks to @BIOKNOX who recently helped me get my Note 9 working again, I want to make a complete software backup. A complete IMAGE of the current software so just in case something goes wrong, I could have somewhere to come back to. So I need help with that. I use twrp will that work? Is their a better software? Will Twrp work the way i want it to? Thank you in advance
BlackJackN9 said:
Hey everyone thanks to @BIOKNOX who recently helped me get my Note 9 working again, I want to make a complete software backup. A complete IMAGE of the current software so just in case something goes wrong, I could have somewhere to come back to. So I need help with that. I use twrp will that work? Is their a better software? Will Twrp work the way i want it to? Thank you in advance
Click to expand...
Click to collapse
Since you're using TWRP then that's the best. Make a backup of all partitions. If there is a problem while restoring try to restore one by one, maybe some cannot be restored, can't say nothing here. But a nandroid TWRP backup is the way to go, yes.
koragg97 said:
Since you're using TWRP then that's the best. Make a backup of all partitions. If there is a problem while restoring try to restore one by one, maybe some cannot be restored, can't say nothing here. But a nandroid TWRP backup is the way to go, yes.
Click to expand...
Click to collapse
You made me really happy then really sad. xD
anyways thanks
ill try them both.
koragg97 said:
Since you're using TWRP then that's the best. Make a backup of all partitions. If there is a problem while restoring try to restore one by one, maybe some cannot be restored, can't say nothing here. But a nandroid TWRP backup is the way to go, yes.
Click to expand...
Click to collapse
Hey, I backed up the file in steps, cause I did not had a big SD card at hand. The problem I am facing is I cannot backup system image. How can I backup that file? Is it important? Btw all back ups are done using twrp and I just realised that I could have just backed everything up in the phone storage and then copied it all as one file on to my laptop.
BlackJackN9 said:
Hey, I backed up the file in steps, cause I did not had a big SD card at hand. The problem I am facing is I cannot backup system image. How can I backup that file? Is it important? Btw all back ups are done using twrp and I just realised that I could have just backed everything up in the phone storage and then copied it all as one file on to my laptop.
Click to expand...
Click to collapse
I haven't had any experience with TWRP or such things on phones newer than the Galaxy S5. I don't see a point to root or tinker with my Note 9 as it's perfect stock so can't really test if i can backup the system image myself. All things are important in a backup, is it grayed out or something? I'd always do a full 1 backup though, not in parts. Seems easier to restore later.