Database Info

TWRP Failed to make backup folder

Today I was trying to back everything up because I needed to do a clean install. I used to have CMW, and it would work perfectly. Few days ago I switch to TWRP because of its friendly UI. Everytime I try to make a backup, I get this "Failed to make backup folder". When I go to the mount tab, or explorer, it shows my sd card and the folder named TWRP...is there any solution to this? Or should I switch back to cmw?
Thanks

elias.acab said:
Today I was trying to back everything up because I needed to do a clean install. I used to have CMW, and it would work perfectly. Few days ago I switch to TWRP because of its friendly UI. Everytime I try to make a backup, I get this "Failed to make backup folder". When I go to the mount tab, or explorer, it shows my sd card and the folder named TWRP...is there any solution to this? Or should I switch back to cmw?
Thanks
Click to expand...
Click to collapse
If you're using the version of TWRP modified to work with SELinux (needed for KitKat 4.4.x ROMs) you may need to shorten the name of the target file before starting the backup.

benyto said:
If you're using the version of TWRP modified to work with SELinux (needed for KitKat 4.4.x ROMs) you may need to shorten the name of the target file before starting the backup.
Click to expand...
Click to collapse
Thanks a lot!! that fixed my problem. One more question: TWRP backups dont have the boot.img file in their folders. I read that it automatically flashes the boot.img when Im restoring the backup. Will it still flash it even though Im s-on?
Thanks

elias.acab said:
Thanks a lot!! that fixed my problem. One more question: TWRP backups dont have the boot.img file in their folders. I read that it automatically flashes the boot.img when Im restoring the backup. Will it still flash it even though Im s-on?
Thanks
Click to expand...
Click to collapse
TWRP should backup your /boot partition to the boot.emmc.win file. As far as I know it should also be able to restore this, even if you are S-On. However, I am not positive about that

