Related
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S5 Unified (klte): International, Canada, Sprint, TMO
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte
Notice: ATT and VZW are locked. You must unlock them to be able to flash a recovery
Click to expand...
Click to collapse
special credits to @PlayfulGod for his unified device tree
https://github.com/playfulgod
XDA:DevDB Information
[klte][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Samsung Galaxy S 5
Contributors
Phil3759
Version Information
Status: Stable
Created 2014-04-04
Last Updated 2014-04-16
reserved
You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.
PlayfulGod said:
You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.
Click to expand...
Click to collapse
ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code
Phil3759 said:
ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code
Click to expand...
Click to collapse
not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.
TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol
Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.
PlayfulGod said:
not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.
TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol
Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.
Click to expand...
Click to collapse
Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files
Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)
Can you try this:
ensure you are not using the recovery.fstab file in your device tree but the fstab.qcom
adb shell:
Code:
mount /system
/system/bin/toolbox setenforce permissive
Click to expand...
Click to collapse
See if you can now access internal storage in write mode
Phil3759 said:
Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files
Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)
Can you try this:
See if you can now access internal storage in write mode
Click to expand...
Click to collapse
Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.
I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.
Its using the fstab.qcom.
PlayfulGod said:
Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.
I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.
Its using the fstab.qcom.
Click to expand...
Click to collapse
Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users
If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level
Phil3759 said:
Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users
If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level
Click to expand...
Click to collapse
I will give that a try. thanks
img built and linked to tester(s).
PlayfulGod said:
I will give that a try. thanks
img built and linked to tester(s).
Click to expand...
Click to collapse
Thanks,
will watch your thread and wait for testers before wasting more time on it
Phil3759 said:
Thanks,
will watch your thread and wait for testers before wasting more time on it
Click to expand...
Click to collapse
Philz, its boot looping! it doesnt work at all !
leoaudio13 said:
Philz, its boot looping! it doesnt work at all !
Click to expand...
Click to collapse
Can you post a stock recovery.img please!
Phil3759 said:
Can you post a stock recovery.img please!
Click to expand...
Click to collapse
Here you are : https://drive.google.com/file/d/0B3HkAzPm36j4b05kbDNtTVA1ZnM/edit?usp=sharing
I'll test this on Friday. Verizon S5 on it's way that day.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Philz,
Thank You for all you did.
Every time i'm buying a new phone, i have the pleasure to get your recovery "ready to install".
Great work, great support.
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Has this been tested on a 900H Model?
Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk
leoaudio13 said:
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
LoL
Two months!
Hope someone else will test before
Phil3759 said:
LoL
Two months!
Hope someone else will test before
Click to expand...
Click to collapse
U dissapeared since I post u the stock recovery lol. I was wondering
Sent from my SM-G900F using Tapatalk
Hi, you can see my question.
I've try wipe, but only data works. And no change.
I've try to réinstall the custom rom, you can see result.
Ttry to flash stock rom with odin, odin failed.
and try to réinitialise with smart switch ( he say me i havent tow slot for sim, i know). And ... nothing change.
The device has been already root, and i've already change for this custom rom with no problem.
Thanks for your help.
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Just for to be sur, this screenshoot is just a example. Other installation make me the same error.
This rom work really good and other people haven't any problems.
Send me the kernel and I disable /data ecncrypting for you
DThrawn said:
Hi, you can see my question.
I've try wipe, but only data works. And no change.
I've try to réinstall the custom rom, you can see result.
Ttry to flash stock rom with odin, odin failed.
and try to réinitialise with smart switch ( he say me i havent tow slot for sim, i know). And ... nothing change.
The device has been already root, and i've already change for this custom rom with no problem.
Thanks for your help.
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Click to expand...
Click to collapse
do't worry it is normal i explain you
when you format with twr the data is readable
and the first time starting system Samsung encrypt the file so txr can't mount again data
but don't care about it
DThrawn said:
Edit: with format data after wipe data and after reboot on twrp, no red line, i've install the rom. good : i've the rom, bad : the problem is come back.
Click to expand...
Click to collapse
It's all because kernel has encrypted /data and data encrypts after a reboot. Some changes in the kernel solve your problem. Data will mount always after some changes in the kernel
maxx35000 said:
do't worry it is normal i explain you
when you format with twr the data is readable
and the first time starting system Samsung encrypt the file so txr can't mount again data
but don't care about it
Click to expand...
Click to collapse
Forgetten said:
It's all because kernel has encrypted /data and data encrypts after a reboot. Some changes in the kernel solve your problem. Data will mount always after some changes in the kernel
Click to expand...
Click to collapse
Ok, I understand more why it's all my recovery is down. my device work good also with what you said i'm more quiet.
But why reinitialisation with switch, let the same problem. The kernel is not reinitialised to ?
I've try to modify selinux permissions before to install a sound mod and create an folder init.d. Is it possible the problem stay cause that?
DThrawn said:
Ok, I understand more why it's all my recovery is down. my device work good also with what you said i'm more quiet.
But why reinitialisation with switch, let the same problem. The kernel is not reinitialised to ?
I've try to modify selinux permissions before to install a sound mod and create an folder init.d. Is it possible the problem stay cause that?
Click to expand...
Click to collapse
I don't sure about that but you should mount your /data using patched kernel. Send it to pm and I patch them to mount data fully
Forgetten said:
I don't sure about that but you should mount your /data using patched kernel. Send it to pm and I patch them to mount data fully
Click to expand...
Click to collapse
I'm a old beginner, I don't know where is the kernel and I don't know if it's sur to give mine cause i don't know what information of my device is in.
I appreciate your help but i can't give anything what a I don't know.
DThrawn said:
I'm a old beginner, I don't know where is the kernel and I don't know if it's sur to give mine cause i don't know what information of my device is in.
I appreciate your help but i can't give anything what a I don't know.
Click to expand...
Click to collapse
OK. Say. Which ROM do you use?
Forgetten said:
OK. Say. Which ROM do you use?
Click to expand...
Click to collapse
I use the evo-grace V1.2 J7 2016, but I ve never had problem before trying install sound mod with modification of selinux permission.
Unmount data always but not important, but some install, wipe or backup impossible it's new.
Flash before formatting data.
https://www.androidfilehost.com/?fid=24591000424951049
ashyx said:
Flash before formatting data.
https://www.androidfilehost.com/?fid=24591000424951049
Click to expand...
Click to collapse
Thanks, work realy fine. no red line at all.
Also i lose root and the problem come back when i try to reinstall the rom evo-grace, cause she's rooted and she has its own no encrypted file, i think.
DThrawn said:
Thanks, work realy fine. no red line at all.
Also i lose root and the problem come back when i try to reinstall the rom evo-grace, cause she's rooted and she has its own no encrypted file, i think.
Click to expand...
Click to collapse
When you flash anything that modifies or replaces the boot partition you need to reflash the patch afterwards or the data partition will be re-encrypted.
ashyx said:
When you flash anything that modifies or replaces the boot partition you need to reflash the patch afterwards or the data partition will re-encrypted.
Click to expand...
Click to collapse
Yes, i've can make some backup and install like that. It's help me. And now i've install permanetly the rom of max35000, , he have make some good modification. Problem solved with help of you to.
Thanks for have take a time for look that.
Forgetten said:
Send me the kernel and I disable /data ecncrypting for you
Click to expand...
Click to collapse
Hi my bro
Please help me
How can i make disablr / data ecncrypting ??
I have j710f frp on with pattern
Can i open it without losing data ??
---------- Post added at 10:09 PM ---------- Previous post was at 10:00 PM ----------
How can i make a kenel to disable data ecncrypting ??
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Wow man! Someone "ACTUALLY" did it!
I'll try when my f1 arrives
the top corners curves and the margin being small is just killing me :/
But nice work dude
How did you manage to unlock so fast?
1emrys1 said:
How did you manage to unlock so fast?
Click to expand...
Click to collapse
Yeah, how
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
How's the experience using a GSI on this phone? What works and what doesn't? Camera usable?
ffh2303 said:
How's the experience using a GSI on this phone? What works and what doesn't? Camera usable?
Click to expand...
Click to collapse
Open camera is working fine.
Almost all working but all GSI have little bug and u have to fixed it manually
Jio volte not working in some gsi
1emrys1 said:
How did you manage to unlock so fast?
Click to expand...
Click to collapse
Ok lets unlock your device within a second
Dont update your phone before this process
First backup your some data like sms call history to mi cloud with sync on ,(see pic in attachment)
Now enable developer option
In this setting u have to check 4 option.dont forget 4 option
Check devoloper option
Check miui unlock(wait mi server read your device)
Check two types of usb debugging
Now download some photo from miui cloud that u just uploaded see sync on and find my device on
Now use mi unlock tool v2.2.406 or other versions u can try
Hope this time u can unlock .dont forget dont update your phone before unlock
Notch support and Jio Volte support for phh treble based ROMs
Can someone make a flashable zip to add notch support to phh treble based ROMs like how it is for mi 8 and can someone make flashable zip to add Jio Volte support for phh treble ROMs any help would be appreciated!
Have a nice day!
I've got mine unlocked fast because I am an old user of xiaomi and i've unlocked my old phone(also xiaomi phone).
Otherwise u've to wait for 720hrs.
Might clear out abit confusion.
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
do you flash A or B GSI?
thank you
abihakim said:
do you flash A or B GSI?
thank you
Click to expand...
Click to collapse
A gsi
It shows 57hours waiting time before unlock. I'm on miui version 9.6.18.0.
How can I unlock for sure?
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
Hi, I'm quite new here and while I have a general understanding of what you say here, I'm not sure I could follow those instructions without bricking my device by overlooking something or just basic newbie stupidity... Could you make a more detailed guide, please?
PocoSteve said:
Hi, I'm quite new here and while I have a general understanding of what you say here, I'm not sure I could follow those instructions without bricking my device by overlooking something or just basic newbie stupidity... Could you make a more detailed guide, please?
Click to expand...
Click to collapse
after unlock ur device flash twrp then post here i will help you
Pranay nagavolu said:
It shows 57hours waiting time before unlock. I'm on miui version 9.6.18.0.
How can I unlock for sure?
Click to expand...
Click to collapse
you r lucky then not 72 only 57
sankhauaa said:
you r lucky then not 72 only 57
Click to expand...
Click to collapse
Lol
Should we disable force encryption if we want to flash Magisk ?
Hi,
Any place where GSI ROMs are listed ?
That would also be a nice addition to XDA I think
Regards.
Hi everyone. I have a problem that would be the call volume too low! what with the miui 9 I didn't have. now I have the global 10.4.2 .. thanks
Peppone990 said:
Hi everyone. I have a problem that would be the call volume too low! what with the miui 9 I didn't have. now I have the global 10.4.2 .. thanks
Click to expand...
Click to collapse
Easy to fix, problem very good know by me.
Boot to twrp, mount all partitions, flash zip from attachment. Solved
Give a thanks ??
dromaczek said:
Easy to fix, problem very good know by me.
Boot to twrp, mount all partitions, flash zip from attachment. Solved
Give a thanks ??
Click to expand...
Click to collapse
is this attachment works with Pixel Experience (Android 10)?
amit1971 said:
is this attachment works with Pixel Experience (Android 10)?
Click to expand...
Click to collapse
Yes, it should work.
But dont forget on TWRP mount vendor partition first (before flash!!) (this zip dont check is correctly mounted, if not mount it doesnt do anything)
dromaczek said:
Yes, it should work.
But dont forget on TWRP mount vendor partition first (before flash!!) (this zip dont check is correctly mounted, if not mount it doesnt do anything)
Click to expand...
Click to collapse
I had to flash SAR-TWRP for Pixel Experience Android 10.
Do i need to flash Official TWRP for this? That attachment doesn't work with SAR-TWRP.
amit1971 said:
I had to flash SAR-TWRP for Pixel Experience Android 10.
Do i need to flash Official TWRP for this? That attachment doesn't work with SAR-TWRP.
Click to expand...
Click to collapse
Then i dont know, i use this patch on xiaomi EU and pixel experience official (not 10), works perfectly.. try... if doesn work, fix script -> maybe mount poin of vendor partition is other, and dont install
dromaczek, do you have patch revert zip?
dromaczek said:
Easy to fix, problem very good know by me.
Boot to twrp, mount all partitions, flash zip from attachment. Solved
Give a thanks ??
Click to expand...
Click to collapse
Thank you for your effort dromaczek!
Can you please tell me if i need to mount
-Cache
-Data
-System
-Vendor
-Usb-OTG
-and click on Mount system partition read only
for this to work?
Thank you
inglar2k said:
dromaczek, do you have patch revert zip?
Click to expand...
Click to collapse
No, i dont have, make backup vendor partition
---------- Post added at 10:03 AM ---------- Previous post was at 10:02 AM ----------
TATA_MATA said:
Thank you for your effort dromaczek!
Can you please tell me if i need to mount
-Cache
-Data
-System
-Vendor
-Usb-OTG
-and click on Mount system partition read only
for this to work?
Thank you
Click to expand...
Click to collapse
hmm, i think only ventor mount should you have...
dromaczek said:
No, i dont have, make backup vendor partition
---------- Post added at 10:03 AM ---------- Previous post was at 10:02 AM ----------
hmm, i think only ventor mount should you have...
Click to expand...
Click to collapse
I am sorry, I didnt understand. You believe that I only need to mount Vendor and nothing else? Thank you
I created a script that'll ease Custom ROM installation on A/B devices. The script is generic and will work w/ any rom, device.
General flash instructions:
-Flash OxygenOS
-Flash your Custom ROM of choice
-Flash Finalize.zip
-Boot to System
Download finalize script from here
#######################################
For the intellectuals: This script copies firmware to both slots, clears dalvik-cache and deletes the useless India partition.
Hope this saved you guys some headache while flashing ROMs.
Good job
Sent from my OnePlus6 using XDA Labs
Links off
Link not found.
anhenrique said:
Links off
Click to expand...
Click to collapse
kaziupal said:
Link not found.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261712574
New script in the OP, look there again
I used this same zip on my Motorola G7 Power device. It worked well and is no doubt a life saver. Does anyone know how this is different than finalize zip? I guess I could take a look inside both of them and try to determine what the differences are that way....
There's Finalize.zip I found and I think it is easier. Bacause all you have to do is flash the zip file after installing OOS and ROM with built-in TWRP, then format data and reboot to system. No reboot to recovery in between and save you time.
tiga016 said:
There's Finalize.zip I found and I think it is easier. Bacause all you have to do is flash the zip file after installing OOS and ROM with built-in TWRP, then format data and reboot to system. No reboot to recovery in between and save you time.
Click to expand...
Click to collapse
Link ?
lazye53 said:
Link ?
Click to expand...
Click to collapse
Finalize zip: https://androidfilehost.com/?fid=8889791610682890605
Finalize also deletes India partition.
Flash OOS, flash rom, flash finalize, format data, reboot system.
For some info on finalize see op on Pixen here: https://forum.xda-developers.com/on...ross-device-development/rom-pixen-os-t3969005
Edit
PokemonTotalWar said:
https://androidfilehost.com/?fid=4349826312261712574
Click to expand...
Click to collapse
Stahp
Prakyy said:
Stahp
Click to expand...
Click to collapse
Did you take it down for a reason? It's still accessible through Lineage's website, and people are asking for it. Ask a mod to lock your thread if you don't want any more posts on it, brother
anhenrique said:
Links off
Click to expand...
Click to collapse
Updated w/ AFH link
PokemonTotalWar said:
Did you take it down for a reason? It's still accessible through Lineage's website, and people are asking for it. Ask a mod to lock your thread if you don't want any more posts on it, brother
Click to expand...
Click to collapse
I said stop because you are posting incorrect file. Anyways, I also made a script called "Finalize.zip" which is the one I suggest people use and I've updated the thread to reflect the same.
Didn't check on XDA for a while cuz it wasn't on my mind, really.
Prakyy said:
I said stop because you are posting incorrect file. Anyways, I also made a script called "Finalize.zip" which is the one I suggest people use and I've updated the thread to reflect the same.
Didn't check on XDA for a while cuz it wasn't on my mind, really.
Click to expand...
Click to collapse
Ah, alright. Not trying to be rude, just didn't get the idea from your previous response. Now that Finalize is up on the main post, I'll go ahead and edit my comment to say so
flash713 said:
I used this same zip on my Motorola G7 Power device. It worked well and is no doubt a life saver. Does anyone know how this is different than finalize zip? I guess I could take a look inside both of them and try to determine what the differences are that way....
Click to expand...
Click to collapse
tiga016 said:
There's Finalize.zip I found and I think it is easier. Bacause all you have to do is flash the zip file after installing OOS and ROM with built-in TWRP, then format data and reboot to system. No reboot to recovery in between and save you time.
Click to expand...
Click to collapse
Yes I made the finalize thingy as well lol.
And PiXeN uses that in the official flash instructions so yeah, it works and is definitely the one I recommend you use.
Also, updated the OP.
Prakyy said:
I created a script that'll ease Custom ROM installation on A/B devices. The script is generic and will work w/ any rom, device.
General flash instructions:
-Flash OxygenOS
-Flash your Custom ROM of choice
-Flash Finalize.zip
-Boot to System
Download finalize script from here
#######################################
For the intellectuals: This script copies firmware to both slots, clears dalvik-cache and deletes the useless India partition.
Hope this saved you guys some headache while flashing ROMs.
Click to expand...
Click to collapse
Dude! This ist Genius! Thank you so swirling much!
Prakyy said:
Download finalize script from here
Click to expand...
Click to collapse
using this with no issue at all.
this is what XDA Developers was originally meant for.
thank you very much for this share!
Thank you so much for this. It has made all the flashing hassles much convenient. Works very well on the 6T. I have tried it on couple of different ROMs, no problems yet.
Thank u mister for created this zip fils and script inside in it :good: