Database Users

[GUIDE]How to make flashable baseband zip i8190L example

my friend @rcoacci asked me to help him with advice how to make flashable zip with baseband for his i8190L, based on my thread for i8190N...
so here it is:
*** if you don't have no Idea what i'm writing here about, than: DON'T DO THAT AT HOME! ;P
0) i'm doing this on Windows based computer, we need at least 7-zip and Notepad++
1) first i have to thank @tys0n because we're basing this on his zip (script). so ty thanks again!
2) we need mentioned script (zip) so download "GT-I8190_modem.bin-empty-update.zip" on the end of this thread
3) extract it to "Some Folder", now there u have: META-INF folder
4) go to SamMobile and search fot your device and download desired FW, in our example i1890L and i downloaded "Brasil(TIM) I8190LUBAMK1"
5) after file downloads, extract it with 7-zip, you get .md5 file, now right click on that file and open archive with 7-zip (confirm error about file end)
6) inside archive locate modem.bin this is our baseband, and extract that to "Some Folder"
7) goto "Some Folder" where u see: "META-INF" folder and modem.bin file
8) goto "META-INF\com\google\android" and open file "updater-script" with Notepad++
here you have:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden");
show_progress(0.100000, 0);
ui_print("GT-I8190 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("zip by tys0n");
ui_print("Done");
now edit just lines with "ui_print..." to customize text that recovery shows on screen
for our example:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden");
show_progress(0.100000, 0);
ui_print("GT-I8190LUBAMK1 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("zip by tys0n");
ui_print("modem extracted by mattiawhite");
ui_print("Done, reboot 2x if needed!");
first print is information about what version is flashing... so this is minimum to change
please leave tys0ns signature, replace mine with yours etc... (technically, script made by Tys0n, zip made by 7-zip is more accurate ;P)
ok - save that
9) close all, goto "Some Folder" select "META-INF" folder and modem.bin file, right click 7-zip -> add to ***.zip
10) open zip just to check if this 2 things are inside ("META-INF" folder and modem.bin file)
that's it! you're ready to flash!
now i attach here also result of our tutorial "GT-I8190LUBAMK1_modem_upd.zip"
you can flash it to your i8190L device only! i can not confrm its working as i have only N version, but all my other baseband zips are okay so i don't expect problems... if u brake something flash stock FW from Odin as PDA and you are ready to go... don't forget to make backups all the way...
if someone do flash to L device please report if all is fine... (remember to reboot once more if it says baseband: unknown...)
regards!

mattiawhite said:
my friend @rcoacci asked me to help him with advice how to make flashable zip with baseband for his i8190L, based on my thread for i8190N...
so here it is:
*** if you don't have no Idea what i'm writing here about, than: DON'T DO THAT AT HOME! ;P
0) i'm doing this on Windows based computer, we need at least 7-zip and Notepad++
1) first i have to thank @tys0n because we're basing this on his zip (script). so ty thanks again!
2) we need mentioned script (zip) so download "GT-I8190_modem.bin-empty-update.zip" on the end of this thread
3) extract it to "Some Folder", now there u have: META-INF folder
4) go to SamMobile and search fot your device and download desired FW, in our example i1890L and i downloaded "Brasil(TIM) I8190LUBAMK1"
5) after file downloads, extract it with 7-zip, you get .md5 file, now right click on that file and open archive with 7-zip (confirm error about file end)
6) inside archive locate modem.bin this is our baseband, and extract that to "Some Folder"
7) goto "Some Folder" where u see: "META-INF" folder and modem.bin file
8) goto "META-INF\com\google\android" and open file "updater-script" with Notepad++
here you have:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden");
show_progress(0.100000, 0);
ui_print("GT-I8190 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("zip by tys0n");
ui_print("Done");
now edit just lines with "ui_print..." to customize text that recovery shows on screen
for our example:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden");
show_progress(0.100000, 0);
ui_print("GT-I8190LUBAMK1 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("zip by tys0n");
ui_print("modem extracted by mattiawhite");
ui_print("Done, reboot 2x if needed!");
first print is information about what version is flashing... so this is minimum to change
please leave tys0ns signature, replace mine with yours etc... (technically, script made by Tys0n, zip made by 7-zip is more accurate ;P)
ok - save that
9) close all, goto "Some Folder" select "META-INF" folder and modem.bin file, right click 7-zip -> add to ***.zip
10) open zip just to check if this 2 things are inside ("META-INF" folder and modem.bin file)
that's it! you're ready to flash!
now i attach here also result of our tutorial "GT-I8190LUBAMK1_modem_upd.zip"
you can flash it to your i8190L device only! i can not confrm its working as i have only N version, but all my other baseband zips are okay so i don't expect problems... if u brake something flash stock FW from Odin as PDA and you are ready to go... don't forget to make backups all the way...
if someone do flash to L device please report if all is fine... (remember to reboot once more if it says baseband: unknown...)
regards!
Click to expand...
Click to collapse
[GUIDE]How to make flashable baseband zip i8190L example
Click to expand...
Click to collapse
This topic is totally misleading.
You don´t make a flashable zip (coding), only change displayed lines in the script that are shown in the flashing screen.