[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.

Pre Rooted fw for the Z5

I am looking for a pre Rooted firmware, downloaded a custom Fw from XperiFirm and thought it'd be Rooted but it wasn't.
So I created a Pre Rooted FW using PRF Creator.
Done that, flashed the rom, using flash tool.
And somehow it didn't work.
So I was just wondering is there any pre Rooted firmwares out there I could download and flash from flash tool.
Also without losing any apps/app data if possible.
Thank you, please not my phone has not got a recovery.

You cannot flash a pre-rooted firmware without recovery so you need to unlock the bootloader and root
Sent from my E6653 using Tapatalk

No worries thank you.
I have tried unlocking the boatloads but keep getting errors.
My BL is unlockable

bjmag94 said:
No worries thank you.
I have tried unlocking the boatloads but keep getting errors.
My BL is unlockable
Click to expand...
Click to collapse
Hi
Did you try this ? ([GUIDE] StockROM -> # GUIDE -> UNLOCK BOOTLOADER)
What errors are you getting ?

I followed the guide off the Sony website to unlock the bootloader.
And I'm not sure what the errors are, I will have have to post them here soon when I get back on the computer
Emilen942702 said:
Hi
Did you try this ? ([GUIDE] StockROM -> # GUIDE -> UNLOCK BOOTLOADER)
What errors are you getting ?
Click to expand...
Click to collapse

bjmag94 said:
And I'm not sure what the errors are
Click to expand...
Click to collapse
Settings> Developer Options> Enable OEM unlock
set that and then try unlocking the bootloader

Awesome thanks worked for me, now my bootloader is unlocked can I flash a recovery then the PRF I created without losing any data?
SnowManWales said:
Settings> Developer Options> Enable OEM unlock
set that and then try unlocking the bootloader
Click to expand...
Click to collapse

bjmag94 said:
Awesome thanks worked for me, now my bootloader is unlocked can I flash a recovery then the PRF I created without losing any data?
Click to expand...
Click to collapse
I just looked at my phone after unlocking the Bootloader and it has deleted all my photo's off the phone, and some that I can not get back of my son, is there any way that I can get these back, I used FlashTool to unlock the Bootloader

bjmag94 said:
I just looked at my phone after unlocking the Bootloader and it has deleted all my photo's off the phone, and some that I can not get back of my son, is there any way that I can get these back, I used FlashTool to unlock the Bootloader
Click to expand...
Click to collapse
do you guys even try to think about a data backup before messing around and doing things that are able do delete your stuff?
Photos were stored on internal or SD card?
SD will be easy (if you haven't writen a lot of data on it).
Internal could be difficult...

They were on my internal.
Yes I did think about it, but only backed it up yesterday and didn't realise that there were more photo's taken since, because my partner also uses it to take photo's because of the camera quality..
So I only lost about 20 photo's but still beside the point..
I didn't think that unlocking your bootloader would delete anything?
So now I am about to look into flashing recovery onto the phone so I can flash the firmware that I created..
Would you suggest backing up my data again prior to flashing the recovery, and then the new firmware?
And will I lose all my app data or is there a way of backing that up as well?
Also how would I flash the recovery?
Thank you!
MKRashka said:
do you guys even try to think about a data backup before messing around and doing things that are able do delete your stuff?
Photos were stored on internal or SD card?
SD will be easy (if you haven't writen a lot of data on it).
Internal could be difficult...
Click to expand...
Click to collapse

I know your problem, I#ve also all photos of my children on my mobile, but exclusivly on the SD card and backup them with Foldersync once a day (to a 256 GB Flashdrive on my fritzbox)
Your Problem now is, that with each file operation on you internal storage (Android operations also count), the bytes of your pictures vanish.
If you're rooted (I think so), you should try easus Android Data Recovery, it's the only tool I know, that can handle internal storage from Windows:
http://www.easeus.com/android-data-recovery/android-phone-internal-storage-recovery.html
I use a lot of easus tools and I always get it back up and running, so give it a shot and good luck!
Unlocking the Bootloader just deletes your TA Partition and with that you DRM Keys. So without a TA Backup or a DRM Fix, your camera quality will descent drastically.

Thank you, I am not rooted as of yet..
But I will still give that a shot and see what I can recover..
Hopefully I haven't lost it completely, oh well that will teach me for next time, so how will I flash the recovery onto my phone?
So then I can flash the pre-rooted firmware to get root access.
Is there any simple guides to follow? Or simple methods, like a code to run through fastboot cmd?
Thank you once again in advanced..
MKRashka said:
I know your problem, I#ve also all photos of my children on my mobile, but exclusivly on the SD card and backup them with Foldersync once a day (to a 256 GB Flashdrive on my fritzbox)
Your Problem now is, that with each file operation on you internal storage (Android operations also count), the bytes of your pictures vanish.
If you're rooted (I think so), you should try easus Android Data Recovery, it's the only tool I know, that can handle internal storage from Windows:
http://www.easeus.com/android-data-recovery/android-phone-internal-storage-recovery.html
I use a lot of easus tools and I always get it back up and running, so give it a shot and good luck!
Unlocking the Bootloader just deletes your TA Partition and with that you DRM Keys. So without a TA Backup or a DRM Fix, your camera quality will descent drastically.
Click to expand...
Click to collapse

1. Flash Recovery "twrp-3.0.2-0-E6653-20160504.img" (extract the zip before) via fastboot
2. Flash a rootable Customkernel (boot.img) (extract Z5_AndroPlusKernel_Permissive_v36.zip) via fastboot.
3. Flash "SuperSU-v2.76.zip" (copy the zip to SD or internal) via TWRP
Download the files here: https://www.dropbox.com/sh/6424n9sop6kqmj7/AADtEiR3EeZXxedR7_g9lA-ma?dl=0
I've rooted my brand new Z5 a week ago with these files.
4. Do a DRM fix to get the camera quality back you're used to, without you will have really bad pictures in low light condition:
http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
If you want to do a fresh systemflash before rooting your device, use Flashtools xperifirm to get the latest Marshmallow 6.0.1 Stock Rom
Do not check any point on "wipe" for flashing, unless you want to setup the whole phone new. It's possible that you have to if you update from 5.1.1
KR
Rashka

Thank you I am already running marshmallow 6.0.1.
I am using the Custom AU one.
I can't manually root it via SuperSU or anything though, not sure if it is a rootable firmwatte or not..
But how do I flash the recovery?
Sorry I new to all this, I done my Z2 about two years ago, followed a guide off here, but it was more simple for the Z2 than the Z5 I think..
And only had to flash a custom rom and it was already rooted and then had to install busybox to get recovery and done it that way..
But now I would not have a clue what the heck I am doing haha..
I will not lose any data while flashing a recovery will I?
MKRashka said:
1. Flash Recovery "twrp-3.0.2-0-E6653-20160504.img" (extract the zip before) via fastboot
2. Flash a rootable Customkernel (boot.img) (extract Z5_AndroPlusKernel_Permissive_v36.zip) via fastboot.
3. Flash "SuperSU-v2.76.zip" (copy the zip to SD or internal) via TWRP
Download the files here: https://www.dropbox.com/sh/6424n9sop6kqmj7/AADtEiR3EeZXxedR7_g9lA-ma?dl=0
I've rooted my brand new Z5 a week ago with these files.
4. Do a DRM fix to get the camera quality back you're used to, without you will have really bad pictures in low light condition:
http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
If you want to do a fresh systemflash before rooting your device, use Flashtools xperifirm to get the latest Marshmallow 6.0.1 Stock Rom
Do not check any point on "wipe" for flashing, unless you want to setup the whole phone new. It's possible that you have to if you update from 5.1.1
KR
Rashka
Click to expand...
Click to collapse

Why dont your take a backup of the phone via Xperia Companion?
Alternatively, use Titanium Backup (free on Google Play) after you are rooted - before flashing your own ROM
Did you read the WHOLE guide @Emilen942702 linked you to? Especially sections [GUIDE] GENERAL and [GUIDE] StockROM / # GUIDE
If you use AndroPlus kernel v.36 then no need to do the DRM fix as it is already included in the kernel.

MKRashka said:
do you guys even try to think about a data backup before messing around and doing things that are able do delete your stuff?
Photos were stored on internal or SD card?
SD will be easy (if you haven't writen a lot of data on it).
Internal could be difficult...
Click to expand...
Click to collapse
yes, that why i back everything i want to sd card and cloud storage, all automated
sent from my Xperia Z5

I flashed the Kernel and Recovery and installed SuperSU.
And the done the DRM, and now I can not use google play, keep getting an error saying that it can not connect to google play or some crap..
Any easy fixes without having to completely wipe and install a fresh rom?

bjmag94 said:
I flashed the Kernel and Recovery and installed SuperSU.
And the done the DRM, and now I can not use google play, keep getting an error saying that it can not connect to google play or some crap..
Any easy fixes without having to completely wipe and install a fresh rom?
Click to expand...
Click to collapse
Try to clear data/cache/force stop from :
-Google Services Framework (type the three dots in the upper right corner, and tick "display system apps")
-Google Play Store
-Google Play Services
If it doesn't work
Try to delete hosts file from /etc/hosts (with a root explorer) and reboot
And btw, do you have Freedom installed ?

I will give this a try, and yeah I do, about to uninstall it as it keeps changing on me
Emilen942702 said:
Try to clear data/cache/force stop from :
-Google Services Framework (type the three dots in the upper right corner, and tick "display system apps")
-Google Play Store
-Google Play Services
If it doesn't work
Try to delete hosts file from /etc/hosts (with a root explorer) and reboot
And btw, do you have Freedom installed ?
Click to expand...
Click to collapse

bjmag94 said:
I will give this a try, and yeah I do, about to uninstall it as it keeps changing on me
Click to expand...
Click to collapse
That's the reason, try to stop it Belfort uninstall, if you can't then just delete host file
Envoyé de mon E6653 en utilisant Tapatalk

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

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