Database Info

[Q] CWM Backup Folder not showing - CWM sees backups

Okay, so I am rooted on stock with ElementalX and philz touch recovery. I typically alternate between elementalX and stock kernel. About 2 weeks ago whenever I make a backup it backups fine, however when I go to my clockworkmod folder via root explorer it is not there. However Philz touch/CWM sees the backup folder and can restore and backup to it. I have wiped everything, I have flashed back to stock with the firmware and fastboot, where it completely wipes everything with a fresh install. Same results. I am out of ideas. If I try to copy over a clockworkmod folder with backups I have on my PC or even try to create a clockworkmod folder it gives me an error that its unable to create this folder and or copy it from my PC to my Nexus 5.
Anyone have any ideas as to what is happening? I even tried philz touch to make backups as if they were made in TWRP, so it creates a TWRP folder, but that does not do anything either. Any help would be appreciated as I am out of ideas.

ozzmanj1 said:
Okay, so I am rooted on stock with ElementalX and philz touch recovery. I typically alternate between elementalX and stock kernel. About 2 weeks ago whenever I make a backup it backups fine, however when I go to my clockworkmod folder via root explorer it is not there. However Philz touch/CWM sees the backup folder and can restore and backup to it. I have wiped everything, I have flashed back to stock with the firmware and fastboot, where it completely wipes everything with a fresh install. Same results. I am out of ideas. If I try to copy over a clockworkmod folder with backups I have on my PC or even try to create a clockworkmod folder it gives me an error that its unable to create this folder and or copy it from my PC to my Nexus 5.
Anyone have any ideas as to what is happening? I even tried philz touch to make backups as if they were made in TWRP, so it creates a TWRP folder, but that does not do anything either. Any help would be appreciated as I am out of ideas.
Click to expand...
Click to collapse
CWM is outdated.
"Internal Storage" on the Nexus 5 is /data/media/0 (which is what /sdcard is also symlinked to)
CWM uses the outdated legacy location of /data/media/clockworkmod (note the lack of /0)
Therefore you cannot see CWM backups if you look in the internal storage while booted into Android.
Development on Philz Touch has also come to an end - you should use TWRP.

Lethargy said:
CWM is outdated.
"Internal Storage" on the Nexus 5 is /data/media/0 (which is what /sdcard is also symlinked to)
CWM uses the outdated legacy location of /data/media/clockworkmod (note the lack of /0)
Therefore you cannot see CWM backups if you look in the internal storage while booted into Android.
Development on Philz Touch has also come to an end - you should use TWRP.
Click to expand...
Click to collapse
Flashed TWRP and redid a new backup, went to the root explorer and no folder fo TWRP is present, if I go back into TWRP it sees the backup I made but that is it. For some reason I am unable to see the folder.... any ideas?

ozzmanj1 said:
Flashed TWRP and redid a new backup, went to the root explorer and no folder fo TWRP is present, if I go back into TWRP it sees the backup I made but that is it. For some reason I am unable to see the folder.... any ideas?
Click to expand...
Click to collapse
Try deleting the TWRP folder using TWRP itself, reboot the recovery, change a setting or two then make a backup again.
Also make sure you're using a newer version of TWRP if you aren't already.

Sounds like a job for restorecon

rootSU said:
Sounds like a job for restorecon
Click to expand...
Click to collapse
OP says he completely wiped everything while flashing factory images though, so I dunno

Lethargy said:
OP says he completely wiped everything while flashing factory images though, so I dunno
Click to expand...
Click to collapse
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer

rootSU said:
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer
Click to expand...
Click to collapse
Guess its still possible but wouldn't really expect it to happen after a full wipe. Worth a shot anyways now that you've mentioned it.

rootSU said:
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer
Click to expand...
Click to collapse
What is restorecon?
Edit - Flashed toe factory image again and each time I run the flash factory image I get this at the end of each flash, see attached
Found this, its the same issue I am having:
http://androidforums.com/threads/twrp-lollipop-and-the-nexus-5.883331/
Now after flashing a factory image phone just hangs, bootanimation goes on forever and ever, so for now I have no working Nexus 5. Any ideas?
Edit - Flashed TWRP and used MTP mode, internal data is completely blank, no android folder, etc... just empty...

