Database Users

[HOW TO] Flash PAC-ROM to Cricket / AIO (jflteaio) running I337ZTUUBND3

Hello all,
Using TWRP, I successfully flashed PAC-ROM to my Cricket 'jflteaio' or SGH-i337z ... I337ZTUUBND3, Galaxy S4.
A bit of helpful info for noobs: I rooted with 'towelroot' app --- Google it
And installed TWRP 2.7 from here
At this point...MAKE A BACKUP in TWRP!!! I AM NOT LIABLE FOR BRICKED DEVICES!
Now on to the real fun stuff! Follow these steps to flash Pac-Man ROM:
1. Download the GENERAL jflte rom 'zip' file and not the 'md5sum' from the PAC ROM website:
Download the zip HERE
2. Extract the zipped jflte pac rom into a new folder anywhere in Windows. In the new folder, navigate to this location:
\META-INF\com\google\android\
3. Download and install the free Windows program, NotePad++ --- Google it
4. Right-click on 'updater-script' in the folder \META-INF\com\google\android\
(IMPORTANT: Leave the 'update-binary' file alone; only modify the 'updater-script')
5. click on "Edit with NotePad++".
6. In NotePad++, Under the first word/command "assert" you will see a bunch of commands that start with 'getprop'. Find a spot where it reads '||' and make a new line directly after this. you will see many jflte codenames, so making your new line after you see 2 of the same codename and '||' will do.
7. Make sure the new line you made does not cut any commands in half and copy/paste in these lines of code:
Code:
getprop("ro.product.device") == "jflteaio" ||
getprop("ro.build.product") == "jflteaio" ||
(NOTE: This code will allow install of PAC-ROM on jflteaio)
8. Make sure to save the changes in the file. Close NotePad++.
9. Zip all the files you extracted from the original back up with 7zip or winrar... make sure the file extention is not '.7z' or '.rar'. Must be '.zip' to work. And the files you just zipped have to be in the root location of the zip file. In other words, make sure when you open your new zip, the first folder you see is 'META-INF'... for example in 7zip, you have to select all the elements(there are 5 in total...3 folders and 2 files) in the new folder you created earlier, and right-click and choose 7zip and 'add to archive'.
10. You can now flash the rom in TWRP from an sdcard by following the instructions HERE on XDA
(FINAL NOTE: By the way, make sure NOT to install the AT&T SafeStrap Kernel during the flash, as it may cause the ROM not to boot, and as always, make a TWRP BACKUP before you attempt flashing!)
I do not own any of the software in this guide. A special thanks to all the devs out there who make our lives better!
Best of skill (and luck) to you all!
raydantheman

[TOOL] Updater-Script Auto MAKER

Description:
I developed this program so that i can build my script fast and easily with clicks of button so i thought of sharing my program. This program is designed to auto make your updater-script. You can edit a updater-script or build your own. It has a Graphical interface and is made on Java.
It allow the user to check some boxes and it will build a script.
For beginners they should take a look at ASC by Octanium91 its better than my program and might work better for you.
THREAD NAVIGATION:
1.Descrption,Features,Credits
2.Screenshots
3.Download & Installation,Usage​
Click to expand...
Click to collapse
FEATURES
Auto build an updater-script of your choice
Edit an updater-script
Good for those who are lazy don't want to make a script (like me )
Now Supports ext3,ext4.yaffs2 mounting (change \mountpoint )
Based on JAVA
​
Version Information:
Developed By: Ayan
Version: 1.0.3
Stage: Beta
Bugs
1. Select Rom button does not work
2. Can view updater-script but cannot save.
3. updater-script tested on twrp, CWM, philz recovery thanks to nashj1975.
4.You tell me.
CREDITS To (Do not forget to thank them.)
1. Octanium91 for his android script creator.
2. Karadorde for his great tutorial to write updater-script.
3. coolexe for his script syntax
Mail me at [email protected] for any feedbacks or tell me more mountpoint so that i can add them.
__________________________________________________ __________________________________________________
SCREENSHOTS
​
__________________________________________________ __________________________________________________
DOWNLOAD​
UPDATER-SCRIPT maker v1.0(mediafire)​UPDATER-SCRIPT maker v1.0.3(mediafire)​
INSTALLATION,USAGE​​1. Download Java from here.
2. Download updater-script maker.
3. Extract to any location.
4. Run Updater-script.jar
Code:
[COLOR="Teal"][SIZE="3"][COLOR="DarkRed"]I don't take responsibility of any negative things like, boot looping, bricked device,
broken SD card, your kitten run away with neighbors cat or your phone became a zombie
and a next world war caused by Tool above...[/COLOR][/SIZE][/COLOR]

