Database Info

[guide][how to change the boot animation and bootlogo][root required]

Hello to everyone.
In this guide I will explain you How to Change the Boot Animation & Bootlogo of your phone by an easy and detailed step by step process.
So as the name suggests Bootlogo is the first slide that appears when you power on your phone and Boot Animation is the animation that play there after till the device if fully switched on.
THINGS NEEDED:-
1) A rooted phone.
2) Custom Recovery (CWM or TWRP)
3) Root Explorer App ( Available on Play Store )
NOTE - There are no particulars in case of bootlogos and boot animations, that means any particular bootlogo or boot animation will work on your device if its screen resolution is same as your phone's.
WORD OF CAUTION - Though the method is universal and works for everyone, If anything goes wrong and you brick your device, I am not to be held responsible. ( In case you soft brick your device, flashing the stock firmware on your device and then wiping the cache through recovery will fix it)
CHANGING THE BOOTLOGO :-
1) To change the bootlogo and then apply a custom one, first you need to select the bootlogo that suits you and download it's zip file. Various bootlogos are available on the internet and you will find the best ones in the XDA Themes and Apps forum. So head on to the forum and download the bootlogo zip file that suits you the most.
2) After downloading the zip file reboot your phone to recovery
3) Select 'install zip' in the recovery menu and then browse through your folders and select the bootlogo zip file. Install the zip.
BOOM! You have successfully changed your bootlogo. Reboot your phone to see the change.
CHANGING THE BOOT ANIMATION :-
Now changing this ain't as easy as changing the bootlogo since here the zip is not flashable.
1) As mentioned in the above process download the boot animation zip file that you like the most which you will again find in the XDA Themes and Apps forum.
2) After downloading the zip, open the Root Explorer App and head to the place where you have downloaded the boot animation.(If the file name is bootanimation.zip then for now rename it to something else)
3) Copy the zip file and paste it to system\media which is located in the internal memory of the phone. (You will see that there already exists a bootanimation.zip file which is the original boot animation of your phone)
4) Now rename the original boot animation file to something else and the one you downloaded to bootanimation.zip
5) After that long press the boot animation you downloaded and see the permissions. Make the following changes if it ain't already. Grant the read permission to all three I.e. owner, group and others and the write permission to owner only thus making the permissions as rw-r-r.
BAM! You successfully changed your boot animation. Reboot your phone to see the changes.
If you want some help or underwent a problem, feel free to comment.
Please hit the thanks button if I helped because just saying it won't do me any good.
Cheers!

Error on OTA [EMUI 3.1 6.1.1]