Update, flashed factory image for 4.4.4 and that flashed without errors, going to let it boot up and do its thing. Once done I will try to flash 5.0.1 again.. will report back.
Update - Guess I am stuck for now on 4.4.4. Flashing 5.0 or 5.0.1 fails on userdata as previous screenshot.

ozzmanj1 said:
Update, flashed factory image for 4.4.4 and that flashed without errors, going to let it boot up and do its thing. Once done I will try to flash 5.0.1 again.. will report back.
Update - Guess I am stuck for now on 4.4.4. Flashing 5.0 or 5.0.1 fails on userdata as previous screenshot.
Click to expand...
Click to collapse
Out of curiosity, how much ram do you have on your pc?
Sent from my Nexus 9 using XDA Free mobile app

I am running on 8gb ram

I think I may have resolved the issue, I factory flashed 4.4.4, rebooted, then flashed a recovery, rebooted, then copied over a nandroid backup from end of last month, and restored from that back to 5.0.1. All seems well now, I did not wipe anything when doing the restore. Everything seems to be working now.. will report back if I see any other issues. Thank you to all for your assistance.

rootSU said:
Sounds like a job for restorecon
Click to expand...
Click to collapse
I am back with the same issue. Flashing 4.4.4 image flashes okay, however any attempt at flashing 5.0 or 5.0.1 causes an error just as its wiping userdata. Only way around is to flash 4.4.4 and then restore with a nandroid, which I keep plenty of those laying around.
Mind if I ask what the tutorial is for restorecon? Thank you.

FlashFire with HTC One A9?

Anyone used ChainFire's FlashFire with the One A9?
I've used it for backups successfully but have yet to restore anything with it (a little squeamish to do so :silly.
And I'll just add, if anyone has used it and could offer any tips or procedures that would be great.

FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
Click to expand...
Click to collapse
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?

theNdroid said:
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
Click to expand...
Click to collapse
Of course. Root is required to use FlashFire. I use Xposed as well, and I've had no problems updating via FlashFire.

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Click to expand...
Click to collapse
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?

eelpout said:
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
Click to expand...
Click to collapse
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***

CSnowRules said:
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
Click to expand...
Click to collapse
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.

eelpout said:
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
Click to expand...
Click to collapse
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.

CSnowRules said:
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
Click to expand...
Click to collapse
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.

