Database Info

[SOLVED] TWRP backups: Delete failed

Hi
Despite several attempts with different file managers and TWRP versions I can't delete my TWRP backups. The only solutions I have is through the recovery mode or a terminal command (rm -rf /sdcard/...).
No issue to delete folders from other directories though.

Is this the same with new backups?

rootSU said:
Is this the same with new backups?
Click to expand...
Click to collapse
Yep

Primokorn said:
Yep
Click to expand...
Click to collapse
odd. i use root explorer, open twrps file, select backups, long press on the backup i want to delete, then press delete(and its gets deleted). what file explorer do you use?

Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?

rootSU said:
Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?
Click to expand...
Click to collapse
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.

simms22 said:
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.
Click to expand...
Click to collapse
I mean for @Primokorn not in general
Sent from my Nexus 5 using Tapatalk

@Primokorn try root explorer

I tried with root explorer, solid explorer and ES file. Nothing works with these apps.
Actually I already had this issue with old TWRP versions.
I manage my backups from the recovery mode now but that's really odd...
Maybe doing a new fastboot flash could fix it. Last time I had to use Flashify to upgrade because I didn't have a PC.
Then I'll try with adb if needed.

If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.

KJ said:
If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.
Click to expand...
Click to collapse
Yep. Better yet, flash a userdata.img I reckon

Problem solved after flashing userdata.img. Thanks guys.

I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP

iliass01 said:
I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP
Click to expand...
Click to collapse
It's too late for me to try but I keep this in mind. I took the opportunity to clean up my internal memory lol
BTW due to this issue ADB didn't work while being into recovery mode. Everything is fixed now.

stuck in boolloop after installing layers

Hello
i installed layers and applied a theme and performed a reboot and the device is stuck . any ideas ?

Hello,
please reflash your ROM.

No need to reflash your ROM, OP. Reboot to recovery (a custom one, of course), and either by using adb shell or twrp's built in file manager, remove what you will from /system/vendor/overlay.
a hammerhead wrote this.

beekay201 said:
No need to reflash your ROM, OP. Reboot to recovery (a custom one, of course), and either by using adb shell or twrp's built in file manager, remove what you will from /system/vendor/overlay.
a hammerhead wrote this.
Click to expand...
Click to collapse
What of there's no /system/vendor/overlay/, just /system/bin/? Also, I see just /vendor in the root. It contains firmware and lib folders. Also, I have /sdcard/Overlays and it contains Backup folder(which is empty) and vividcolorwhite.zip. Nothing more.

drago06 said:
What of there's no /system/vendor/overlay/, just /system/bin/? Also, I see just /vendor in the root. It contains firmware and lib folders. Also, I have /sdcard/Overlays and it contains Backup folder(which is empty) and vividcolorwhite.zip. Nothing more.
Click to expand...
Click to collapse
vividcolorwhite.zip: is this the overlay that's giving you grief? delete/move it.

drago06 said:
What of there's no /system/vendor/overlay/, just /system/bin/? Also, I see just /vendor in the root. It contains firmware and lib folders. Also, I have /sdcard/Overlays and it contains Backup folder(which is empty) and vividcolorwhite.zip. Nothing more.
Click to expand...
Click to collapse
You have to mount your system partition. Just boot into twrp recovery, go to mount, mount system. After you mount the system partition you should be able to see all the system folders.

Mr.FREE_Bird said:
You have to mount your system partition. Just boot into twrp recovery, go to mount, mount system. After you mount the system partition you should be able to see al the system folders.
Click to expand...
Click to collapse
THANKS! This is exactly what I was looking for.

I'm rooted, phone is trying to update from 8.0.0.369 to 8.0.0.373 and it just...

It ends up in recovery mode so I just turn it off and boot up again and it says update failed. I realize it will lose root so I'll have to reroot but will it lock the bootloader again also? I'm just tired of seeing it everyday want to update so figured I'd let it do it but it does't seem to work. Is there a manual update file somewhere? I googled but I can't find it. Should I find the complete rom and re-install the newest version?

jeffrimerman said:
It ends up in recovery mode so I just turn it off and boot up again and it says update failed. I realize it will lose root so I'll have to reroot but will it lock the bootloader again also? I'm just tired of seeing it everyday want to update so figured I'd let it do it but it does't seem to work. Is there a manual update file somewhere? I googled but I can't find it. Should I find the complete rom and re-install the newest version?
Click to expand...
Click to collapse
Bootloader will stay unlocked. If it's an OTA it's trying to install it will fail IF it wants to patch ramdisk as you're rooted.
You can restore stock ramdisk and it should update correctly, but I'd use FullOTA instead for best compatibility.
You can install FullOTA either using HWOTA or installing TWRP (by Pretoriano80 as it has decryption support) and use HuRUpdater script to update.