JackoMJ said:
This topic is totally misleading.
You don´t make a flashable zip (coding), only change displayed lines in the script that are shown in the flashing screen.
Click to expand...
Click to collapse
yes and i never said i do code, i explicitly said i'm using tys0ns script, i just showed how to change text, everything is up there,
you thing it is wrong to put it inside "CODE" should i use "QUOTE instead"
i just wanted to show people how to add title and text nothing more, i leaved al creadits etc
please say what should i correct??
cous i only wanted to help after other asked me how i did it...
so i'm open for suggestions and sorry for misleading if so

Thanks @mattiawhite I did just that, and was waiting for an opportunity to release the zip on the forums. It worked without any problems for me. At least after the second reboot.
So for people who wants to do this:
1) BACKUP YOUR EFS FILE SYSTEM (BOTH TWRP AND CWM DO THAT);
2) Flash the zip.
3) IT MAY SHOW UNKNOW BASEBAND/IMEI ON FIRST BOOT. DON'T PANIC AND REBOOT AGAIN. It happened to me, so I know how it feels.
After the second reboot all was fine and is still fine. Phone calls, 3G, Data, etc, all working.

damn i should let u post our PM, now i wouldnt be charged for misleading...
anyhow, im glad its workin'
Sent from my GT-I8190N with CM11

Thanks a lot.
I Believe this guide will be so usefull becuase I am trying to compiling my own kernel.
would it be the same steps to make a flasheable zip for it?

yes, only thing, i think you have to modify script to flash carnel on rigth place (right pit or whats the name)
google it, or searche here for tys0ns work im prety sure i had one zip for kernel to from him... if i found il post it...
Sent from my GT-I8190N with CM11

chacox said:
Thanks a lot.
I Believe this guide will be so usefull becuase I am trying to compiling my own kernel.
would it be the same steps to make a flasheable zip for it?
Click to expand...
Click to collapse
for example look here
http://forum.xda-developers.com/showthread.php?t=2550392
u find in second post zip with kernel, where and how u flash
and u will also find link to github of that kernel...
maybe it helps...
Sent from my GT-I8190N with CM11

mattiawhite said:
for example look here
http://forum.xda-developers.com/showthread.php?t=2550392
u find in second post zip with kernel, where and how u flash
and u will also find link to github of that kernel...
maybe it helps...
Sent from my GT-I8190N with CM11
Click to expand...
Click to collapse
Actually I have the kernel compiled and testing it on my device from Maclaw's source for CM11, I only need to make a flasheable zip becuase what I did is moved and replaced boot.img and modules into the last Maclaw's built ( cm11.0_golden.maclaw.20140108.zip) and then flashed my device. But I am not sure how to make a flasheable zip only for kernel. Thanks for your help. I will keep looking for that over here
{
"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"
}

chacox said:
Actually I have the kernel compiled and testing it on my device from Maclaw's source for CM11, I only need to make a flasheable zip becuase what I did is moved and replaced boot.img and modules into the last Maclaw's built ( cm11.0_golden.maclaw.20140108.zip) and then flashed my device. But I am not sure how to make a flasheable zip only for kernel. Thanks for your help. I will keep looking for that over here
Click to expand...
Click to collapse
ok than if u follow uper link and download flashable zip you can replace boot img with yours, check script as in my guide... and u will make it
... what mods did u do in kernel??
Sent from my GT-I8190N with CM11

mattiawhite said:
ok than if u follow uper link and download flashable zip you can replace boot img with yours, check script as in my guide... and u will make it
... what mods did u do in kernel??
Sent from my GT-I8190N with CM11
Click to expand...
Click to collapse
I didn't make too much changes really.
For now, I only added ROW scheduler, enable kernel size optimization, I compiled with linaro-4.7, I used LZO as compression method and I used Bootimgutils.zip to extract ramdisk from Maclaw and repack it.