Using updater-script maker
HOW TO USE​
Don't use "auto build" if you have different mountpoint
You can use the "select updater-script"
You can use the auto-build for ext3,ext4 ;just change the mountpoints.
Using Auto Build
1. Tick your desired boxes .
Code:
You can easily choose between Rom and flashable zip
2. Click on 'Auto Build' button.
3. Choose your rom folder then select open
Code:
[COLOR="Sienna"]Don't use open button to view folder[/COLOR]
if you have no folder then choose desktop
4.Updater-script will be generated and will be previewed
Code:
updater-script is not yet saved, it can be edited
5.After doing any changes press save button
Code:
[B]NOTE:[/B] You can select your save location
Using Select Updater Script
1. Click on 'Select Updater Script'.
2. Choose your updater-script.
3. Edit the updater-script.
4. Copy-paste it to Notepad++ You can save the updater-script to anywhere.
5. Save it as updater-script.

Changelog
12th June 2015-Initial release UpSAM v1.0.0
17th June 2015-UpSAM v1.0.3 release
Included a lot of things
Changed .jar to .exe don't be afraid

Reserved
UpSAM v1.0.1 completed
will release UpSAM v1.0.3 directly
You can send me feedback here.

I've always wanted something like this, I tried ACS but I didn't understand it. Thank you

Thanks mate press the thank button if i helped you.

nashj1975 said:
I've always wanted something like this, I tried ACS but I didn't understand it. Thank you
Click to expand...
Click to collapse
Thanks mate press the thank button if i helped you.

@ayan312002 I tried your tool and it works . I forgot to edit the mountpoints since i have an ext4 emmc device but it worked either way . Thanks and also it works with cwm and philz recovery. :highfive:
EDIT: I've added my mountpoints here they are:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p8", "cache");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/custpack");
Those mountpoints are for an MT6572 device.

If I'm Porting CM 14.1 ROM To CM 11 Base ROM, Will This Work Fine?

[SOLVED] Unable update to MarshMallow (via OTA or Manual)

I have this firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So i try trough OTA and also in manual mode copyng file UL-ASUS_Z00E-WW-13.10.7.1-user.zip, but always i have this message
and no update.
My Asus ZenFone 2 Laser is ZE500KL, with root and TWRP.
I unroot it but I can not upgrade to marshmallows for a recovery problem, because my recovery in not stock. I tried to put another stock recovery, but when I search to update, this verify if the recovery was firmware WW-12.8.5.222, while finding the version 12.8.5.118 and fails update.
How can I restore its original recovery or all system including recovery ?
Please help me
Thank

Hi, I advice you to not upgrade because Marsmallow haves many bug (proximity sensor e battery drain). If you want update try to make factory reset first

Hi, your zip is a full rom not an ota... The ota 12.8.5.222to13.10.6.16 exists you can find it on google its named "WW_ZE500KL-12.8.5.222-13.10.6.16-fota-user.zip"
I think that if you want do your full rom maj, you must wipe and format all things... But i'm not sure
Sent from my ASUS_Z00AD using XDA-Developers mobile app

Please help me i cannot update to marshmallow from my firmware 12.8.5.222 on OP.
I unrrot the phone and always i receive this message
Thinking that the problem was recovery and i flash with twrp another standard recovery but always same message.
So in which way i can upgrade to marshmallow, possibly without losing apps and data...please
Thank
Hispa

