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.
Related
Just my $0.02
I don't necessarily think it is a good idea to delete stuff from /system after applying the OTA. From what I understand, there is no (known) way to revert to the original firmware, and if you happen to delete something on /system POST-OTA, there is a very good chance that you will not be able to apply future updates, due to the recovery not finding the file(s) necessary to patch. Same issue people who deleted Google Goggles had prior to this OTA, however, in this case, we did have the escape route of flashing the stock firmware, then applying the OTA...
Best bet at the moment:
Temp-root via VISIONary, fire up adb shell or a terminal:
Code:
# pm disable [i]package_name[/i]
Or use the "freeze" function in Titanium Backup.
Thanks, rmk40!
yea thats what i was thinking also. paulobrien made a theard about titanium removing apps from /system but how would your be able to revert in case of an update?
I dont think you can because we cant downgrade
I agree.
Besides, using "pm disable <package_name>" via adb shell is just as effective as removing any app, without any of the risks.
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
wheeliest said:
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
Click to expand...
Click to collapse
it was easy to revert....THIS TIME. from what i can gather, the g2 isnt able to be downgraded. witht he last ota...people flashed the base over to get the apps back to original....but next time you wont be able to flash the same file cuz it'll be considered a downgrade.
i'm definatlely gunna stay clear of /system til the great devs we rely so much upon finally scream victory against HTC/eMMC. then i'll be back to the heavy mods.
the stock rom isnt bad. its vinilla, and the hardware of the g2 makes up for it. everything seems to fly without a hiccup of anykind.
wheeliest said:
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
Click to expand...
Click to collapse
With the quality of your thoughts HTC wouldn't hire you to be their janitor. Good luck with the next OTA!
wheeliest said:
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
Click to expand...
Click to collapse
What did you gain from removing them, though?
Nobody is saying you shouldn't remove them because it is naughty or immoral or icky. It's true that we have the capability of removing the apps if we want to, and that is a good thing. But, in practice, this interferes with upgrading when fixes come out and it may be a lot more of a hassle the next time than we saw with this OTA(*). So, for now, until permanent root comes along and we can flash whatever ROM we want, it's not a smart thing to do when there are other ways to achieve the same ends.
It would be one thing if you actually got the space back, but since the pre-installed apps are on a fixed partition that you don't need extra space on, removing them provides no more value than disabling them.
(*) I'd be curious, though, to know if anyone has proven that flashing the original stock system doesn't work after the OTA. As far as I know the Android update mechanism doesn't enforce strictly increasing ROM versions (people were flashing the original G1 ROM after several updates had happened - it was the standard way to root the device). All it would take would be one guinea pig to do the fastboot reflash of the original ROM on top of their OTA'd device to know if it will work.
Minimally, though, having to reflash the original ROM in order to add a patch or update means your phone gets wiped and you have to deal with the hassle of restoring it to working order - hardly a decent tradeoff if disabling the apps does the trick with fewer ramifications...
havikx said:
but next time you wont be able to flash the same file cuz it'll be considered a downgrade.
Click to expand...
Click to collapse
Being a devil's advocate here - is that really true?
Other Android phones have been able to flash back to prior ROMs in the past (the standard way to root the G1 was to flash one of the original shipped ROMs and it would flash regardless of which version you were on).
Having to flash the original ROM does reset your phone and that, to me, is a more obvious and practical drawback to removing built-in apps, especially if disabling them is just as easy (and you don't get any useable file space back when you remove them anyway).
Someone in the G2-Root channel tried and it failed. The phone checked to see what version it was flashing and if it was older than what is already on it, it will fail.
From what I remember... the hardboot/spl version has to be different (older) in order for it to fail... of course this is speculation.
In fact the hardboot version hasn't changed so it should revert. Weird that it failed... I don't understand why it would.
After applying the OTA manually, I just tried to flash back to the pre-OTA stock using fastboot.
I get an error:
FAILED (remote: 43 main version check fail)
**** lol. I've already used titanium backup to remove that damn photobucket app that kept posting notifications on why I should use their crappy service. Any hope for me?
Sent from my T-Mobile G2 using XDA App
the truth is, in 6 months there will be a better phone... and ill end up getting it.. and if worse comes to worse, i can pan up $130 for a new g2...
i had to do alot of my **** to my phone inorder to apply the ota update.... i wil not remove one app of the phone until its rooted
I don't think it will come to that. I am currently trying to re-apply to OTA to see if it will just reinstall the missing apps and get it back to where it was.
If that doesn't work, I'll wipe through recovery, and then apply the OTA.
After that, though, I'll wait until someone smarter does something about it.
Will post results in a few.
EDIT: The OTA applied just fine, but the missing apps were not restored. Hopefully, since the OTA applied, even with missing apps, future OTAs will also apply.
Another solution would be for someone to extract the ROM and apply the full ROM, as opposed to just the OTA patch.
Already tried. You can't use hboot to go back to 1.19, you can't you fastboot-windows, and factory restore just deletes your data XD
Looks like I'm totally screwed. I hope paul (or anyone for that matter) finds a solution. I really don't want to be stuck with a phone that can't update, all because T-Mobile decided that they really liked photobucket.
ibemad1 said:
Already tried. You can't use hboot to go back to 1.19, you can't you fastboot-windows, and factory restore just deletes your data XD
Looks like I'm totally screwed. I hope paul (or anyone for that matter) finds a solution. I really don't want to be stuck with a phone that can't update, all because T-Mobile decided that they really liked photobucket.
Click to expand...
Click to collapse
i'm super confused with this thread. how could you have deleted a program from /system when we dont have full root yet? just powering down the device and powering it back on would essentially re-install that app would it not? unless you applied the ota before rebooting your phone in which case i dont know what would happen, but if you shut down your phone and power it back on on the original firmware, all modifications to /system should be undone. so after a reboot, applying the ota shouldnt be a problem
*sigh* You CAN make modifications to /system. There's no "restore" that happens on reboot, it's just that it appears r/w to android and android caches the writes to /system.
You can delete files(and apps obviously) from /system by telling android to restore off of that file. Here's how the restore process is supposed to work:
Restore recieves the .zip containing firmware
Restore verifies firmware
Restore flashes firmware
Restore deletes old .zip containing firmware
However, if you tell it to restore off of a file that doesn't contain firmware (such as an apk) this happens:
Restore recieves .apk
Restore verifies apk for firmware install
Restore says WTF THIS IS NOT FIRMWARE
Restore deletes the .apk even though the restore didn't work.
And that's how we are able to delete files in /system ^_^
shizenyasuya said:
i'm super confused with this thread. how could you have deleted a program from /system when we dont have full root yet? just powering down the device and powering it back on would essentially re-install that app would it not? unless you applied the ota before rebooting your phone in which case i dont know what would happen, but if you shut down your phone and power it back on on the original firmware, all modifications to /system should be undone. so after a reboot, applying the ota shouldnt be a problem
Click to expand...
Click to collapse
Paul came up with a method that tricks the phone into thinking something is an update.zip, which, when it cannot be applied, is then deleted. It's creative, but many of us jumped the gun, and deleted a bunch of stuff, which me might regret later. See this thread on MoDaCo.
Great, i hope we're not screwed because i deleted a bunch of the bloatwares =/
Sent from my T-Mobile G2 using XDA App
I have been searching the internet far and wide for some type of solution to the boot loop I am getting. I'm in way over my head here. Before anyone considers trying to root their new Note 3... I should warn you that it is extremely risky. It's much riskier than rooting my original Note was. It seems like Samsung has gotten savvier to people modifying the phones.
My knox "warranty void" is now maked as 0x1... which from my understanding means that I can no longer load a stock kernel on my phone... The problem is I can't find any non-stock kernels or roms for the N900W8. Hopefully this is just a matter of time, and I can try to make due without a phone for a while. (the thought of that being more than a few days is gutwrenching. I use my phone at work constantly.)
I made the mistake of trying to restore a backup through TWRP after SuperSU was crashing constantly. Little did I know that restoring a backup would throw me into a boot loop. And now upon reading the "rooting" instructions, I see in huge bold capital letters "DO NOT RESTORE A NANDROID OR YOU WILL HARD BOOTLOOP." The problem is I had never even heard of "Nandroid" before tonight. I rooted my original Note a long time ago and never thought about it again. After looking up what a "Nandroid" is, I've become aware that it's backup software for rooted users. Well.. how could I possibly have a Nandroid if I wasn't able to root yet. Are all backups, even those made in TWRP referred to as Nandroids? If that disclaimer had said "DO NOT RESTORE A BACKUP", then perhaps I would have known... but ultimately I should have been 10x more careful in this. The idea that the act of restoring a backup will ruin your phone is like a horror story. There is no way I would ever attempt to root this phone if I knew that you could not restore a backup.
Anyways... let this serve as a warning to those who don't know everything about these devices. If there is a single term in anything you are reading that you don't understand, even if it doesn't seem to apply to you, DO NOT PROCEED UNTIL YOU KNOW WHAT IT MEANS.
P.S. if someone could help me unbrick my phone, I would be forever grateful.
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
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)
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