I discovered the hard way not to include the System Image when backing up with TWRP. But it seems I overlooked the Vendor Image. Turns out all of the backups I've made for the last few months have been worthless because I neglected to uncheck it. My question is why are those two options even included when they trash the backup?:crying:
lewmur said:
I discovered the hard way not to include the System Image when backing up with TWRP. But it seems I overlooked the Vendor Image. Turns out all of the backups I've made for the last few months have been worthless because I neglected to uncheck it. My question is why are those two options even included when they trash the backup?:crying:
Click to expand...
Click to collapse
Not sure what you mean - simply UNselecting them when restoring the backup should be the same as not backing them up at all.
Nimueh said:
Not sure what you mean - simply UNselecting them when restoring the backup should be the same as not backing them up at all.
Click to expand...
Click to collapse
That assumes I knew what was causing the problem in the first place. Had I known then, what I know now, I would never have included the vendor image in the backup and wouldn't need to uncheck it in the restore. All I knew at the time was that when I had problems with the latest release and tried to restore the backups, they all failed. So I erased them and started from scratch. :crying: It wasn't until later I figured out the problem. That's why I'm warning others.
lewmur said:
That assumes I knew what was causing the problem in the first place. Had I known then, what I know now, I would never have included the vendor image in the backup and wouldn't need to uncheck it in the restore. All I knew at the time was that when I had problems with the latest release and tried to restore the backups, they all failed. So I erased them and started from scratch. :crying: It wasn't until later I figured out the problem. That's why I'm warning others.
Click to expand...
Click to collapse
But there are reasons someone would want to back up those partitions, so a general statement saying they shouldn't be in a backup is simply wrong.
I've always read up on a new device, checked XDA, asked in Telegram groups to find out exactly what to backup and/or restore. You can't blame the maker(s) of TWRP for you not doing your research
Nimueh said:
But there are reasons someone would want to back up those partitions, so a general statement saying they shouldn't be in a backup is simply wrong.
I've always read up on a new device, checked XDA, asked in Telegram groups to find out exactly what to backup and/or restore. You can't blame the maker(s) of TWRP for you not doing your research
Click to expand...
Click to collapse
I can blame anyone I care to blame. You have your opinion and I have mine. I have been using TWRP backup for years and never had a need for those options and don't have one now. And I have used XDA for years and have never seen ANYONE state a need or reason for them. As far as I'm concerned, your remarks serve no purpose at all except to irritate me.
@lewmur You seem to disagree with the advice given, but as far as I can see @Nimueh is only trying to clarify things and help. Your remarks come off as quite rude, so could you please dial that down a few notches before things get out of hand. I understand that you are frustrated for having gone through this, but I advice you to look at this experience as you having learned something new. And every day you learn something new is a good day.
I'll add that I have many times benefited from backing up the system partitions on my devices when testing different things. Every device might be different though, so the advice of doing research is not a bad one. Luckily for the next user you have now been able to share your experience and others can hopefully benefit from your warning.
Remember to keep things friendly on the forum. That way everyone involved benefits from the exchange.
Cheers
Didgeridoohan
Forum Moderator
Didgeridoohan said:
@lewmur You seem to disagree with the advice given, but as far as I can see @Nimueh is only trying to clarify things and help. Your remarks come off as quite rude, so could you please dial that down a few notches before things get out of hand. I understand that you are frustrated for having gone through this, but I advice you to look at this experience as you having learned something new. And every day you learn something new is a good day.
I'll add that I have many times benefited from backing up the system partitions on my devices when testing different things. Every device might be different though, so the advice of doing research is not a bad one. Luckily for the next user you have now been able to share your experience and others can hopefully benefit from your warning.
Remember to keep things friendly on the forum. That way everyone involved benefits from the exchange.
Cheers
Didgeridoohan
Forum Moderator
Click to expand...
Click to collapse
I found HIS remarks to be insulting and of no help at all. Just how does saying MY warning is of no use, help anyone?
edit: BTW, it wasn't backing up the system PARTITION that was a problem. It was backing up the system IMAGE. How many times have you found THAT to be useful???? Much less the vendor IMAGE??
lewmur said:
I found HIS remarks to be insulting and of no help at all. Just how does saying MY warning is of no use, help anyone?
edit: BTW, it wasn't backing up the system PARTITION that was a problem. It was backing up the system IMAGE. How many times have you found THAT to be useful???? Much less the vendor IMAGE??
Click to expand...
Click to collapse
Nowhere does @Nimueh claim that your warning is of no use or doesn't help anyone. Their first post is simply about a clarification that it is possible to not restore all parts of a backup.
You might want to read the TWRP faq on how the backup function works:
https://twrp.me/faq/whattobackup.html
As far as I'm concerned, as long as any further discussions are kept friendly and respectful, this is a closed chapter.
Happy flashing.
Didgeridoohan
Forum Moderator
Related
Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!
I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.
Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?
is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O
Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
im ready to get this done what have we got so far?
About 140 pages of failed attempts.
well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing
binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny
doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.
jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.
Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.
Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"
Did you run the simlock option in the bootloader, and it passed
binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.
I'm curious as to whether anyone has successfully restored one of the recently posted backups to the point where you can take a OTA update. For that matter, has anyone successfully restored to the point where you can boot into the system and use it. We have various people who fear that they've bricked.
Has anyone who can't get their phone working returned it? And if so, has Alcatel accepted it and given you your money? It may be too soon to know on this, I realize.
I don't need to change anything at the moment, but I have some trepidation about doing a restore out of fear that I'll brick my phone or something close to it. I don't want to be on 5.02 for as long as I have the phone.
It would be nice if Alcatel would release system images. I'm not holding my breath, though. Has anyone contacted them to make that request? Any response from them about this?
My purpose here is to get, for all of us, a sense of what works and what doesn't, whether or not people should feel confident about rooting their phone, etc.
As it was mentioned, their support is lacking any usefull info on any question (my experience writing to them from different email accs) or they aren't willing to share.. Too bad I would say..
source code will be given, but i think after next big update. Releasing source code of lauch firmware does not make any sense.
I have spoken with Alcatel support here in Czech republic and they said, they will sure release the source code and that the updates will come every 4-6 weeks.
And for the restore thing. You can always root your device, make backup, and when update is online, just backup your apps (titanium backup), restore the system., unroot, update. Then root, and restore your apps using titanium backup. Sounds complicated, but its matter of one hour maximum.
DallasCZ said:
source code will be given, but i think after next big update. Releasing source code of lauch firmware does not make any sense.
I have spoken with Alcatel support here in Czech republic and they said, they will sure release the source code and that the updates will come every 4-6 weeks.
And for the restore thing. You can always root your device, make backup, and when update is online, just backup your apps (titanium backup), restore the system., unroot, update. Then root, and restore your apps using titanium backup. Sounds complicated, but its matter of one hour maximum.
Click to expand...
Click to collapse
I had a disaster of sorts yesterday that ended up answering a lot of the questions I had in the OP. I had some concerns, based on experiences a few had posted here, that restoring the backups posted in another topic weren't a sure thing. I got into a situation where I had to start over again from scratch. I wiped my data from TWRP, then restored the UER0 backup. It appeared that I was back to factory status. TWRP even prompted me about whether or not I wanted to maintain a state where I'd be able to take an OTA or compromise it to root. And the updater on the phone worked, too, though I was running the latest and there was no need for it to download anything. But it gave all the right messages. So getting into a state to receive an OTA or return the device seems very doable.
Foolishly, I hadn't done a nandroid or Titanium backup, yet, so I had to do a lot of this the hard way, other than that I copied the contents of my sdcards to my computer. But, yes, now I've done a nandroid and a Titanium backup of the reconfiguration and am well positioned to make a quick recovery should I have to do this again or when the next OTA arrives. I agree that once set up right with backups, that the whole process is less daunting than it would seem on the surface.
i don't get the point.. you just want to say, that you have mafe a restore of a system successfully? great.
DallasCZ said:
i don't get the point.. you just want to say, that you have mafe a restore of a system successfully? great.
Click to expand...
Click to collapse
I started this topic to get feedback from people on whether they'd successfully restored the system with the backups that have been provided here on the forum. Some had expressed that their attempts had failed and they feared that they were bricked. If there are problems inherent in these devices for whatever reason with respect to this, users here should know about them and we should be able to find out whether or not those problems can be remedied by one protocol or another. I was concerned that people with rooted phones, myself included, were potentially facing problems that would prevent us from getting OTA updates, among other things. Nobody came forward here to respond to my questions. That's OK. No one is obligated. But the topic has had 344 views, so some people must be curious. So I wanted to let people know that the UER0 backup does work, at least for me.
Others have had trouble, possibly even when trying to restore from TWRP in what they think are appropriate ways. I'm not clear exactly why, but it would be great to be able to help them, if possible. Nobody wants their new phone to be bricked. Everyone wants to know what works and what doesn't when they're faced with starting over again or getting set to take an OTA. These are new, low priced phones. There are no system images available from the manufacturer. People have generously done all they could here to work around that. We don't have the resources available to us that a Nexus phone does, or some of the others that have larger sales and communities here. Without data to show whether the efforts on XDA are succeeding or not, it's harder to act with confidence. So I'm providing some.
That's the point.
i think if you flash the corresponding system image there should be no problem. Twrp backup is device specific since it allows to backup also persiat partitions with device specific imei. I just unrooted the phone and the chceck for updates worked as it should.
So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.
Really? No one?
bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.
Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse
I've researched this thoroughly, but find some ambiguities that still remain among the many tutorials. While many, including @Heisenberg in his extremely helpful 6P guide, says to backup only system/boot/data, I see elsewhere to backup system/boot/data/vendor @Heisenberg even says so in one thread, which is at odds with what appears in his guide).
To complicate matters, it is unclear what "system" and "vendor" above refer to, as TWRP lists both a "system" and "system image" and a "vendor" and "vendor image".
**So, simply put: what exact partitions do I need to backup in order to be able to restore a fully functioning instance of my current ROM, even if I'm restoring from another ROM or stock?** I would think a vendor partition would need to be backed up, given that I may be restoring from a ROM within a different vendor image currently in effect.
Many, many thanks in advance!
Zwitterion said:
I've researched this thoroughly, but find some ambiguities that still remain among the many tutorials. While many, including @Heisenberg in his extremely helpful 6P guide, says to backup only system/boot/data, I see elsewhere to backup system/boot/data/vendor @Heisenberg even says so in one thread, which is at odds with what appears in his guide).
To complicate matters, it is unclear what "system" and "vendor" above refer to, as TWRP lists both a "system" and "system image" and a "vendor" and "vendor image".
**So, simply put: what exact partitions do I need to backup in order to be able to restore a fully functioning instance of my current ROM, even if I'm restoring from another ROM or stock?** I would think a vendor partition would need to be backed up, given that I may be restoring from a ROM within a different vendor image currently in effect.
Many, many thanks in advance!
Click to expand...
Click to collapse
System/Boot/Data/Vendor are all you need. I've never used the image options so I don't know if they work. Backing up the Vender partition would only be needed if you are restoring from a Rom with a different vendor. It's a small file so I always back it up anyway. One thing to keep in mind though is that you could save yourself some trouble if you delete your lock screen pin and finger print before making a backup. TWRP has been known to have issues restoring those when coming from another Rom. Although there is a work around if that happens.
Zwitterion said:
To complicate matters, it is unclear what "system" and "vendor" above refer to, as TWRP lists both a "system" and "system image" and a "vendor" and "vendor image".
**So, simply put: what exact partitions do I need to backup in order to be able to restore a fully functioning instance of my current ROM
Click to expand...
Click to collapse
Same question here. which one should I backup?
system
vendor
or
system image
vendor image
?
Zwitterion said:
I've researched this thoroughly, but find some ambiguities that still remain among the many tutorials. While many, including @Heisenberg in his extremely helpful 6P guide, says to backup only system/boot/data, I see elsewhere to backup system/boot/data/vendor @Heisenberg even says so in one thread, which is at odds with what appears in his guide).
To complicate matters, it is unclear what "system" and "vendor" above refer to, as TWRP lists both a "system" and "system image" and a "vendor" and "vendor image".
**So, simply put: what exact partitions do I need to backup in order to be able to restore a fully functioning instance of my current ROM, even if I'm restoring from another ROM or stock?** I would think a vendor partition would need to be backed up, given that I may be restoring from a ROM within a different vendor image currently in effect.
Many, many thanks in advance!
Click to expand...
Click to collapse
System and Data all you need to backup.
murphyjasonc said:
System/Boot/Data/Vendor are all you need. I've never used the image options so I don't know if they work. Backing up the Vender partition would only be needed if you are restoring from a Rom with a different vendor. It's a small file so I always back it up anyway. One thing to keep in mind though is that you could save yourself some trouble if you delete your lock screen pin and finger print before making a backup. TWRP has been known to have issues restoring those when coming from another Rom. Although there is a work around if that happens.
Click to expand...
Click to collapse
Many thanks for this. Exactly the sort of insight I was looking for. And you have successfully restored your phone with backups made in the above manner?
Zwitterion said:
Many thanks for this. Exactly the sort of insight I was looking for. And you have successfully restored your phone with backups made in the above manner?
Click to expand...
Click to collapse
Yeah. I'm constantly tweaking my phone or trying new Roms. I just make sure I have a fresh backup before I make a change. If something doesn't go right which seems to happen a lot I just boot up in TWRP and restore. No harm done and I try again. Just make sure you have the most updated version of TWRP. 3.1.1 I believe and you shouldn't have any trouble.
murphyjasonc said:
Yeah. I'm constantly tweaking my phone or trying new Roms. I just make sure I have a fresh backup before I make a change. If something doesn't go right which seems to happen a lot I just boot up in TWRP and restore. No harm done and I try again. Just make sure you have the most updated version of TWRP. 3.1.1 I believe and you shouldn't have any trouble.
Click to expand...
Click to collapse
You rock, thanks! Running Pure Nexus, want to try Nitrogen.
Zwitterion said:
You rock, thanks! Running Pure Nexus, want to try Nitrogen.
Click to expand...
Click to collapse
Nitrogen is an excellent Rom. I highly recommend it. It's been my go to Rom for awhile. I've been trying Aquarius for the last couple of weeks and it seems to perform equally as well.
murphyjasonc said:
Nitrogen is an excellent Rom. I highly recommend it. It's been my go to Rom for awhile. I've been trying Aquarius for the last couple of weeks and it seems to perform equally as well.
Click to expand...
Click to collapse
Have you tried Pure Nexus? Any thoughts on how it compares to Nitrogen? Wondering whether I should spend the energy to try out Nitrogen.
Zwitterion said:
Have you tried Pure Nexus? Any thoughts on how it compares to Nitrogen? Wondering whether I should spend the energy to try out Nitrogen.
Click to expand...
Click to collapse
Yeah PN is the first rom I ever tried. I've gone back to it several times. It's one of the most stable Roms available but in my opinion it lacks a lot of the customization that Nitrogen has. Nitrogen typically has updates more often also.
murphyjasonc said:
Yeah PN is the first rom I ever tried. I've gone back to it several times. It's one of the most stable Roms available but in my opinion it lacks a lot of the customization that Nitrogen has. Nitrogen typically has updates more often also.
Click to expand...
Click to collapse
Sweet. I'm going to go for it. Thanks for all the help and insight, man!
Which things should I select to backup in twrp?
Last time when I restored the backup I got stuck in the bootloader.
ZaKh10 said:
Which things should I select to backup in twrp?
Last time when I restored the backup I got stuck in the bootloader.
Click to expand...
Click to collapse
Everything!
This is the question that pisses me off every time I see it. Not because the OP asked it,,,but because no one ever really gives a good answer. Rather they give what they do. There are many devs out there who spend a crap load of time making TWRP and it would just be nice if they spoke up and ended this debate. Is it system_images, vendor_image, boot, and data? Some say no Vendor_image because that causes problems. Others say backup everything,,,well why backup everything and take up all that space if you dont need to? I backed up everything and got stuck in a bootloop when I restored. I have been doing android since day one and never seen so many answers to one question. Can just one TWRP dev speak up and give us a definitive answer, or do they not know as well?
Archangel said:
This is the question that pisses me off every time I see it. Not because the OP asked it,,,but because no one ever really gives a good answer. Rather they give what they do. There are many devs out there who spend a crap load of time making TWRP and it would just be nice if they spoke up and ended this debate. Is it system_images, vendor_image, boot, and data? Some say no Vendor_image because that causes problems. Others say backup everything,,,well why backup everything and take up all that space if you dont need to? I backed up everything and got stuck in a bootloop when I restored. I have been doing android since day one and never seen so many answers to one question. Can just one TWRP dev speak up and give us a definitive answer, or do they not know as well?
Click to expand...
Click to collapse
This X 1,000!
I've made different backups checking off different things to back up and I'm terrified of having to restore something! Let's just say I'm extra careful of any mod I flash in case I fu-- something up! Haven't had to restore a backup yet and will be shaking when I have to. I have read so much about it, but there is no clear answer and much of it is confusing. And maybe it's the blond girl in me but I remain confused about the A and B partitions - something else I need to read up on.
Wish TWRP devs would have an official message on what to back up and restore! :good:
exactly right! Plus I LOVE the people who say well just back up what they do and it was a fluke that it worked for them. I am like you now, I am very careful what mods I use because I know I will have to start over from scratch and redo my phone. For me I just use TWRP for flashing zips now thats all.
darbylonia said:
This X 1,000!
I've made different backups checking off different things to back up and I'm terrified of having to restore something! Let's just say I'm extra careful of any mod I flash in case I fu-- something up! Haven't had to restore a backup yet and will be shaking when I have to. I have read so much about it, but there is no clear answer and much of it is confusing. And maybe it's the blond girl in me but I remain confused about the A and B partitions - something else I need to read up on.
Wish TWRP devs would have an official message on what to back up and restore! :good:
Click to expand...
Click to collapse