eelpout said:
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
Click to expand...
Click to collapse
Ok, this post will go a bit off topic. That being said, I can offer two courses of action. I take no responsibility for anything in this post.
Safest--almost no risk (my personal preference)
1. Backup your data partition, including internal SD via TWRP to ext SD or USB OTG drive. Flash the latest RUU from HTC. Boot stock and apply OTAs until there are no more updates available. Fastboot flash the latest TWRP, and finally restore your data and flash the latest SuperSU via TWRP. Reboot your fully updated, rooted A9 with all your data still intact.
A little risky and untested to my knowledge--could result in a hard brick if something partially fails. FLASHING BOOTLOADERS IN FLASHFIRE IS STILL ALPHA FOR HTC DEVICES!!! This may work with s-on...but may require s-off.
Your system partition must have never been mounted r/w for this to work.
2. Download the OTA zips for your phone from the first update available to the latest and the latest SuperSU and TWRP. Use FlashFire to do everything in one shot. Select allow flashing bootloaders in FlashFire settings, select your OTAs for installation from oldest to newest (don't select restore boot and recovery), select TWRP and SuperSU for installation, disable everroot and preserve recovery. Cross your fingers and timidly press flash... If all is successful, you should have the same end result as option 1.
I STRONGLY recommend the first method, but if you're feeling lucky and decide to try the second method, please share how it goes, since this post is FlashFire related and this would be the ultimate test of FlashFire for our devices.

For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.

NuShrike said:
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
Click to expand...
Click to collapse
The solution for problem 1 can be handled in TWRP. The files can be deleted via TWRP's file manager or the built in terminal, which may be easier for some people.
Also, the solution for the corrupted data and internal SD is to create an image of the data partition (just like the system image backup option). This can be done via dd in TWRP or adb. It requires a large amount of storage and it takes longer, but I've had to do it, since I use VIP Access by Symantec for work. A normal file based backup in TWRP breaks that app. This also keeps the pin/fingerprint data intact.
If we could have that implemented in a user friendly manner, that would be great, but I'm sure CaptainThrowback and Chainfire both have bigger issues to deal with. I could probably figure out a solution, but the work wouldn't be worth it for my own benefit, since I'm fluent with the Linux command line.

Help!!! (STUCK IN REBOOT LOOP)

So long story short I got myself in a reboot loop. I have an unlocked bootloader and TWRP installed on my MHA-L29C636B110 and it's always rebooting itself until it reaches back to Huawei eRecovery. I tried everything I could by factory resetting on TWRP, reflashing SuperSU and data files, and still end up in constant reboot loops until I reach eRecovery. Please someone help me resolve this issue!

Did you try wipe+reflash the Rom?
If your afraid you'll lose data just backup using twrp and then use helium once your set to restore apps and data from the backup.

IronSingh said:
Did you try wipe+reflash the Rom?
If your afraid you'll lose data just backup using twrp and then use helium once your set to restore apps and data from the backup.
Click to expand...
Click to collapse
I can't seem to find a ROM for MHA-L29C636B110. Also I don't have a SD card so if I do find the ROM, do I just flash it on TWRP? I tried everything I could think of and it always leads me back to reboot loop to eRecovery

Ben_Li said:
I can't seem to find a ROM for MHA-L29C636B110. Also I don't have a SD card so if I do find the ROM, do I just flash it on TWRP? I tried everything I could think of and it always leads me back to reboot loop to eRecovery
Click to expand...
Click to collapse
Which SuperSU did you install?
And did you decrypt first if the supersu you're installing needs decryption?
If you didn't 'Format Data' in TWRP and SuperSU removes encryption you're trying to boot with an encrypted /data partition which doesn't decrypt.

Ben_Li said:
I can't seem to find a ROM for MHA-L29C636B110. Also I don't have a SD card so if I do find the ROM, do I just flash it on TWRP? I tried everything I could think of and it always leads me back to reboot loop to eRecovery
Click to expand...
Click to collapse
Do you want to install custom Rom or do you want stock Rom. If you want stock Rom why did you root?
Also as ante0 asked did you decrypt?

ante0 said:
Which SuperSU did you install?
And did you decrypt first if the supersu you're installing needs decryption?
If you didn't 'Format Data' in TWRP and SuperSU removes encryption you're trying to boot with an encrypted /data partition which doesn't decrypt.
Click to expand...
Click to collapse
So at first, I flash the SuperSU files and data files from here: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. It worked perfectly fine and my storage was decrypted. But then i got into another issue so I rebooted into twrp, wiped, format data, and installed the files again (SuperSU and both data files) from the same link above. If my phone is already decrypted, and I wiped and format the data, I only need to flash SuperSU and the data files? I'm lost and this is a new phone.
Can you please give me a step by step rundown of what I need to do to get my phone back working. Again, the phone is a MHA-L29C636B110 with the bootloader unlocked, TWRP 3.1.0-1-hi3660 installed. Whenever I flash something or even factory reset it reboots for a while and then goes back to eRecovery.

IronSingh said:
Do you want to install custom Rom or do you want stock Rom. If you want stock Rom why did you root?
Also as ante0 asked did you decrypt?
Click to expand...
Click to collapse
At first everything went well and I decrypted the data. I wanted a custom ROM but I knew it would be a lot of work and I could get into a lot of problems. But then the SuperSU kept giving me the notification that the binary needs to be updated. So I downloaded the SuperSU v2.46 update on the Chainfires website and gave me a bootloop. I then went back to TWRP, wiped, format data, and sideload flashed the SuperSU files and both data files from: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986 which ended up giving me a reboot loop back to eRecovery.

Ok
Do This.
nicenice00 said:
If your Model is MHA-L29 you can try this.
Load and Exract to SD card .
Push Power button and vol+/vol- to recovery mode.
I think it can help you. (Sorry, my english isn't good)
drive.google.com/open?id=0B9GG_Oe0gQDyUWlCS3lTRm5IOUE
Click to expand...
Click to collapse
Download the file extract it to your internal Storage.
So there should be a Folder in your /sdcard folder named dload and there should be update.app file in that folder.
while you are in TWRP you can simply do adb push /dload /sdcard/dload from command line

Ben_Li said:
So at first, I flash the SuperSU files and data files from here: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. It worked perfectly fine and my storage was decrypted. But then i got into another issue so I rebooted into twrp, wiped, format data, and installed the files again (SuperSU and both data files) from the same link above. If my phone is already decrypted, and I wiped and format the data, I only need to flash SuperSU and the data files? I'm lost and this is a new phone.
Can you please give me a step by step rundown of what I need to do to get my phone back working. Again, the phone is a MHA-L29C636B110 with the bootloader unlocked, TWRP 3.1.0-1-hi3660 installed. Whenever I flash something or even factory reset it reboots for a while and then goes back to eRecovery.
Click to expand...
Click to collapse
what did you wipe (Other than tapping the 'Format Data' button)?
If dload update doesn't fix it, as mentioned above, you could (You should!!) update to B181 using this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Download HWOTA_2017050101_Base.zip, HWOTA_2017050101_Windows.zip (if you're on Windows), HWOTA_2017050101_Linux.zip (If you're on Linux) and HWOTA_2017050101_MHA.zip.
Extract all to the same folder.
MHA-L29C636B181 firmware: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v85049/f2/full/update.zip
MHA-L29C636B181 public data zip: http://update.hicloud.com:8180/TDS/...49/f2/full/public/update_data_full_public.zip
MHA-L29C636B181 hw data zip: http://update.hicloud.com:8180/TDS/...hw_spcseas/update_full_MHA-L29_hw_spcseas.zip
Place update.zip, public zip and hw zip in HWOTA/update/ folder.
Rename update_data_full_public.zip to update_data_public.zip
Rename update_full_MHA-L29_hw_spcseas.zip to update_all_hw.zip
Run update.bat if windows, ./update.sh from terminal if Linux.
Put phone in Download mode (Vol down+power+usb plugged in).
Select Same Brand Update when it asks.
Select Script Update Directory when it asks.
If all went well you should be on B181.

IronSingh said:
Ok
Do This.
Download the file extract it to your internal Storage.
So there should be a Folder in your /sdcard folder named dload and there should be update.app file in that folder.
while you are in TWRP you can simply do adb push /dload /sdcard/dload from command line
Click to expand...
Click to collapse
So there is a file named TWRP in the /sdcard when I am on TWRP. So I move the dload.rar into the /sdcard/TWRP then flash it? I apologize if this sounds stupid I want clear specifications so I won't fall under any more problems

No you have to extract dload on your computer the move that folder to the phone.
This will Restock your device and lock it.
If you don't want to do that, I suggest you download RomAur from here
Download the following files
RomAur B182 v1.5
KangVip Framework for v1.5
L29C636 Data Files B181
Then copy them to your Internal or External Drive
Then follow from Step 7
7 - Make a FULL Wipe if come from another FW, before installing the ROM on TWRP(DALVIK-CACHE,CACHE,DATA,SYSTEM)
8 - Install Rom
9 - Install Data Files
10 - Reboot
11 - Install KangVip - Optional
12 - Enjoy

IronSingh said:
No you have to extract dload on your computer the move that folder to the phone.
This will Restock your device and lock it.
If you don't want to do that, I suggest you download RomAur from here
Download the following files
RomAur B182 v1.5
KangVip Framework for v1.5
L29C636 Data Files B181
Then copy them to your Internal or External Drive
Then follow from Step 7
7 - Make a FULL Wipe if come from another FW, before installing the ROM on TWRP(DALVIK-CACHE,CACHE,DATA,SYSTEM)
8 - Install Rom
9 - Install Data Files
10 - Reboot
11 - Install KangVip - Optional
12 - Enjoy
Click to expand...
Click to collapse
THANK YOU SO MUCH IT WORKED! In all honestly, I cannot thank you enough as I've had issues with this phone for the past 3 days and it's been messing with my head. Again, thank you so much for helping me out today! You are a great member of this wonderful community

Ben_Li said:
THANK YOU SO MUCH IT WORKED! In all honestly, I cannot thank you enough as I've had issues with this phone for the past 3 days and it's been messing with my head. Again, thank you so much for helping me out today! You are a great member of this wonderful community
Click to expand...
Click to collapse
Just out of curiosity did you get the custom Rom or did you go stock?
It's no problem,I was once where you are. I wanst born with knowledge someone shared it with me and the least I can do is share it back.

I flashed the custom ROM. I tried it at first but I didn't wipe the system. This time I did and it worked like a charm thank you for everything I look forward using this device for the next few years

You can done follow link .
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656

newyesor said:
You can done follow link .
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Click to expand...
Click to collapse
Everything was fix thank you though

That link is a good way for comeback .

Sorry guys i have same problem but with L09, can someone give me files for L09 ?
Thanks a lot

[Rooted] [Q] I uninstalled Google Playstore HELP!!

I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help

GphonePrince said:
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
Click to expand...
Click to collapse
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!

GphonePrince said:
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
Click to expand...
Click to collapse
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/

GphonePrince said:
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
Click to expand...
Click to collapse
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I will look into it thanks

Backup and Restore - a Hybrid Method (Android 9)

I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup Boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img (extract from ap section of downloaded firmware for stock) or install UPie
2. Restore Boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files to /system/system
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.

If anyone can think of another system directory which I can backup and restore please let me know.

physwizz said:
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img
2. Restore boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
Click to expand...
Click to collapse
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.

Jeremy_J7 said:
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWinRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Click to expand...
Click to collapse
I think the system settings are stored in /data
I'll add it to the list.

physwizz said:
I think the system settings are stored in /data
I'll add it to the list.
Click to expand...
Click to collapse
Test it before you add to the list, can't be giving these people false information bro ?

Jeremy_J7 said:
Test it before you add to the list, can't be giving these people false information bro
Click to expand...
Click to collapse
True

I debloated from here
https://forum.xda-developers.com/galaxy-a20/development/debloat-samsung-a20-variants-t4070957
Then I added the updated camera from Ultimate Pie.
My app folders are here
https://mega.nz/file/dtkkES5L#YfHwWC3rlswwYUeA_cdUESCMQo8rvq8k8n20N-oc-8w

Alright will take a look, is this bootloader specific?

Jeremy_J7 said:
Alright will take a look, is this bootloader specific?
Click to expand...
Click to collapse
Not sure.
If it doesn't work it might reboot into recovery and then you need to copy and paste your own /app and /priv-app folders back in place.

@jajk
Try this

@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?

jajk said:
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
Click to expand...
Click to collapse
If you're talking about the red text that talks about 'official binaries' when booting after you flash TWRP (FRP LOCK) then there's a very easy fix.

@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....

jajk said:
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
Click to expand...
Click to collapse
I got that because i was using old data
solved by doing a clean install
The data was then good in future

@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different

jajk said:
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
Click to expand...
Click to collapse
You didn't restore old data?
Clean install?

@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....

jajk said:
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
Click to expand...
Click to collapse
What does red writing say?

@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....

jajk said:
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
Click to expand...
Click to collapse
I've had that twice
1. When I forced reboot before UPie was finished installing
2 when I didn't wipe caches , data and system before installing UPie
Could also be Samsung Conspiracy Theorist Detection Program (SCTDP) lol