Database Info

TWRP backups

So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:

mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.

exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.

robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!

mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?

mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.

TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??

mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.

I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks

What version of twrp ?
I only use rc1, never seen this.

Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.

pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.

Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks

pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?

Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.

pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.

Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.

pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.

Confused using TWRP on U11 to restore

I dutifully searched & couldn't find a thread here on restoring a nand backup… I tried to restore one & I got a msg abt how it won't work on a read only setting- but I saw elsewhere there are probs relating to restoring a nand b/u on a U11…
All help appreciated, TIA, oldwolf

You must have TWRP with Magisk flashed to have access to system/mount system.
Sent from my HTC U11 using Tapatalk

arses, tnx for reply. I have TWRP & Magisk, & this is 1st time & 1st device I'm using Magisk; so give a guy a break. Nobody said anything abt mounting, unmounting or at which point it is safe. Or why it'd be needed w/twrp & this fone. I guess I need step by step instructions to restore my nand backup & how/when to mount /unmount so I can continue doing more of the same.
Also, can one backup or restore only portions of a full nand i.e. data-only or system-only?
If you'll be good enuf- pls mention strategies when one would use which kind of restore to fix which kind of probs. Be sure official thanks will be forthcoming & returning the favor will occcur once I get 'surer' on my feet w/this.
Much appreciated; oldwolf

oldwolf613 said:
arses, tnx for reply. I have TWRP & Magisk, & this is 1st time & 1st device I'm using Magisk; so give a guy a break. Nobody said anything abt mounting, unmounting or at which point it is safe. Or why it'd be needed w/twrp & this fone. I guess I need step by step instructions to restore my nand backup & how/when to mount /unmount so I can continue doing more of the same.
Also, can one backup or restore only portions of a full nand i.e. data-only or system-only?
If you'll be good enuf- pls mention strategies when one would use which kind of restore to fix which kind of probs. Be sure official thanks will be forthcoming & returning the favor will occcur once I get 'surer' on my feet w/this.
Much appreciated; oldwolf
Click to expand...
Click to collapse
Magisk has nothing to with twrp.
You need to mount system with write permissions and then you can restore your Backup.
You can also choose what to restore, but this depends in your Backup.

diamond09, thanks for the clarification...
I seemed to recall that the Sprint U11 + TWRP + Magisk make for a combo that should not be run together w/unlocked- or was that twrp & encrypted? As I said, I'm new to this ver. of TWRP…
Once I'm in twrp, & ready to restore - that's when you mount system w/write permission- I imagine that is done in TWRP.
Once restored, do you have to remount system w/read only permissions, or does a reboot return system to read only?
I was much more comfortable w/older twrp on my S4 …
BTW, can you make diff slots in TWRP3 to boot diff roms? I have a 128Gb Sandisk class10 & loads of space…
TIA, oldwolf

oldwolf613 said:
diamond09, thanks for the clarification...
I seemed to recall that the Sprint U11 + TWRP + Magisk make for a combo that should not be run together w/unlocked- or was that twrp & encrypted? As I said, I'm new to this ver. of TWRP…
Once I'm in twrp, & ready to restore - that's when you mount system w/write permission- I imagine that is done in TWRP.
Once restored, do you have to remount system w/read only permissions, or does a reboot return system to read only?
I was much more comfortable w/older twrp on my S4 …
BTW, can you make diff slots in TWRP3 to boot diff roms? I have a 128Gb Sandisk class10 & loads of space…
TIA, oldwolf
Click to expand...
Click to collapse
It has nothing to do with HTC or TWRP IMHO, but with the update policy of Google that changed to Block Based OTA. This means that the OTA checks if the md5 sum of system partition matches the value that hmwould be expected. If you now mount system partition r/w this will change the md5 and a future OTA will fail due to the fact that it recognizes the change in md5.
If you now have a pristine backup of system image, meaning a system image backed up when mounted read only in TWRP you would restore it by mounting the actual, altered system partition r/w. TWRP then writes the system.img from backup to the system partition. As the image has never been mounted all will be fine. To make sure TWRP won't mount it again would be the best to have respective notification when starting TWRP, asking you if you want to mount r/w or ro.
Many of us check the mark that TWRP shall not ask this again, which means those people got to remember to unchecked the r/w option in the Mount menu after performing a restore, as well as to active r/w support prior to a restore.
As soon as you restored the system image, you can easily mount system ro, reboot to TWRP and flash Magisk as this won't alter your system partition but root your device and e.g. run custom ROM in for of a Magisk Module.
In regard of multiple ROMs this is not possible. It'd need a hack like e.g. MultiROM and a special MultiROM TWRP to do such things. But as told above you could flash different Sense based Custom ROMs as Magisk Module and change them by activating the one and deactivating the other, do a reboot and do for it. This you'd use the same data partition and Apps on every single Custom ROM and could run LeeDrOiD, ViperU and BadBoys Magisk version without altering your system, speaking of your stock ROM. Same is valid for custom kernels that are available as Magisk Modules.
Sent from my htc_pmeuhl using XDA Labs

Development TWRP for Moto G Stylus 2021 xt2115-1 (otg mouse necessary)

OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.