ante0 said:
Bootloader will stay unlocked. If it's an OTA it's trying to install it will fail IF it wants to patch ramdisk as you're rooted.
You can restore stock ramdisk and it should update correctly, but I'd use FullOTA instead for best compatibility.
You can install FullOTA either using HWOTA or installing TWRP (by Pretoriano80 as it has decryption support) and use HuRUpdater script to update.
Click to expand...
Click to collapse
I have TWRP 3.2.1-0 since I installed Oreo. Is the full ota downloaded into my phone somewhere since it seems to download it fine then I can install it with TWRP? Or do I need to find it online somewhere. Since it ends up in TWRP after trying to install if it was someplace I can find then maybe I can just install whie in TWRP. I'll google for HuRpdater script or is it on here somewhere? I just googled but nothing came up.

jeffrimerman said:
I have TWRP 3.2.1-0 since I installed Oreo. Is the full ota downloaded into my phone somewhere since it seems to download it fine then I can install it with TWRP? Or do I need to find it online somewhere. Since it ends up in TWRP after trying to install if it was someplace I can find then maybe I can just install whie in TWRP. I'll google for HuRpdater script or is it on here somewhere? I just googled but nothing came up.
Click to expand...
Click to collapse
Updates go to /data/update/
But you can download it from http://pro-teammt.ru/firmware-database/ (download update.zip, public zip and data zip for your firmware. You can click the File list link after you have searched to find the public and hw data)
And HuRUpdater is found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
TWRP can't install huawei update.zips by default, so you'd have to download firmware then use HuRUpdater to flash it.

ante0 said:
Updates go to /data/update/
But you can download it from http://pro-teammt.ru/firmware-database/ (download update.zip, public zip and data zip for your firmware. You can click the File list link after you have searched to find the public and hw data)
And HuRUpdater is found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
TWRP can't install huawei update.zips by default, so you'd have to download firmware then use HuRUpdater to flash it.
Click to expand...
Click to collapse
I found the files where you said, thanks. update_data_public.zip, update_MHA_L29_hw_usa.zip, and update.zip
When I read the instuction it calls for 3 files 2 of which are already spelled out correctly but looks like I need to rename the MHA file to update_all_hw.zip is this correct?
It also says to put the recovery image in the same folder if I want to keep custom recovery so sounds like it will wipe it if I don't. I'll have to download twrp 3.2.1-0 again
Ok this is interesting, I have 2 files in data with 6 digit names 151465 and 161808 and both have the 3 files but they are of different sizes but the exact same names as I mentioned before. Maybe better to go to the website you mentioned or I'll screw something up with them.
Figured out how to open the file list and can see the 3 files now so I'll get all 3. Update.zip is 2gb is that right? It's gonna take like 5 hours it says.

jeffrimerman said:
I found the files where you said, thanks. update_data_public.zip, update_MHA_L29_hw_usa.zip, and update.zip
When I read the instuction it calls for 3 files 2 of which are already spelled out correctly but looks like I need to rename the MHA file to update_all_hw.zip is this correct?
It also says to put the recovery image in the same folder if I want to keep custom recovery so sounds like it will wipe it if I don't.
Ok this is interesting, I have 2 files in data with 6 digit names 151465 and 161808 and both have the 3 files but they are of different sizes but the exact same names as I mentioned before. Maybe better to go to the website you mentioned or I'll screw something up with them.
When I click on the "update" hyperlink it just opens a new page and doesn't seem to start downloading. Maybe I need to do something else?
Click to expand...
Click to collapse
Rename the zip with HW in its name to update_all_hw.zip and Public to update_data_public.zip.
If recovery.img is present in the same dir as guru it will flash it back to recovery_ramdisk after update is flashed. It's to save a step so you don't have to reboot to fastboot to flash it again.
/data/update includes old/partial downloads too. So if you for example have used eRecovery before to download, but cancelled it, the update is still there. Same goes for system update. I would rather use firmware finder/teammt because you know those are completed zips.
On the site you can click on file list to show links to downloads, the update link rarely works anymore. It just parses data from hicloud but for some reason the update link always points to front page (or to search results if you have searched).
So just copy paste the update, public and Hw l29 links into a new tab to download.
jeffrimerman said:
Figured out how to open the file list and can see the 3 files now so I'll get all 3. Update.zip is 2gb is that right? It's gonna take like 5 hours it says.
Click to expand...
Click to collapse
That's correct.

It's going to erase everything isn't it? Rename the TWRP to "recovery" right? Since it's already a .img file I imagine I don't need to add ".img" right?

jeffrimerman said:
It's going to erase everything isn't it? Rename the TWRP to "recovery" right? Since it's already a .img file I imagine I don't need to add ".img" right?
Click to expand...
Click to collapse
Updating doesn't wipe. And HuRUpdater will tell you if it should wipe, it will also tell you if it will lock bootloader.
Yes, if you don't have "show extentions" turned on in Windows just rename it to recovery.

ante0 said:
Updating doesn't wipe. And HuRUpdater will tell you if it should wipe, it will also tell you if it will lock bootloader.
Yes, if you don't have "show extentions" turned on in Windows just rename it to recovery.
Click to expand...
Click to collapse
It didn't erase anything woooo hoooo. Thank you. I did loose root which will be easy to put back on. At the end if installing everything automatically there were 2 buttons on the bottom. One was erase cache/dalvik I think and the other was reboot so I just rebooted to be safe. Figured if it was buggy I could always go back and erase the cache/delvik but looks fine. Just checked and my TWRP is there so all is good

TWRP : SYSTEM partition not in backup list, how do i backup it?!

After unlocking phone & installing TWRP, i want to backup of course, but in the partition list, SYSTEM is not here! Never seen this before. Happens with any version of TWRP for the Realme 5 Pro. I may be missing something..? Let me know ASAP, thanks

Try Erase Partition Recovery and Flash TWRP again.
Command
fastboot erase recovery
fastboot flash recovery file-name-twrp.img
Click to expand...
Click to collapse

faisalxp said:
Try Erase Partition Recovery and Flash TWRP again.
Click to expand...
Click to collapse
Thanks but that did not change anything. When you go to BACKUP, do you see SYSTEM (just that, not SYSTEM IMAGE)? I noticed by going into file manager that system folder appear as "system_root" perhaps that's the issue..?
But then it should be the same for everyone, why it isn't i don't get it?! In mount section, SYSTEM is NOT ticked after booting recovery, but ticking it doesn't change anything unfortunately..

Yeah realme rename it to system_root

faisalxp said:
Yeah realme rename it to system_root
Click to expand...
Click to collapse
..? Not sure to understand your reply (=how is it helping me) : are you saying it is so for ALL Realme roms/devices? I read it's only for non-indian versions.. I need some guidance here :angel:

GoJo ^^ said:
Thanks but that did not change anything. When you go to BACKUP, do you see SYSTEM (just that, not SYSTEM IMAGE)? I noticed by going into file manager that system folder appear as "system_root" perhaps that's the issue..?
Click to expand...
Click to collapse
Have you previously tried to backup a System Image and try to open the backup file system_image.emmc.win with an Archive application like RAR or Zip ?
If so you will see that the System folder is inside the system_root folder so it can be concluded that System Image or system on twrp is the same as system_root or root. You can check attachment file.
I think the problem is with the twrp source or the developer, where the system image backup path leads to System_Root not /system_root/system.
If you only want to backup only the system partition you can use "dd" command on the TWRP terminal.
But then it should be the same for everyone, why it isn't i don't get it?! In mount section, SYSTEM is NOT ticked after booting recovery, but ticking it doesn't change anything unfortunately..
Click to expand...
Click to collapse
When you tick and mount the system partition on twrp, you will be able to edit all files and folders in system_root. for more details diferent tick and untick system, you check the file attachment.
GoJo ^^ said:
..? Not sure to understand your reply (=how is it helping me) : are you saying it is so for ALL Realme roms/devices? I read it's only for non-indian versions.. I need some guidance here :angel:
Click to expand...
Click to collapse
I try searching and not its not same for all device realme, one of the example : Realme X & XT using /system-root
I think it depends on the variant or type of device reality. bit the point its same System Image or system on twrp is the same as system_root or root

But "SYSTEM IMAGE" is +5GB, never seen such big parition on any phone.. It does contain system certainly, as well as other thing i do not need. I wish there was a way to backup just system like i did up until today on all other devices..