Hello,
I am trying to update my H60-L12 from 6.1.1 to 6.1.16 (and then beyond) using OTA.
I have my phone rooted and with custom recovery. I know I have to unroot and restore stock recovery to get the OTA updates. Yesterday I learnt also that to get 6.1.16 I have to use TAPVPN to connect to the internet via Singapore (thanks to @bcostea for the hint).
Now I find that my phone downloads the update and when it tries to install there is an error in the process at the 6%.
I learnt that the update process logs its progress in the file /splash2/recovery_log
There I find this:
Code:
UI percent:5%.
file "/system/framework/com.google.widevine.software.drm.jar" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/framework/com.google.widevine.software.drm.jar", "6189c99c76c84310f35b967e768440088e140f78", "7b4afc644b4d388fe159120f434f769a635a8c5e")
str1:/system/framework/com.google.widevine.software.drm.jar, str2:6189c99c76c84310f35b967e768440088e140f78
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=231: err_no = 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=233: push binary errno 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=238: assert info: assert_filename:/system/framework/com.google.widevine.software.drm.jar
E:assert failed: apply_patch_check(E:
It seems that my com.google.widevine.software.drm.jar is not the one expected by the process.
That makes some sense, as after I installed the full stock rom, I was not able to apply the pa_gapps (some error related to not being possible to install them in a system that did not had a previous version installed to avoid conflicts) (more details on this are available if anybody has a hint or is willing to trobuleshoot it).
Thing is that I applied open_gapps, which are working just fine, but seem to have a different com.google.widevine.software.drm.jar version.
Till 6.1.1, I was able to replace the com.google.widevine.software.drm.jar file in my phone with one from the system.img of the Stock ROM, and then the update was working.
With 6.1.1 I have not been able to find the right file (one with a SHA-1 hash of 7b4afc644b4d388fe159120f434f769a635a8c5e, seems to be necessary).
I have 3 files with hashes:
6189c99c76c84310f35b967e768440088e140f78
654d36de1c8e9e84979a67e897f36dc17a6f7565
bb6bfd30b3d6d03ecf9531e37bcdb0b5a8123e11
They come from stock, from pa_gapps and from open_gapps, but none of them work.
I put them in the \system\framework folder, but the update still fails with the same error.
Can anyone give me a hint? I am going to try by deleting the file, as I have seen that in the log there is one that is not found and the process does not complain that much.
Maybe someone has the right file in this phone and can send it to me. That would be great!!
Thanks in advance!

Well, it seems I managed to make it work.
Instructions below are without warranty. You know that. It's your phone, if you break it, it's your fault. Not mine. You acknowledge that.
Here is how I did it (if you don't know how to execute any of the steps, just google. Instructions have been provided a million times on how to boot in recovery, how to flash an image or how to do a full backup from custom recovery...):
1. I downloaded the full image of the release I had in my phone (I.e. 6.1.1)
2. Using Huawey Upgrade Extractor I extracted system.img and recovery.img
3. I restarted into custom recovery (TWRP) and took a full backup of my phone to the SD. I then removed the SD.
4. I restarted in fastboot mode and using fastboot.exe I flashed recovery.img and system.img (in my case that did not remove anything from my phone, but as I said before, I took a backup beforehand, just in case).
5. I rebooted the phone. Everything was working just fine.
6. I used TAPVPN app to connect through Singapore, so I could get the update to 6.1.16.
7. The update downloaded and installed as expected.
8. Then I used again TAPVPN to get 6.2.1.
9. Same result: download and installation as expected.
10. Then I rooted again and installed custom recovery by using Honor Multi-Tool.
I hope this helps.

Error during shield update

Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?

bird12358 said:
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
Click to expand...
Click to collapse
some more information might help people help you mate, are you rooted, do you have a custom recovery installed or are you running a custom rom? things like that help us alot

I user to be as root. But I restore factory setting ans I still have thé error.
Should i made an other thing to suppress thé root settings.?

Yes Mate I thought no so do you have a custom recovery installed
Sent from my HTC One using Tapatalk

I don t think I have that recovery installed. Where could I find this?

bird12358 said:
I don t think I have that recovery installed. Where could I find this?
Click to expand...
Click to collapse
Turn off your tablet then hold volume down and the power button untill you get to the boot loader then use the volume down button to select recovery and press power if you have a custom recovery it will bot to it and it will say team win recovery
Sent from my HTC One using Tapatalk

It seems I don t have a custom recovery. How should I do nos?

[APP] [T285] [2017/12/08] Boot Logo Changer

Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer

device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked

gian20 said:
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
Click to expand...
Click to collapse
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.

gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16

gian20 said:
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.

gcrutchr said:
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
Click to expand...
Click to collapse
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)

Unable to change Boot Logo
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
Click to expand...
Click to collapse

SM T285 flash wrong bootlogo.zip
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:

hassansys2 said:
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.

soaib333 said:
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.

gcrutchr said:
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
Click to expand...
Click to collapse
yes sir the jpg file is around 600 kb..... sir please help me..... :crying::crying::crying::crying::crying::crying:... please tell me sir what can i do for recover my device... sir please...... please sir :crying::crying::crying::crying::crying::crying::crying:

gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
sir please, can you send me stock boot logo tar.md5 file for SM-T285 ...... beacuase my phone is bricked.. only download mode is working...... if i flash the orignal bootlogo.tar.md5 i hope it will recover please sir help me.... i request you sir please :crying::crying::crying::crying::crying::crying:

I have a huge problem. I made the .jpg file too big and now the tablet won't boot except for DOWNLOAD MODE. I wasn't able to backup so I just downloaded the param.ifs from this reply.
gian20 said:
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Click to expand...
Click to collapse
Now I am using Windows 7 Heimdall to flash this. Except with this I am unable to flash because it's showing "Error: Failed to retrieve config descriptor."
Need help ASAP
Update: After a few tries, now it says
"Initializing Protocol...
Error: Failed to send data!Releasing device interface...
Solution: Used Odin. Basically, using 7zip, packed the param.lfs to a tar file, then packing that to a gzip file, then prooding to flash via ODIN

Any one have stock param.tar file for flashing on sm-t285?? Plz help me? ? ?

Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working

Darksnite said:
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Click to expand...
Click to collapse
How big is the image you are trying to install?

gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 150 kb i dont have it now but i can get it again but i did make sure the picture was below 200 kb

And when i factory data reseted the phone it still have the same logo

gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked

Darksnite said:
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Click to expand...
Click to collapse
You need yo rename your image to: logo.jpg
Then use 7zip or winrar to open bootlogochanger. replace the logo.jpg in the zip file with your logo.jpg

no-verity-opt-encrypt-6.1 - Updater process ended with ERROR: 1

I'm currently trying to root my Samsung S8+ (G955FD). I've followed the TWRP guide, step by step, but I've run into a roadblock trying to flash no-verity-opt-encrypt-6.1.
I've repeated the steps from the TWRP multiple times, but every time i attempt to flash no-verify it prints:
...
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/no-verity-opt-encrypt-6.1.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
If i attempt to install the no verity with the 'Zip signature verification' ticked, It prints the same but instead of "Updater process ended with ERROR: 1" it prints "Zip signature verification failed!".
I've tried multiple different mirrors, and verified the hash, so I'm not exactly sure what Zip signature is.
I accidentally attempted to boot into system after installing TWRP for the first time and got stuck on the boot-loop, and i assume it's still that way, in a boot-loop. I did a complete factory reset prior to attempting this. I'm 99% sure I enabled USB de-bugging in dev settings. I've tried wiping the preload partition to get rid of the "Failed to mount /preload message". I have no backup of anything. I hope I'm not leaving out any info..
P.S - I do recall getting some pretty big errors while attempting to format data partition. Here is a imgur link of what it printed.. , but after repeating the steps from TWRP, these errors are nowhere to be found.
P.P.S - At least let me know if i need to buy a new phone

I should have thought to include this, but here is the recovery.log https://pastebin.com/vRNUgNdU
Edit: Sorry for adding a new reply, i didn't realise i could edit

Lexiannn said:
I'm currently trying to root my Samsung S8+ (G955FD). I've followed the TWRP guide, step by step, but I've run into a roadblock trying to flash no-verity-opt-encrypt-6.1.
I've repeated the steps from the TWRP multiple times, but every time i attempt to flash no-verify it prints:
If i attempt to install the no verity with the 'Zip signature verification' ticked, It prints the same but instead of "Updater process ended with ERROR: 1" it prints "Zip signature verification failed!".
I've tried multiple different mirrors, and verified the hash, so I'm not exactly sure what Zip signature is.
I accidentally attempted to boot into system after installing TWRP for the first time and got stuck on the boot-loop, and i assume it's still that way, in a boot-loop. I did a complete factory reset prior to attempting this. I'm 99% sure I enabled USB de-bugging in dev settings. I've tried wiping the preload partition to get rid of the "Failed to mount /preload message". I have no backup of anything. I hope I'm not leaving out any info..
P.S - I do recall getting some pretty big errors while attempting to format data partition. Here is a imgur link of what it printed.. , but after repeating the steps from TWRP, these errors are nowhere to be found.
P.P.S - At least let me know if i need to buy a new phone
Click to expand...
Click to collapse
P.P.S - At the worst case your would only need to flash stock firmware.
You will always get the error message when your first format your data through TWRP.
It seems that the no- verity-opt-encrypt zip is causing the same issues as yours mainly on android 9 ( pie ) with other people to.
Your can repeat your TWRP proceedure but instead of using the no- verity-opt-encrypt zip use the one from this guide
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
You will probably have to add ' quota ' to the file name.

spawnlives said:
You will probably have to add ' quota ' to the file name.
Click to expand...
Click to collapse
Sorry, but I don't fully understand what you mean by this. I literally just add the word 'quota' to the name of the .zip file? Just quota? Does it need to be in a specific order, letter case or with or without quotations?
I can't seem to find a solid answer on the thread.

Lexiannn said:
Sorry, but I don't fully understand what you mean by this. I literally just add the word 'quota' to the name of the .zip file? Just quota? Does it need to be in a specific order, letter case or with or without quotations?
I can't seem to find a solid answer on the thread.
Click to expand...
Click to collapse
I normally add after forceenrypt before the date.
Downloaded zip file
Disable_Dm-Verity_ForceEncrypt_11.02.2020
Change to
Disable_Dm-Verity_ForceEncrypt_quota_11.02.2020

Lexiannn said:
I'm currently trying to root my Samsung S8+ (G955FD). I've followed the TWRP guide, step by step, but I've run into a roadblock trying to flash no-verity-opt-encrypt-6.1.
I've repeated the steps from the TWRP multiple times, but every time i attempt to flash no-verify it prints:
If i attempt to install the no verity with the 'Zip signature verification' ticked, It prints the same but instead of "Updater process ended with ERROR: 1" it prints "Zip signature verification failed!".
I've tried multiple different mirrors, and verified the hash, so I'm not exactly sure what Zip signature is.
I accidentally attempted to boot into system after installing TWRP for the first time and got stuck on the boot-loop, and i assume it's still that way, in a boot-loop. I did a complete factory reset prior to attempting this. I'm 99% sure I enabled USB de-bugging in dev settings. I've tried wiping the preload partition to get rid of the "Failed to mount /preload message". I have no backup of anything. I hope I'm not leaving out any info..
P.S - I do recall getting some pretty big errors while attempting to format data partition. Here is a imgur link of what it printed.. , but after repeating the steps from TWRP, these errors are nowhere to be found.
P.P.S - At least let me know if i need to buy a new phone
Click to expand...
Click to collapse
i have solution brother
the problem is Twrp Use old Twrp

Abdilaahi said:
i have solution brother
the problem is Twrp Use old Twrp
Click to expand...
Click to collapse
Which version did you use?

I encountered the same issue with my old but beloved Redmi 3S. Used TWRP 3.2.3-4 (or older), that did the trick.