hispanico957 said:
Please help me i cannot update to marshmallow from my firmware 12.8.5.222 on OP.
I unrrot the phone and always i receive this message
Thinking that the problem was recovery and i flash with twrp another standard recovery but always same message.
So in which way i can upgrade to marshmallow, possibly without losing apps and data...please
Thank
Hispa
Click to expand...
Click to collapse
Apparently, your current recovery version does not match with your current firmware version. There are two possible workarounds-
1. Wipe system by executing "fastboot erase system" in fastboot mode. Then reflash latest official asus lollipop ROM. This will fix the recovery and firmware mismatch and you will then be able to flash MM via stock recovery.
2. If you are experienced with edit8ng updater-script, Extract all contents of MM ota. Open updater-script and remove all asserts and lines that say "abort". Then compress the contents again. (You can't edit without extracting coz zip is signed). Flash this modified ota zip via TWRP.
If you still can't flash it or you are unable to edit updater-script, pm me, I have downloaded the MM ROM, I will send you modified updater-script.
I can even convert this ota into .imgs so that you can flash directly via fastboot

sziraqui said:
Apparently, your current recovery version does not match with your current firmware version. There are two possible workarounds-
1. Wipe system by executing "fastboot erase system" in fastboot mode. Then reflash latest official asus lollipop ROM. This will fix the recovery and firmware mismatch and you will then be able to flash MM via stock recovery.
2. If you are experienced with edit8ng updater-script, Extract all contents of MM ota. Open updater-script and remove all asserts and lines that say "abort". Then compress the contents again. (You can't edit without extracting coz zip is signed). Flash this modified ota zip via TWRP.
If you still can't flash it or you are unable to edit updater-script, pm me, I have downloaded the MM ROM, I will send you modified updater-script.
I can even convert this ota into .imgs so that you can flash directly via fastboot
Click to expand...
Click to collapse
Very very big if you can upload updater-script and image i thank you.
In anyway in updater-script i see 4 lines with abort:
Code:
(greater_than_int(getprop("ro.build.date.utc"), 1450932645)) || [B][COLOR="Red"]abort[/COLOR][/B]("Can't install this package less than or equal WW_12.8.5.221_user(Thu Dec 24 12:50:45 CST 2015) device build time (" + getprop("ro.build.date") + ").");
ifelse( getprop("ro.product.name") == "OPEN_Phone", ui_print("OPEN SKU device"), (
getprop("ro.product.name") == "WW_Phone" || [B][COLOR="Red"][COLOR="red"][B][B][COLOR="Red"]abort[/COLOR][/B][/B][/COLOR][/COLOR][/B]("This package is for "WW_Phone" devices; this is a "" + getprop("ro.product.name") + "".");
) );
ui_print("Target: asus/WW_Phone/ASUS_Z00E_2:6.0.1/MMB29P/13.10.7.1-20160514:user/release-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "100,0,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,753664,753666") == "8af3f740e6ebbdf56700096039cefc8918322b9d" then
if range_sha1("/dev/block/bootdevice/by-name/system", "102,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,737279,753152,753664,753666,754178") == "cf88d7b8183bd71c4f9a980377c32bce5c33a559" then
ui_print("Verified the updated system image.");
else
[B][COLOR="red"]abort[/COLOR][/B]("system partition has unexpected non-zero contents after OTA update");
endif;
else
[B][COLOR="red"]abort[/COLOR][/B]("system partition has unexpected contents after OTA update");
so i change in this way...its correct ?
Code:
ifelse( getprop("ro.product.name") == "OPEN_Phone", ui_print("OPEN SKU device"), (
) );
ui_print("Target: asus/WW_Phone/ASUS_Z00E_2:6.0.1/MMB29P/13.10.7.1-20160514:user/release-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "100,0,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,753664,753666") == "8af3f740e6ebbdf56700096039cefc8918322b9d" then
if range_sha1("/dev/block/bootdevice/by-name/system", "102,32770,32961,32963,33475,65535,65536,65538,66050,98303,98304,98306,98497,98499,99011,131071,131072,131074,131586,163839,163840,163842,164033,164035,164547,196607,196608,196610,197122,229375,229376,229378,229569,229571,230083,262143,262144,262146,262658,294911,294912,294914,295105,295107,295619,327679,327680,327682,328194,360447,360448,360450,360962,393215,393216,393218,393730,425983,425984,425986,426498,458751,458752,458754,459266,491519,491520,491522,492034,524287,524288,524290,524802,557055,557056,557058,557570,589823,589824,589826,590338,622591,622592,622594,623106,655359,655360,655362,655874,688127,688128,688130,688642,720895,720896,720898,721410,736767,737279,753152,753664,753666,754178") == "cf88d7b8183bd71c4f9a980377c32bce5c33a559" then
ui_print("Verified the updated system image.");
else
endif;
else
..regarding point 1) in which way reflash latest official asus lollipop ROM ?
Thank for support
Hispanico

alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery

sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
Ok i try... i prefer second step because with first all my dta are deleted..
BUMMM
Hispa
A BIG THANK sziraqui

sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
Does this work with a Rom

I want to ask you,what twrp version do you installed in the screenshot? 3.0.0.0 or 3.0.2.0 ? My phone is like to you.. I cant upgrade to MM

sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
Many thanks for this help, it works like a charm !

Hi I have the same problem of the topic. I followed your solution. I changed the updater-script but now I have the problem with the zip file. WinRar tells me that the files I try to put into the zipare too big and it suggests me to use rar and not zip. What do I have to do?

At last I created the zip file with compressed folder windows but I cannot flash the new zip. I don't have any OS in my Laser.
I followed what you wrote.
I downloaded the firmware WW 13.10.10.44 from Asus web site
I extracted the content in a folder. I canceled updater-script and I changed it with your zip updater-script-modified
I put everything inside a zip
I tried to flash it but it doesn't work. I put a screenshot here https://ibb.co/Tkxq5hY

[Guide] How to create your own AIO TWRP flashable update ZIP file

[Guide] How to create your own AIO TWRP flashable update ZIP (AIO=All-in-One)
I didn't see this posted and hopefully there's non or I've just wasted my time in making this.
All credit goes to @inside!out from Team MT. He posted this guide in a Russian language website so this is an interpretation of what I understood to the best of my language skills.
Application of use: Making this file is just for convenience purpose more suited for [email protected] like myself.:cyclops:
Disclaimer: Use an follow this steps at your own risk. I'm not responsible for anything that might happen to your lovely phone. So you better have some skills on what you're doing and how to go around in solving problems.
Knowledge level: Medium
Requirements:
1. A working PC with Note++ and 7-Zip applications installed. These applications are free, just Google them for download links.
2. The update.zip and update_data_full_hw_xx.zip files for your specific Honor 8 model.
Here is @yalokiy 's guide on How to find beta links for update.zip and update_data_full_hw_xx.zip:
https://forum.xda-developers.com/honor-8/how-to/guide-how-to-beta-links-update-zip-t3534004
Step 1:
Create a working folder in your PC and name it whatever you want, e.g. "work place".
Step 2:
Extract the content of each zip file into two separate folders. For example "update" and "update_data".
Step 3:
Rename the UPDATE.APP file from the update.zip to UPDATE0.APP. Then move that file into the update_data folder.
Step 4:
Open the "updater_script" file that is inside the "update_data/META-INF/com/google/android/" folder and open it in a new NOTE++ window.
Once it's opened you'll see something like this:
Code:
ui_print("Verifying current userdata...");
mount("f2fs","EMMC","/dev/block/platform/hi_mci.0/by-name/userdata", "/data");
mountencrypt("/data");
ui_print("Removing unneeded files...");
delete(
" ");
ui_print("Patching userdata files...");
ui_print("Removing empty directorys...");
delete_recursive(
" ");
ui_print("Unpacking data new files...");
delete_recursive("/data/hw_init");
package_extract_dir("data", "/data");
.........................
cut
.........................
ui_print("write radio image ...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
Step 5:
Copy these two lines that are located at the end of the script:
Code:
ui_print("write radio image ...");
assert(update_huawei_pkg_from_ota_zip( "UPDATE.APP"));
and paste the copy just below it, to look like this:
Code:
ui_print("write radio image ...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
ui_print("write radio image...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
Step 6:
Modify the text to look like this and save the changes:
Code:
ui_print("Flashing update0.app...");
assert(update_huawei_pkg_from_ota_zip("UPDATE0.APP"));
ui_print("Update data full hw...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
Step 7:
Exit NOTE++ and create a zip file with the content inside the update_data folder (i.e. data, META-INF, UPDATE.APP, and UPDATE0.APP) using the 7-Zip application.
You can later rename the ZIP file to whatever you like. I named my "AIO_TWRP_update_FRD-L14C567B360.zip".
I'll be later adding a download link of my ZIP file for the FRD-L14 once it's uploaded. Done.
Note: If you want to use the content of this guide and rewrite it to your liking be my guest, just remember to give credit to the people involved in creating it.

Great! I'll test this when I've time! Very useful:good:!

Dominikrod said:
[Guide] How to create your own AIO TWRP flashable update ZIP (AIO=All-in-One)
Click to expand...
Click to collapse
Good job, mate!

[F3111][Guide][N][33.3.A.1.115] Root with Working patched DRM fix (without ta backup)

Hi all!
Happy to share a workaround for root and successful DRM fix.
If you lose your drm key, that's okay, this fix will restore all function which depends on it (picture quality, super vivid mode, etc.....). There's nothing satisfying than using your phone at its full potential with your own custom. Spot the difference!!!!
1. Unlock bootloader
2. Flash boot.img (Patched to be compatible with the drmfix)
>>> fastboot flash boot boot.img
3. Flash recovery.img
>>> fastboot flash recovery recovery.img
4. Boot to recovery by holding vol - and power; then swipe to allow modification and Format data (mandatory)
5. Flash drmfix.zip
6. Flash Magisk 14.0
7. Boot to android, you're done!!!
Type *#*#7378423#*#* then >>Service info>>Configuration or >>Service tests>>Security to check if all your keys are active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link:
# For boot.img here!!!
# For recovery.img here!!!
# For drmfix This does the trick

@pa7taloha Recovery Download link not working for me. Is normal TWRP also okay?
Edit: Nevermind, just saw its for F3311 not for F3111.

F3311? You mean Xperia XA or Xperia E5?

okhayko said:
F3311? You mean Xperia XA or Xperia E5?
Click to expand...
Click to collapse
I mean Xperia xa F3111. OP corrected, Thank you

Hi OP, still not working, all my is are "unknown"

okhayko said:
Hi OP, still not working, all my is are "unknown"
Click to expand...
Click to collapse
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?

pa7taloha said:
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
Click to expand...
Click to collapse
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]

okhayko said:
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
Click to expand...
Click to collapse
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.

pa7taloha said:
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
Click to expand...
Click to collapse
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!

okhayko said:
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
Click to expand...
Click to collapse
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.

pa7taloha said:
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
Click to expand...
Click to collapse
Thanks buddy. Here is my boot.img that i was flash
boot.img file

For F3116 [33.3.A.1.97]
okhayko said:
Thanks buddy. Here is my boot.img that i was flash
boot.img file
Click to expand...
Click to collapse
Now
1. flash this bootF3116.img file, using the command "fastboot flash boot bootF3116.img" (without quotes)
2. Go to twrp recovery and "format data" (I suppose you already have flashed twrp)
3. Flash drmfix.zip
4. Flash Magisk if you need root.
5. Reboot
Download link
bootF3116.img
The compatible drmfix.zip
If you still have any problem let me know

Hi,
i had a F3112, is the DRM fix compatible ?
thanks

bobladure said:
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
Click to expand...
Click to collapse
Hi, F3112 and F3116 has the same boot.img file so you can try to flash the boot.img, and drmfix.zip above your post and post your feedback here

Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.

cojocar.andrei said:
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
Click to expand...
Click to collapse
Sorry for late reply.
I will try to be clear as much as I can(bad english speaker).
We have tested this workaround to: xperia xa f3111(Mediatek, Nougat) and xperia x perfomance(qualcom, Nougat and 0reo) and it work fine in Nougat and Oreo too. I hope this will work too to the other xperia devices, so we can relate it.
I did not compile kernel from source, I have just extracted it with flashtool kernel.elf and unpacked/repacked it with AIK Linux/Carliv-image-kitchen. I am a Linux user.
For mediatek processor,
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init, .
Code:
on early-init
[COLOR="Red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.aee.rc
add this red line in on init
Code:
on init
export LD_PRELOAD libdirect-coredump.so
write /proc/self/coredump_filter 39
setprop ro.aee.enperf off
[COLOR="Red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
7. Open "fstab.mt6755" and copy in new text file the path to your system, it should be in the first line, we will use this later in the drmfix.zip
6. repack your kernel
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.mt6755" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip
For Qualcom processor
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init
Code:
on early-init
[COLOR="red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.environ.rc
add this red line to the last line.
Code:
export SYSTEMSERVERCLASSPATH /system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
[COLOR="red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
5. Open "fstab.qcom" and copy in new text file the path to your system, we will use this later in the drmfix.zip
6. repack your kernel, flash it
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.qcom" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/bootdevice/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip, and flash it.
Avalaible for clarification.

https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.

matan290 said:
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
Click to expand...
Click to collapse
Sorry to hear that, It is always recommended to do a full nandroid backup before flashing anything. To get rid of those Unknown error you have to reflash your firmware. What causes these error is that the drm.zip you've flashed has deleted the credmgr.db file in /data/credmgr/, this contains all your phone credential. May be you've flashed any drmfix(old drmfix in other thread) before flashing this, because this fix will not delete anything in your system. And no need to wipe cache/dalvik after flashing it.

Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.

matan290 said:
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
Click to expand...
Click to collapse
You can use flashtool and download a frimware the latest version by xperifirm which is integrated in the flashtool. Or if you want to use Pc Companion you have to relock your bootloader and unlock after it's done.