Is there a Pure Nougat TWRP Backup? - X Style (Pure) Q&A, Help & Troubleshooting

I am looking for a stock Nougat TWRP Backup. I am searching the forums and all I can find is TWRP backups for other regions. I am currently running the Retla Nougat.
Can anyone post a TWRP Backup or link me to a post where one could be found?

System, boot are the same.
Twrp can't backup baseband.
So...
You can restore any Nougat.
...
Somewhere was N for fastboot.
https://forum.xda-developers.com/moto-x-style/general @kpcurl

dzidexx said:
System, boot are the same.
Twrp can't backup baseband.
So...
You can restore any Nougat.
...
Somewhere was N for fastboot.
https://forum.xda-developers.com/moto-x-style/general @kpcurl
Click to expand...
Click to collapse
Can you explain that again? I’m wanting the same thing. I’m on 7.1.2 rom
Sent from my iPad using Tapatalk

https://youtu.be/ppME4cYW55Y @rh535

Thanks dzidexx. I already used a 1572 restore for my 1575. However, it's not perfect and many 1575 users are having issues with the using the restore from other regional versions.

Restore backup for update is very bad idea. It is only system partition, rest you have MM.
Use flashfire app u will see how much.
@

Related

Can I make use of Nougat's automatic updates and have/keep root? TWRP ver. to use?

Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
EvanVanVan said:
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
Click to expand...
Click to collapse
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
+1 Flashfire
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
EvanVanVan said:
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
Click to expand...
Click to collapse
The other issue with TWRP was backing up and restoring the EFS partition, it seemed that 3.0.2-1 corrupted it on restore which would be a problem. They did have a work around. They suggested using -0 would be fine. I have -2 and did a N to N restore with no issue, but I did not restore EFS. I'm always extra careful with new versions, I tend to backup my data and backups off-phone just in case.
dratsablive said:
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
Click to expand...
Click to collapse
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
smallvan said:
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
Click to expand...
Click to collapse
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
dratsablive said:
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
Click to expand...
Click to collapse
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
smallvan said:
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
Click to expand...
Click to collapse
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
dratsablive said:
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
Click to expand...
Click to collapse
I believe I am looking for a suitable way to upgrade my 6p from MM to N that I have explicitly stated at my wrong thread post. This is absolutely not my intention to return my 6p back to stock of MM. And there is every reason to upgrade to N, thus, vendor.img is no doubt a must for an amateur like me.
Nevertheless, thanks for dratsablive kind suggestions.

Twrp help

Hi, i made a backup of my stock rom but when I go into restore I can't see any folders on any drive. If I click on file Explorer I can see them and also when I click on install. How can I restore by backup? Thanks.
Sent from my XT1039 using Tapatalk
Hi, what is your TWRP version, 3.0.2.1 ?
i agree with the previous post, what version of twrp are you using? 3.0.2-1 sometimes wont find 3.0.2 nands. Let us know, and we can probably help unless they got deleted, in which case its gone. But if that happens, you can always download the stock tarball from sammobile.com/firmwares
also, what S5 variant are you using?

While rooting...i lost my os..i can get no further than into recovery

while in process of rooting..it seems i made a mistake..i am informed by twrp ,,,no os installed..
Always make a backup mate. You might consider flashing stock ROM via fastboot. And then proceed with rooting and whatever you were trying to do.
https://mirrors.lolinet.com/firmware/moto/potter/official/
Flash twrp then custom rom. AOSPEX works great
tywinlannister7 said:
Always make a backup mate. You might consider flashing stock ROM via fastboot. And then proceed with rooting and whatever you were trying to do.
https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
Wonderful. I was looking for the XT1681 official modem/baseband files.
Thanks a lot.

Stuck in TWRP after pushed upgrade 28s

This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that

How do I get back to 7.1

A month or two ago I put on AOSP 8.1 via this thread.
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I'd like to go back to where I was. I have a full twrp backup. I cannot restore that currently due to the aosp being encrypted. You get a bunch of errors.
What is the easiest way to get back to a place where I can simply restore my twrp backup?
TWRP is installed. 3.1.1 I'm assuming I should upgrade to 3.2.2. Curious if that will let me just restore from my twrp backup.
It was suggested I flash another .img file but I'm not sure which one.
j1tters said:
A month or two ago I put on AOSP 8.1 via this thread.
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I'd like to go back to where I was. I have a full twrp backup. I cannot restore that currently due to the aosp being encrypted. You get a bunch of errors.
What is the easiest way to get back to a place where I can simply restore my twrp backup?
TWRP is installed. 3.1.1 I'm assuming I should upgrade to 3.2.2. Curious if that will let me just restore from my twrp backup.
It was suggested I flash another .img file but I'm not sure which one.
Click to expand...
Click to collapse
You can flash N with Emma... Or, if you just flash a different boot img from a different rom, or update TWRP to 3.2, (it's official now), you should be able to restore backup.
levone1 said:
You can flash N with Emma... Or, if you just flash a different boot img from a different rom, or update TWRP to 3.2, (it's official now), you should be able to restore backup.
Click to expand...
Click to collapse
Emma? Where does one get that. I've always used xpirifirm and flashtool.
Oh seriously? I was kind of hoping that was the answer, that twrp 3.2.2 will be able to restore that.
Thanks
j1tters said:
Emma? Where does one get that. I've always used xpirifirm and flashtool.
Oh seriously? I was kind of hoping that was the answer, that twrp 3.2.2 will be able to restore that.
Thanks
Click to expand...
Click to collapse
https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/
levone1 said:
You can flash N with Emma... Or, if you just flash a different boot img from a different rom, or update TWRP to 3.2, (it's official now), you should be able to restore backup.
Click to expand...
Click to collapse
So I got 3.2.2 installed. It will not restore my old backup.
Could not mount data unable to find crypto key. Also not cannot boot into working oreo.
Unable to mount /data
Unable to find file system
Error opening modem_fs1.emmc.win no such file.
At this point I can get to twrp 3.2.2 and I can get to fastboot.
Cant get emma to see phone.
Any suggestions?
I got emma working. I got it flashed back to nougat. I still cannot restore twrp.
I get this
unable to find file system (first period)
Error opening modem_fs1.emmc.win no such file.
j1tters said:
I got emma working. I got it flashed back to nougat. I still cannot restore twrp.
I get this
unable to find file system (first period)
Error opening modem_fs1.emmc.win no such file.
Click to expand...
Click to collapse
Hi, how did you get emma recognize your phone? I can't see my phone in it.
andry360 said:
Hi, how did you get emma recognize your phone? I can't see my phone in it.
Click to expand...
Click to collapse
In Emma I went to help, Product information. Then I chose my model. Booted phone into fastboot and plugged it in. Emma saw it from then on.

Categories

Resources