Hey, do u have telegram? If so hit me up on there @rcc2002 username "Ritmo".. Im working on getting you help on this subject as soon as possible because I am so happy that you were able to create this. It does temporary boot. I didn't try flashing it but the problems that create the black screen I believe are Android security during boot, usually something to do with dmverity i think, the no touch screen working is usually a driver issue that just needs a proper driver being installed in the build. Or even pushed with a terminal cmd poss I've seen.. And the two errors coming up permission denied for system root is one I've seen before and is I believe very common. All mostly has to do with Android security and all the little annoying issues in building a permissive recovery I suppose. But anyway the dude I'm going to ask will basically tell you probably exactly what to do the second he sees or hears the errors and sees ur files.. what do the two zip files contain? And how did you build this exactly? Curious.. from common trees from scratch or a device tree builder? if you don't have telegram, just text me 856-896-7600..... ~RAY..

They contain most of kernel files and recovery and boot stock backup. Build.prop fstab and ueventd.rc. Also the device tree all pulled from the device root using root explorer. I ported this over from a different device that had the exact same specs. I used AIK for windows and modified the files to correlate with the moto g stylus 2021.

ID like to work on this also do you have someway to communicate? I may have found one of the kernel source codes you can try building with.

In all honesty I just need somebody to help me learn how to install touch drivers into the recovery. Then I will use avbtools to resize the file to its proper size. Just need the info. The rest of the recovery works. I've tested almost all of it. Haven't tested adb yet but I'm sure that won't be a problem if faulty.

Here is the block partitions I used to partly configure the recovery. It's a bit messy but I think it's OK. Not trying to type all this out. Pulled from device last night.

sosthenisRR said:
OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.
Click to expand...
Click to collapse
Contact me on telegram, I could possibly help. @Electimon

is anyone working on twrp for the xt2131-1?

aaronj1993 said:
is anyone working on twrp for the xt2131-1?
Click to expand...
Click to collapse
No, also that's the 5G https://forum.xda-developers.com/f/moto-g-stylus-5g.12373/

ShayBox said:
No, also that's the 5G https://forum.xda-developers.com/f/moto-g-stylus-5g.12373/
Click to expand...
Click to collapse
yes I know but that's the next closest device.

I'm mid-level to flashing but new(ish) to XDA here. Since this device is so similar "can" you flash the 5G ROMS to the 2021 ? And it boot/work somewhat ? Referring to Lineage OS for the most part since these devices are still somewhat "new" .. Trying to find the best place to ask and this seems to be it so far. No posts much yet in 2022 ..

roiikka said:
I'm mid-level to flashing but new(ish) to XDA here. Since this device is so similar "can" you flash the 5G ROMS to the 2021 ? And it boot/work somewhat ? Referring to Lineage OS for the most part since these devices are still somewhat "new" .. Trying to find the best place to ask and this seems to be it so far. No posts much yet in 2022 ..
Click to expand...
Click to collapse
The Moto G Stylus 5G has a different SoC, so this most likely would not work.

I just upgraded to android 11 on my moto g stylus 2021 XT2115-1 but now I cannot figure out how to root it I can install magisk and patch the boot but it does not stick and keep root but it does show ramdisk as yes, so not sure what the deal is, it has been awhile but it looks like to achieve it we will have to get rid of dmverity and vbmeta at least. to be able to keep a root or roll back to droid 10.

Well I cannot help with twrp but I was able to upgrade to android 11 and get root with magisk rather easily check this post all credit goes to the poster. https://forum.xda-developers.com/t/root-question-for-moto-g-stylus-xt2115-1-2021.4259413/

toxinburn said:
Well I cannot help with twrp but I was able to upgrade to android 11 and get root with magisk rather easily check this post all credit goes to the poster. https://forum.xda-developers.com/t/root-question-for-moto-g-stylus-xt2115-1-2021.4259413/
Click to expand...
Click to collapse
However if someone can get twrp working I got orange fox but meh not my fav i prefer touch twrp please let me know or if i can find it someplace ill post it worst case I just reflash stock recovery and try again.

I can help with this if it hasn't been fixed already ?? Just did twrp for XT2215-4 and XT2211-2

so is this stable? // who knows which ROMs are safe to flash to this xt2115 -1

Terrible this isn't working, you guys throw the stylus in the trash and get new devices?

What's the new member thing about. I've been on xda for 10 years

sosthenisRR said:
OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.
Click to expand...
Click to collapse
I have the xt2115-1 and am curious to know what ever came of this. Was a working TWRP ever accomplished? I am trying to install a custom rom on my phone, but I can't seem to move past a permission denied issue in fastboot and can't seem to locate a working TWRP. Any suggestions?

Why does restoring my backup.ab get stuck at restoring efs2?

I made a backup.ab straight to my PC from twrp since I didn't have enough storage on my phone, not thinking much of it. Now when I try to restore it, everything goes fine except for the last part where twrp tries to restore efs2 and gets stuck on it. I can't install other ROMs after this either and my phone is practically a brick right now. What can I do? Any kind of help is appreciated.

.AB - files are TAR-archives. Hence you can try to extract them by means of Android's TAR applet. TAR is also available in Windows OS as command line tool.

Have you found a way to fix this?

-sandro- said:
Have you found a way to fix this?
Click to expand...
Click to collapse
I realized I backed up both System and System Image partitions. I think my tissot device only supported System Image backups so that's why it was messing up.

Sideload twrp backup?

So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers

Re-flash Stock ROM.

Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.

Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer

what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?

No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.

you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com