GoJo ^^ said:
But "SYSTEM IMAGE" is +5GB, never seen such big parition on any phone.. It does contain system certainly, as well as other thing i do not need. I wish there was a way to backup just system like i did up until today on all other devices..
Click to expand...
Click to collapse
Try this command on Terminal TWRP
Code:
dd if=/dev/block/by-name/system of=/sdcard/backup-system.img

anyone here facing backing up system image back up failed on fox and twrp ?

right magisk patched boot.img file?

After grabbing the boot image matching my current version, patched with magisk, I am told by 2 different tutorials, one in this forum and one on youtube, quote: "Open a terminal in the directory your patched boot img file is and type 'fastboot flash boot magisk_patched.img".
No Problem, both tutorials instruct to type fastboot flash boot magisk_patched.img. My worry is that my file is labeled "magisk_patched-22100_xlAUj" as opposed to just "magisk_patched.img".
I assume I either did something wrong, or the file names have changed since the instructionals. Wanted to make sure before rooting with this patched file since I only have a very surface understanding of what I'm doing, and don't want to brick my phone.
FYI I did try the suggested 'fastboot flash boot magisk_patched.img' command but obviously didn't worry I assume because the file names are different.

I don't know what you already did, but if you can locate where you are along in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
It worked for me if you follow the steps as described.

the file name basically doesn't matter. as long as what you type into terminal matches what magisk gave you, you're fine. to be more specific to your case: since your file is called magisk_patched-22100_xlAUj.img, your terminal command has to be fastboot flash boot magisk_patched-22100_xlAUj.img. to explain further: what you're doing is that you're telling the program fastboot that it's supposed to flash (copy) a specific file to the boot partition on your phone. that specific file here is the one magisk created (magisk_patched-22100_xlAUj.img).
another solution would be to rename magisk_patched-22100_xlAUj.img to magisk_patched.img

Hey thanks so much, just wanted to make sure before I went through went it. However, I am getting a "disc image file is corrupted" message after hitting enter. I transferred the file by just drag and drop onto my pc. Couldn't get the adb pull command to work.
I even re-patched the boot img via magisk and retried, still getting same message. Every thing I'm doing appears to line up with the youtube tutorial. Would this be a case where I would try canary magisk build instead to patch? Or maybe I should make a new thread....

huh, that certainly is odd. no idea why that would happen. which version of magisk are you using and where did you get the boot.img?

Used this guide https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Got the boot.img from here https://developers.google.com/android/images?hl=en#sunfish (made triple sure it matched my current version)
Using Magisk 22.1 patched file in beta mode as instructed

i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.

THEGAZINGVOID said:
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
Click to expand...
Click to collapse
Is the patched image a 0b file? This is happened to me before too. The work around I do is to rename the boot image to something like boot_april.img before patching it in Magisk. Then check to make sure that the patched image isn't a zero byte file before copying it to your PC and flashing in fastboot.

breacherman said:
Hey thanks so much, just wanted to make sure before I went through went it. However, I am getting a "disc image file is corrupted" message after hitting enter. I transferred the file by just drag and drop onto my pc. Couldn't get the adb pull command to work.
I even re-patched the boot img via magisk and retried, still getting same message. Every thing I'm doing appears to line up with the youtube tutorial. Would this be a case where I would try canary magisk build instead to patch? Or maybe I should make a new thread....
Click to expand...
Click to collapse
See post above this one.

THEGAZINGVOID said:
i'm not sure is this is going to work, but here's a boot.img i patched. it's version sunfish-rq2a.210405.005-factory-ab0ba039. maybe try it, see if it works. just to cover my own ass: i'm not responsible if anything goes wrong. anyhow, it's probably a good idea to familiarise yourself with how to restore your phone to factory before flashing anything and keep a backup of the stock boot.img somewhere.
Click to expand...
Click to collapse
Ok, thanks, I might try that, but I'm not sure atm how to backup this stock rom without twrp.

buffal0b1ll said:
Is the patched image a 0b file? This is happened to me before too. The work around I do is to rename the boot image to something like boot_april.img before patching it in Magisk. Then check to make sure that the patched image isn't a zero byte file before copying it to your PC and flashing in fastboot.
Click to expand...
Click to collapse
Thanks for your suggestion but no, it's about 65mb in size.

breacherman said:
Ok, thanks, I might try that, but I'm not sure atm how to backup this stock rom without twrp.
Click to expand...
Click to collapse
I actually tried magisk canary build to patch the boot.img, and it failed, like before at first, I tried a second time to get a screeshot, and it worked for some reason.

You can follow this ↑↑↑ It's worked.