mattiawhite said:
my friend @rcoacci asked me to help him with advice how to make flashable zip with baseband for his i8190L, based on my thread for i8190N...
so here it is:
*** if you don't have no Idea what i'm writing here about, than: DON'T DO THAT AT HOME! ;P
0) i'm doing this on Windows based computer, we need at least 7-zip and Notepad++
1) first i have to thank @tys0n because we're basing this on his zip (script). so ty thanks again!
2) we need mentioned script (zip) so download "GT-I8190_modem.bin-empty-update.zip" on the end of this thread
3) extract it to "Some Folder", now there u have: META-INF folder
4) go to SamMobile and search fot your device and download desired FW, in our example i1890L and i downloaded "Brasil(TIM) I8190LUBAMK1"
5) after file downloads, extract it with 7-zip, you get .md5 file, now right click on that file and open archive with 7-zip (confirm error about file end)
6) inside archive locate modem.bin this is our baseband, and extract that to "Some Folder"
7) goto "Some Folder" where u see: "META-INF" folder and modem.bin file
8) goto "META-INF\com\google\android" and open file "updater-script" with Notepad++
here you have:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden");
show_progress(0.100000, 0);
ui_print("GT-I8190 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("zip by tys0n");
ui_print("Done");
now edit just lines with "ui_print..." to customize text that recovery shows on screen
for our example:
Code:
assert(getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden");
show_progress(0.100000, 0);
ui_print("GT-I8190LUBAMK1 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("zip by tys0n");
ui_print("modem extracted by mattiawhite");
ui_print("Done, reboot 2x if needed!");
first print is information about what version is flashing... so this is minimum to change
please leave tys0ns signature, replace mine with yours etc... (technically, script made by Tys0n, zip made by 7-zip is more accurate ;P)
ok - save that
9) close all, goto "Some Folder" select "META-INF" folder and modem.bin file, right click 7-zip -> add to ***.zip
10) open zip just to check if this 2 things are inside ("META-INF" folder and modem.bin file)
that's it! you're ready to flash!
now i attach here also result of our tutorial "GT-I8190LUBAMK1_modem_upd.zip"
you can flash it to your i8190L device only! i can not confrm its working as i have only N version, but all my other baseband zips are okay so i don't expect problems... if u brake something flash stock FW from Odin as PDA and you are ready to go... don't forget to make backups all the way...
if someone do flash to L device please report if all is fine... (remember to reboot once more if it says baseband: unknown...)
regards!
Click to expand...
Click to collapse
Sir, can you make a flashable baseband for Myphone a919i, Id like to have the baseband used in Yonip v7. If you have time and if you want to only. If not, its okay. I just dont know how even while reading.

JudasOYE said:
Sir, can you make a flashable baseband for Myphone a919i, Id like to have the baseband used in Yonip v7. If you have time and if you want to only. If not, its okay. I just dont know how even while reading.
Click to expand...
Click to collapse
Its hard to say, I don't know anything of your device, where I can find its ROM (firmware) wherefrom we can extract baseband.
Do u know how partitions are organised?
Do you have custom recovery? Twrp or cwm, to be able to flash such zip??
You are on official ROM for that device, or custom?
If you are on official why don't u just upgrade to latest version, you will also get latest baseband??
PM me for more info...

[GUIDE] Update firmware with locked/unlocked bootloader & root (14.3.A.0.761)

Note: This thread is old. Currently you can just update the firmware and then root again using Easy Root Tool
This is a guide on how to update the Z1 Compact to any firmware without losing root on locked bootloader. For unlocked bootloader, please see post #3 ( http://forum.xda-developers.com/showpost.php?p=51254652&postcount=3 )
Requirements
Latest flashtool ( http://www.flashtool.net )
Rooted Z1 Compact (check here for how to root: http://forum.xda-developers.com/showthread.php?t=2642081 )
D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf from 'Firmwares' below
z1c-44-14.X.A.X.XXX-XX.system.flashable.zip from 'Firmwares' below
SuperSU ( http://download.chainfire.eu/supersu )
Latest Z1C-lockeddualrecovery(...).flashable.zip ( http://nut.xperia-files.com/ ) (atleast v2.7.117)
Firmwares
Here you can find some prepared firmwares. Note: Do not mix files from different firmwares!
Jelly Bean (4.3)
14.2.A.1.114 Generic UK (Darkimmortal)
z1c-43-uk.system.flashable.zip | share-online mirror
D5503_14.2.A.1.114_Generic UK-nosystem.ftf
Click to expand...
Click to collapse
KitKat (4.4)
14.3.A.0.681 Generic UK (Darkimmortal)
z1c-44-uk.system.flashable.zip | mega mirror
D5503_14.3.A.0.681_Generic_UK-nosystem.ftf | mega mirror
Click to expand...
Click to collapse
14.3.A.0.757 Generic DE 1279-6978 (louis0815)
z1c-44-14.3.A.0.757-DE.system.flashable.zip
D5503_14.3.A.0.757_GenericDE-nosystem.ftf | mediafire mirror
Click to expand...
Click to collapse
14.3.A.0.757 Generic NO 1279-4149 (nism0o)
z1c-44-14.3.A.0.757-NO.system.flashable.zip
D5503_14.3.A.0.757_GenericNO-nosystem.ftf
Click to expand...
Click to collapse
14.3.A.0.757 Generic UK 1279-4727 (codified)
z1c-44-14.3.A.0.757-UK.system.flashable.zip | gdrive mirror
D5503_14.3.A.0.757_Generic_UK-nosystem.ftf
Click to expand...
Click to collapse
14.3.A.0.757 Generic FR 1279-5365 (emilic)
See here: http://forum.xda-developers.com/showpost.php?p=52599589&postcount=385
Click to expand...
Click to collapse
14.3.A.0.761 Generic NO 1279-4149 (paul5425)
z1c-44-14.3.A.0.761-NO.system.flashable.zip
D5503_14.3.A.0.761_GenericNO-nosystem.ftf
Click to expand...
Click to collapse
Tutorial
You will not lose any data. It is still recommend to take a backup.
Copy D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf to your flashtool installation in the folder firmwares/
Put z1c-44-14.X.A.X.XXX-XX.system.flashable.zip on your sdcard (do not unpack)
Put Z1C-lockeddualrecovery(...).flashable.zip on your sdcard (do not unpack)
Download SuperSU and put on your SD card (do not unpack)
Go to the recovery menu and try flashing SuperSU. If it succeeds, proceed. Otherwise change recovery menu (TWRP is Volume DOWN)
In the recovery menu format /system (located under Mounts & Storage) (do not reboot!)
Install the following files in recovery (in this order)
z1c-44-14.X.A.X.XXX-XX.system.flashable.zip
Z1C-lockeddualrecovery(...).flashable.zip
SuperSU zip file
After installing go to Advanced => Power off (Power off might also be located under Power Options, depending on the recovery you use)
Boot your phone in flashmode (Hold volume down while phone is off and plug in your USB cable)
Open flashtool and flash D5503_14.X.A.X.XXX_Generic_XX-nosystem.ftf (select Wipe [Uncheck Data] and Exclude [Uncheck ALL])
You're done!
Hashes
D5503_14.2.A.1.114_Generic UK-nosystem.ftf
MD5: 47005E1E16B340A90B958919122F89AA
SHA1: 252C905F1F0213D809925BC32A955E421FE4C3E6
z1c-43-uk.system.flashable.zip
MD5: 6221178B6809EA943A0AB5654A9D6A2D
SHA1: 8B9BEAB4846927DED38018B93C56993BD017BFB8
D5503_14.3.A.0.681_Generic_UK-nosystem.ftf
MD5: 5D1BDD44DF531280984B60E810A87FFA
SHA1: 5ADE48599414BE47A0A7DD1BCB37C0F5518F7CCB
z1c-44-uk.system.flashable.zip
MD5: 148BDD3BEAEDE850CAF085ED82518FF9
SHA1: FB594821FBEA030657CA5D048DE2593194F18DF8
D5503_14.3.A.0.757_GenericDE-nosystem.ftf
MD5: D720CD278E0DB88F49FA22CBBE441720
SHA1: 3F4C47B841BD24511C30BB0E44030872BD93921A
z1c-44-14.3.A.0.757-DE.system.flashable.zip
MD5: 38FA3162C725B0E357FD8CDE1AA8CDE8
SHA1: F898DC9580D84D541C622307439B45A607A0A7A5
D5503_14.3.A.0.757_GenericNO-nosystem.ftf
MD5: 3E76A9E4DFE4BD6D2CE05DBBC0B09CB8
SHA1: 44EFFED69E881B08FF6F3AEEF0EDBE69C59187DC
z1c-44-14.3.A.0.757-NO.system.flashable.zip
MD5: A6B54DF73E5E0038152EC2AFFE4E7067
SHA1: DF6F497987D44F43ABF49C4BB98ECC49058F97C6
D5503_14.3.A.0.757_Generic_UK-nosystem.ftf
MD5: 915E348841834816216F4EFE6BB85D29
SHA1: 28EBCA4A3218E45C1C7B00C6DE494052A004DA0B
z1c-44-14.3.A.0.757-UK.system.flashable.zip
MD5: 9A8089751D964312E255ABC507AD1C90
SHA1: 2FC34DB65EA087C0D824502FE1E801027461EC49
D5503_14.3.A.0.761_GenericNO-nosystem.ftf
MD5: 3DD5723B43F834ED55E65A9B8DCCB0D2
SHA1: 84848D4C1ABBD4C2729E3BBCE0706A25379717F8
z1c-44-14.3.A.0.761-NO.system.flashable.zip
MD5: 771B257718FCE8CBE8E3EAE6F29B0765
SHA1: C737EEE5D1DB28F8F918A126A18EDCA7FAF8E5AF
Questions
I get an error in flashtool: "Cannot open bundle. Flash operation canceled"
You need the latest flashtool.
Click to expand...
Click to collapse
I am from Country XY but there is no firmware for my country? :crying:
It doesn't really matter what localization you use. The firmwares are almost the same. Your language will still be available.
Click to expand...
Click to collapse
Are these roms deodexed?
No. All roms are odexed.
Click to expand...
Click to collapse
I can't access recovery menu, when I boot my phone the light is orange, not green?
Somehow you lost your recovery menu. If your bootloader is locked you need to start again from the beginning of the rooting guide.
Click to expand...
Click to collapse
I have another error, which is not in this list!
Post it in the thread but note for successful help you need to provide the following:
dualrecovery version used
flashable system zip used
ftf no-system used
Click to expand...
Click to collapse
Proof
Confirmed working by pcpepik, Boes40 ( http://forum.xda-developers.com/showpost.php?p=51476157&postcount=156 ), tommy17 ( http://forum.xda-developers.com/showpost.php?p=51384084&postcount=125 ), mikk_11 ( http://forum.xda-developers.com/showpost.php?p=51341824&postcount=105 ) and many more on locked bootloader :highfive:
{
"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"
}
Credits
Darkimmortal
[NUT]
pcpepik

Hello,
Seems missing the download path of "Z1C-lockeddualrecovery(...)flashable.zip" and is it also copy to SD card?

Unlocked bootloader
Requirements
Latest flashtool ( http://www.flashtool.net )
fastboot and flashmode drivers installed
Z1 Compact with unlocked bootloader
ftf of firmware (check here http://forum.xda-developers.com/showthread.php?t=2631291 or general section for official firmwares)
SuperSU ( http://download.chainfire.eu/supersu )
Custom kernel with recovery (e.g. dualrecovery kernel or http://forum.xda-developers.com/showthread.php?t=2620794 )
Note: Kernel needs to be for the specific firmware version (dualrecovery kernel is only for latest firmware)
Tutorial
You will not lose any data. It is still recommend to take a backup.
Copy the firmware ftf to your flashtool installation in the folder firmwares/
Download SuperSU and put on your SD card (do not unpack)
Boot your phone in flashmode (Hold volume down while phone is off and plug in your USB cable)
Open flashtool and flash your ftf (select Wipe [Uncheck Data] and Exclude [Uncheck ALL])
After flashing, boot your phone in fastboot mode (Hold volume up while phone is off and plug in your USB cable)
Download a custom kernel and unzip until you have a file called *.img
Put the custom kernel inside the folder of flashtool called x10flasher_lib/
Open cmd and navigate to this folder (e.g. cd C:\flashtool\x10flasher_lib)
Execute the following command to flash the custom kernel (boot.img is the filename of the kernel, change if needed)
fastboot.exe flash boot boot.img
Boot your phone and go to the recovery menu
Note: This is different in some kernels, default is to hold volume up when the led lights up
Optional: If you are using dualrecovery kernel, flash the kernel flashable zip
Flash SuperSU zip
You're done!

Confused about point 5 : Install Z1C-lockeddualrecovery(...)flashable.zip
and warning post 1 : Do not try to flash the dualrecovery, you will end up stuck at boot logo!
So what to install on point 5?

Boes40 said:
Confused about point 5 : Install Z1C-lockeddualrecovery(...)flashable.zip
and warning post 1 : Do not try to flash the dualrecovery, you will end up stuck at boot logo!
So what to install on point 5?
Click to expand...
Click to collapse
Whoops, forgot to delete that step. Fixed now, thanks

what to do with error in flashmode :Cannot open bundle. Flash operation canceled
and point 5 should be power options, not advance

Boes40 said:
what to do with error in flashmode :Cannot open bundle. Flash operation canceled
and point 5 should be power options, not advance
Click to expand...
Click to collapse
You need latest flashtool. Ok thanks, for the tip, which recovery are you using? It's advanced in CWM.

Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).

Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Same!
I have rooted Z1c with Android 4.4!
Hurry!
But supersu can't update. Some app can't rooted (eg. Greenify), Es explorer can't mount system r/w...

Titanium is still working though, Latest Xposed (beta) isn't, no root.

Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Root should still work. But to fix the problem, try this.
Download SuperSU from here: ( http://download.chainfire.eu/supersu )
Copy the file su from the folder arm to somewhere on your phone. (e.g. /tmp)
Give correct permissions (755)
Then copy it to /system/xbin and overwrite the old one.
Please let me know if it worked.

Boes40 said:
Downloading the latest flashtool now...Don't know which recovery, can't check at the moment cause i'm in bootloop but it's from this thread http://forum.xda-developers.com/showthread.php?t=2634196
Edit: Flashed with latest flashtool and suceeded, KitKat installed.
Edit 2 : When opening SuperSU, it needs to update binaries, I have to choose normal cause there's no recovery. Says installing but nothing happens (rebooted elready and tried again).
Click to expand...
Click to collapse
Could we update SuperSu from Play?
Or how can we solved: We have root, but we have an not working supersu...

Problem is I can't copy the file with rootexplorer. First time RE opens it asks for root, press yes of course but it looks it doesn't get root.

Boes40 said:
Problem is I can't copy the file with rootexplorer. First time RE opens it asks for root, press yes of course but it looks it doesn't get root.
Click to expand...
Click to collapse
What is the error message? And have you tried with adb?
And can you check if your system flashable zip has the same hash as in the first post?

With Root Explorer, first mesage is :The current file sytem is r only. Do you want to remount as r-write and continue the operation, / yes / su already exists. Do you want to overwrite it? / yes / Copy failed su to /system/xbin
Haven't tried with adb, how please?
How to check the hash?
thanks

zxz0O0 said:
What is the error message? And have you tried with adb?
And can you check if your system flashable zip has the same hash as in the first post?
Click to expand...
Click to collapse
After run esexplorer and granted supersu: 1. screenshot
After run supersu: 2.
After update normal (we don't have CWM...): 3.
Root checker: 4.
Supersu: 5.
All working except supersu...

Boes40 said:
With Root Explorer, first mesage is :The current file sytem is r only. Do you want to remount as r-write and continue the operation, / yes / su already exists. Do you want to overwrite it? / yes / Copy failed su to /system/xbin
Haven't tried with adb, how please?
How to check the hash?
thanks
Click to expand...
Click to collapse
Copy the new su binary to /tmp then do
adb shell
su
chown root:root /tmp/su
chmod 755 /tmp/su
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
cp /system/xbin/su /system/xbin/su.old
mv /tmp/su /system/xbin/su
papzi57 said:
After run esexplorer and granted supersu: 1. screenshot
After run supersu: 2.
After update normal (we don't have CWM...): 3.
Root checker: 4.
Supersu: 5.
All working except supersu...
Click to expand...
Click to collapse
Have you tried to replace su binary as I posted above and post #11 ?

Just followed ur instructions!
After successful flashing I can still enter Recovery.
Xposed Installer NOT working, requires writing permissions!

mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
error:
block/platform/msn_sdcc.1/by-name/system /system
mount : Operation not permitted
255|[email protected]:/ #

for adb wich mode need: fastboot or flashmode or normal. (I forgotten...)
Su binary can't replace: permission denied

[Unofficial] Offline packages for twrp

Since huawei started to mess around with online firmwares that twrp couldn't handle I decided to create my own offline package with updated firmware(s) and i thought why not create a offline package thread with latest firmwares in it.
This case we can always keep ourself up to date (system wise) without having to restore to stock recovery etc.
However this is a "dirty" way of update firmware and it will only update following partitions:
Boot
Cust
Product
System
Vendor
Version
All other partitions will stay intact! Why? Because if we add other partitions there's a HIGH potential of hard brick the device and I mean really high!
But with official packages it updates all partitions!
Yes. And we can't (for now, or never) re create this procedure we'd have to know how the UPDATE.APP is being built and we can't re create a UPDATE.APP for now.
So far only available homebrewed package is 394 created by me.
See post 2 on how to create your own custom offline package!
Downloads:
FRD-L09C432B934
https://mega.nz/#!j0QXjJKa!i5lOMYjO_GusfzCTT6qVAR7LgzVGdpLT4i66FKCrshQ
blackbuffalo said:
Here is Offline fw for L04C567B385 thanks @blackbuffalo
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Click to expand...
Click to collapse
Thanks @SnoopHTC
L19-C432B398
https://gofile.me/3wKsh/4wlivV41v
Nortonko said:
so coz the link from SnoopHTC is dead i made my own package for FRD-L19C432B398. Here is the link: https://webshare.cz/file/73v2t363K5/twrp-frd-l19c432b398-zip
Click to expand...
Click to collapse

How to do it yourself package.
In order to create a unofficial update package you'll need
Huaweiupdateextractor (google it)
Simg2img (google it)
This template
https://mega.nz/#!i1Y3Wa5J!VfELb8aRkA5bon_OlIRPNAS_xUAmzMq0I-rVywHbvi4
Now extract all needed partitions
Boot
System
Vendor
Product
from big update file
cust
version
from small update file *this can be found in any of the 2 extra small zips
Open cmd and navigate to the folder where you have to both simg2img and your system files. Now cd into your work directory to convert the images.
Simg2img.exe system.img s.img will give you a converted system image with the name s.img
Convert these following partitions
system
Product
Version
Cust
Vendor
Once completed check the update-script
The
c.img is cust
v.img is vendor
ve.img is version
p.img is product.
b.img is boot
s.img is system
you can change these names to its regular name like system.img for system or make it more confusing if you want [emoji14]
Make sure the partitions are exactly the same!
If you decide you want to change the name of the files from s.img to system.img make sure you do it correct!
Because system.img in updater-script is not the same as System.img in root of zip. If you have a captive letter in root and not in updater-script the zip will fail to flash.
Now simply compress the images into a zip and you're done.
Note: after you flashed your offline zip make sure to patch boot! Else it will reboot to recovery
Note you'll get result
Error: Unknown command []] this is not a issue since we're using stock huawei updater binary.
Sent from my FRD-L09 using Tapatalk

Your awesome work will save a lot :good:

Nice but it should not be in "roms etc" threads? More people will find it.

I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored

WYPIERDAALAAC said:
Nice but it should not be in "roms etc" threads? More people will find it.
Click to expand...
Click to collapse
Because I simply put it here
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
Hmm you might have to patch boot after flash??
PalakMi said:
Your awesome work will save a lot :good:
Click to expand...
Click to collapse
It will save a lot of time yes.
Sent from my FRD-L09 using Tapatalk

extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
{
"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"
}
Gesendet von meinem FRD-L09 mit Tapatalk

LastStandingDroid said:
Hmm you might have to patch boot after flash??
Click to expand...
Click to collapse
What schould i do?

Rommco05 said:
I can't find simg2img version which works on Windows 10. One version shows me only
Using STDIN as input
Using STDOUT as output is that right?
Maybe don't know how use this program
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/dev-simg2img-windows-t3156459
This one works just great.
I forgot you might have to use a cmd to convert images will edit post 2
Silencer3007 said:
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
View attachment 4250767
Gesendet von meinem FRD-L09 mit Tapatalk
Click to expand...
Click to collapse
Patch boot with either Supersu or magisk.
Did the backup include version? I doubt which is why you'll get B394 in settings.
It doesn't restore the partition which contains the build number info.
extpumajl said:
What schould i do?
Click to expand...
Click to collapse
Patch boot and try again
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
Patch boot and try again
Click to expand...
Click to collapse
Thx. Now is everything fine.

Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.

Dominikrod said:
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Click to expand...
Click to collapse
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:

Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
Ah no its just that it has to flash boot as well ?
Sent from my FRD-L09 using Tapatalk

Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
No need convert Boot.img, just rename then put it into zip

blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Great that you contribute ?
Sent from my FRD-L09 using Tapatalk

blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Bro can you confirm the build number is not NRDm keys ?

venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
It won't unless he packed the product files which stores the build info
Sent from my FRD-L09 using Tapatalk

venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
it not imcluded

blackbuffalo said:
it not imcluded
Click to expand...
Click to collapse
Ok,then it shows build number correctly?

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

Which Custom Rom will work on J5

Ive made a terrible mistake of not installing DevInfo before wiping my UK unlocked Samsung J5 and now i dont know what model number it was or what cpu i had arm32/64 or x86 I have tryed 3 different Linageos 17 and i keep getting this error on all of them.
I cant get my J5 to work through USB PC (Adb) so have to use another samsung phone which has a SD card so that i can put the rom on that and then transfer that sd card to the j5, also i never backed up my OS so theres nothing on there apart from TWRP
Theres no way in TWRP to get any info on the make or model, is there a safe universal rom to install via TWRP so that i can just check my model number cpu hardware etc, so i can then install the right lineageos 17 afterwards
{
"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"
}

68EC000 said:
Ive made a terrible mistake of not installing DevInfo before wiping my UK unlocked Samsung J5 and now i dont know what model number it was or what cpu i had arm32/64 or x86 I have tryed 3 different Linageos 17 and i keep getting this error on all of them.
I cant get my J5 to work through USB PC (Adb) so have to use another samsung phone which has a SD card so that i can put the rom on that and then transfer that sd card to the j5, also i never backed up my OS so theres nothing on there apart from TWRP
Theres no way in TWRP to get any info on the make or model, is there a safe universal rom to install via TWRP so that i can just check my model number cpu hardware etc, so i can then install the right lineageos 17 afterwards
View attachment 5405063
Click to expand...
Click to collapse
Some sensitive info was overlapped, for this reason this ROM is not recognizing your device as a candidate. If you are totally sure that this ROM work for your device, just delete from the zip path /META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device... and try again.
Regard to know the exact model you could flash a stock recovery (converting it in tar) from any of the LTE models; G/F/FM and booting to it, you will see the build number and the exact model it is.

Many thanks for your help.... Ive managed to find out that its a J5 SM-J530F 2017 (16gb) and with the IMEI number it has a ARM Cortex A53, Samsung Exynos 7870.
I loaded up a stock rom J530FXWS7CTF1 in Odin3_v3.10.5 everything went ok but when its starts up it goes into a loop on restart
Loaded up the Rom and everything went ok
Everything looked good
looks like its failed....

68EC000 said:
Many thanks for your help.... Ive managed to find out that its a J5 SM-J530F 2017 (16gb) and with the IMEI number it has a ARM Cortex A53, Samsung Exynos 7870.
I loaded up a stock rom J530FXWS7CTF1 in Odin3_v3.10.5 everything went ok but when its starts up it goes into a loop on restart
View attachment 5405703
Loaded up the Rom and everything went ok
View attachment 5405705
Everything looked good
View attachment 5405709
View attachment 5405711
looks like its failed....
Click to expand...
Click to collapse
From what I understood, you flashed the official stock firmware through Odin, but then you did try to root it.
If this is the case after to flash the Samsung firmware you should to reboot to system and redo all the process to can flash something custom on it, I mean USB debugging, OEM unlock and this stuff, only starting from there you should go further with.
And one more thing, when you return completely to stock is always recommendable:
- Wiping all and formatting data through stock recovery
- Then go to bootloader (Odin mode)
- When flashing use the CSC_... different from the CSC_HOME this will wipe completely the preferences, and you can start freshly from there.
Why you don't use Magisk instead of SuperSu.

again thank you for your time, i feel a bit embarrassed as im digging my self into a deeper situation and dont know what to do.
Since i dont have a OS installed am either stuck with download mode or twrp and even using magisk i cant get anything to work it seems that the custom lineageOS keeps saying its the wrong version for any of them.
.
.
magisk
anything else i could try if its salvageable, thanks again.

68EC000 said:
again thank you for your time, i feel a bit embarrassed as im digging my self into a deeper situation and dont know what to do.
Since i dont have a OS installed am either stuck with download mode or twrp and even using magisk i cant get anything to work it seems that the custom lineageOS keeps saying its the wrong version for any of them.
View attachment 5408207
.
View attachment 5408209
.
magisk
View attachment 5408211
anything else i could try if its salvageable, thanks again.
Click to expand...
Click to collapse
Some insights about:
- Don't try to flash 3 files at once, flash one by one.
- did you do the right editing from the updater-script as indicated? Can you upload here just this file?
- Did you change the system partition through TWRP I mean did you do "repair file" ?
- It seems that TWRP is not finding the route to misc partition, have your ROM this file? Unpack the stock ROM and search for it in case you didn't do a backup from.
- And as a final resource the PIT repartitioning could work too but, we have to see other reasons why your device got this.

hi thanks again for your patient i cant seem to find the line
META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device...
this is from the rom lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb)

68EC000 said:
hi thanks again for your patient i cant seem to find the line
META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device...
View attachment 5409557
this is from the rom lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb)
Click to expand...
Click to collapse
You have to delete all the lines above, edit it with Notepad++, and let it from "ui_print........" then save it, you don´t need to unpack the zip, just open it, edit it and save, WinRar or 7zip will update the zip with the changes.

I used 7zip to edit the \META-INF\com\google\android\updater-script and saving editied file without unzipping.
then i put the edited lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb) file back onto microSDcard and tried again.

68EC000 said:
I used 7zip to edit the \META-INF\com\google\android\updater-script and saving editied file without unzipping.
View attachment 5410597
then i put the edited lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb) file back onto microSDcard and tried again.
View attachment 5410601
Click to expand...
Click to collapse
You shortened too much the file, from your original updater-script uploaded some days ago you didn't leave the most important scripts.
I don't recommend using a simple Notepad to edit it, you should use Notepad++ or other tool like Sublime.
Can you upload the original-updater script? I will check it, and will upload it again, this way we can discard if this is the culprit or something is wrong with your file system.

yes i deleted too much from the script file... i installed Notepad++ and re-done the script.
redited script saved
starts off good.
i dont know if it failed or if something did work as it asks if you want install twrp again

68EC000 said:
yes i deleted too much from the script file... i installed Notepad++ and re-done the script.
View attachment 5411271
redited script saved
View attachment 5411273
View attachment 5411275
starts off good.
View attachment 5411277
View attachment 5411279
i dont know if it failed or if something did work as it asks if you want install twrp again
Click to expand...
Click to collapse
The ROM you are trying to flash is this? https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/ if not, provide a link.

@68EC000 you should use the latest orange fox recovery for your device, This error was also faced by mt j5, I flashed orange fox recovery and I didn't get any error, With the old version of TWRP I was unable to flash android 10 lineage os on it​

I was also getting this same error 7 with old twrp

[OFFICIAL][TWRP][J530X] OrangeFox Recovery Project [R11.0]
DISCLAIMER I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
flash this recovery and then try to flash lineage os

Hi
Thanks again for your input and help.....so i tryed the Rom from https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/
edited the updater script
Spoiler: Screen shots
error 7 again...
So i tryed hasangillani66 method installing OrangeFox and adb then copying recovery.img to the adb directory but im getting some error when typing device, also everytime a connect the j5 to the pc via usb i hear the usb connection sound but cant see anything in my computer.
Spoiler: Screen shots

68EC000 said:
Hi
Thanks again for your input and help.....so i tryed the Rom from https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/
edited the updater script
View attachment 5412179
View attachment 5412181
error 7 again...
So i tryed hasangillani66 method installing OrangeFox and adb then copying recovery.img to the adb directory but im getting some error when typing device, also everytime a connect the j5 to the pc via usb i hear the usb connection sound but cant see anything in my computer.
View attachment 5412187
View attachment 5412189
View attachment 5412197
View attachment 5412203
Click to expand...
Click to collapse
TBH, I don't understand what you are trying to do with ADB,
Odin works while the device is in download mode, you should power off the device and then either reboot via recovery to bootloader mode or directly by pressing the key combo to download mode.
Extract the image from Orange Fox recovery (usually it comes into a zip with add-ons), compress the recovery image into a tar using 7zip, uncheck in Odin "Auto reboot" option and after to flash it, reboot manually to the new recovery, transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
That's all regards Orange Fox recovery.

Thank you again for your helping a low tech savvy person like myself, well i managed to get somewhere this time as the photos will explan
turned zip to tar
flash passed
starts up with orangefox
now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
thanks again for being so patient.

68EC000 said:
Now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
Click to expand...
Click to collapse
Download Ofox zip from their website. Your device can be found here Orange Fox J5 2017
The XDA thread for orange fox for your device can be found here

68EC000 said:
Thank you again for your helping a low tech savvy person like myself, well i managed to get somewhere this time as the photos will explan
View attachment 5412943
turned zip to tar
View attachment 5412947
flash passed
View attachment 5412949
starts up with orangefox
now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
View attachment 5412963
thanks again for being so patient.
Click to expand...
Click to collapse
Oh Man, I hope you didn't brick your device, the recovery image must be targeted to the AP slot, not to the BL.
If you encountered some issue with a normal boot flash back again the BL file supposed to be in the stock Samsung firmware, extract it from there and compress it as tar with 7zip.
The Orange Fox zip is the same from which you extract it the recovery image, as you could see it contains other files that can't be flashed through fastboot method (for other devices) or download mode (for Samsung) and the zip have to be flashed through Orange Fox to permanently have those files in your SD card in the Fox path directory. Again, is the same zip where you did get the recovery image from.