Database Info

[Q] GT-P5113 modify stock firmware and flash question

I have spent several weeks working on this (reading thread after thread) on modifying stock firmware and im running into a problem. I more or less want to know if what i want to do is actually possible. I have downloaded the original .tar.md5 firmware image, opened with 7zip and "extracted" the .tar file (more or less just removed the hash) and then extracted the .img files from the .tar file. I have unpacked/mounted/modified/repacked using several methods (dsixda kitchen -which havent been able to work around adding the java path since after i add the path cygwin thinks im missing clean app until i remove the path in which case i get an error saying it cant find java/ i have tried mounting using ext4_utils in ubuntu) my issue arises when i take my modified and repacked system.img file i cant get it to work either by 1. zipping it in a .tar with the other .img files and flashing with odin, 2. zipping system.img alone into a .tar and flashing with odin, 3. installing cwm/root and flashing the system.img)
More or less my question is
1. is it possible to modify the stock firmware and load it onto the tablet without rooting
2. can system.img be flashed by itself or does it need the other .img files in the same .tar
3. does the tar file require being signed before flashing even with CWM recovery and root already on the tablet?
I have used these forums for a while to find answers, but i am new to posting, i havent needed to post a question until now since i spend as much time researching as i can before bothering people with a question (i like to figure stuff out and hate to admit defeat) Thanks in advance for the help despite my noobishness

[Q] How to extract build.prop from system.img

I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.

gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
Try the tools in this thread . I used them last week to extract a build prop.
Just load up the system.IMG and drag the file from the system folder to your desktop.

gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ

daniel4653 said:
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
Click to expand...
Click to collapse
I already downloaded that file.... I just need to extract the build.prop from the system.img which I already have. The thing is I am having trouble getting the build.prop
Sent from my SAMSUNG-SM-G920AZ

gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps

tiboric said:
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
Click to expand...
Click to collapse
When I try to open the file the program just closes and i go to the log and this is what it says.
Error Opening \\.\PhysicalDrive1. Error Code 2
No of disks 1
Scanning \\.\PhysicalDrive0
index 0 ID 7 size 976769024
Partition Table Error on C:/Users/giovany/Desktop/New folder (2)/system.img
Invalid End of sector markerBad Super Block. The drive is not ext2 formatted.

Drive is not right formatted.

solution for img extraction/fix here

LG Aristo 3 X220MA Root Search

So I just got the Aristo 3 and wanted to root it. after an extensive search I have come up empty. Does anyone know if there is a method available to use yet or maybe something is in the works? I've unlocked flashing but I cant seem to boot recovery. Any help would be greatly appreciated.

Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image

Nvitethedark said:
Same ive spent about 6 hours researching this ive never built my own root before however i just dont have the time to do whats needed. From what i researched get the original boot rom from lg bridge and perform a restore to download the factory boot image then use magisk to rebuild the image
Click to expand...
Click to collapse
Hmm I'll give it a try. The phone is still new enough that I don't have much saved to it and if I brick it can take it back

should be able to just get the boot image may be the aristo 2 dev would pick this up since he's familiar with it I see you have a few posts in that forum maybe you can send that dev a message see if they would pick it up.

I eagerly await any progress in this run! My girlfriend cracked her screen on her Aristo 2 and decided that it was time to upgrade. I've never been disappointed in the idea of upgrading my phone...until it meant giving up my Aristoboy Mk.2(which was/is quite formidable)and rooted status along with it. If there is anything I might read about the process online, I would at very least consider the task myself. I am learning, but I have some decent skills and experience behind me. Please let me know if I can assist in any way. If not, I hope to see the first strides towards tackling this latest addition to the Aristo line!
My thanks to all my fellow devs here! You each make up a piece of the whole collection that make this, hands down the best forum/online community available the world over! Keep it up! We are making a difference in so many lives!
Your friend,
~[ProTech]~

So I've been busy as **** lately, but I found that the issue seems to be with the os more than the phone itself. I'm not that proficient with downgrading the os to a earlier version since this phone came stock with Oreo. I will try and talk to some of the devs who did the aristo 2 x210ma. Hopefully they have a solution. I've been using my 2 instead. I never realized how much you can't do with a stock phone and os.

OK here's something you can try...
first get dev-patched LGup {GooGle It}
then use the Dump function of Lgup to dump All partitions from your fone...
look for boot_COM{some#here} and rename it to boot.img
put that file on your fones sdcard and install magisk manager app.
use magisk manager app to patch that boot.img file.
find the new file patched_boot.img whereever magisk put it on your sdcard...
move it to your desktop or a folder etc. on P.C
now try to flash it to your fone...
Code:
adb reboot bootloader
Code:
fastboot oem unlock
if that works your bootloader is now unlocked you'll have to reboot the fone once as it'll erase cache and data...
after that
again do
Code:
adb reboot bootloader
now try
Code:
fastboot flash boot patched_boot.img
if that works....
Code:
fastboot reboot
and you'll have root by magisk.
if fastboot's not working other option is to rename "patched_boot.img" to "boot.img"
and then use Partitions DL option in lgup to flash the "patched"boot.img to the phone...
if that works you'll have root by magisk...
If this helped you feel free to hit thanks and come back to post the results plz.
Thanks

LgPWN'd said:
OK here's something you can try...
first get dev-patched LGup {GooGle It}
then use the Dump function of Lgup to dump All partitions from your fone...
look for boot_COM{some#here} and rename it to boot.img
put that file on your fones sdcard and install magisk manager app.
use magisk manager app to patch that boot.img file.
find the new file patched_boot.img whereever magisk put it on your sdcard...
move it to your desktop or a folder etc. on P.C
now try to flash it to your fone...
Code:
adb reboot bootloader
Code:
fastboot oem unlock
if that works your bootloader is now unlocked you'll have to reboot the fone once as it'll erase cache and data...
after that
again do
Code:
adb reboot bootloader
now try
Code:
fastboot flash boot patched_boot.img
if that works....
Code:
fastboot reboot
and you'll have root by magisk.
if fastboot's not working other option is to rename "patched_boot.img" to "boot.img"
and then use Partitions DL option in lgup to flash the "patched"boot.img to the phone...
if that works you'll have root by magisk...
If this helped you feel free to hit thanks and come back to post the results plz.
Thanks
Click to expand...
Click to collapse
My bootloader is already unlocked I've just not been able to flash anything with fastboot. So I have LGup, is there a difference with the dev patched one? I also have magisk on my phone, but it really doesn't give me any options besides to install a new version. I'm gonna go try your suggestion soon though...it sounds promising...and may open up other options if this doesn't succeed. Thanks I'll keep you posted.

Reckless459 said:
My bootloader is already unlocked I've just not been able to flash anything with fastboot. So I have LGup, is there a difference with the dev patched one? I also have magisk on my phone, but it really doesn't give me any options besides to install a new version. I'm gonna go try your suggestion soon though...it sounds promising...and may open up other options if this doesn't succeed. Thanks I'll keep you posted.
Click to expand...
Click to collapse
PLease let us know how it go's...
I'm trying to port and compile Multi-rom for LG-aristo Lg-m210 at the moment...
So I have LGup, is there a difference with the dev patched one?
.
Click to expand...
Click to collapse
in answer to that YES quite a difference...
devpatched lgup gives you extra options such as Dump and Partitions-DL and Chiperase among others...
you'll NEED that dump and partitions-DL option....

LgPWN'd said:
PLease let us know how it go's...
I'm trying to port and compile Multi-rom for LG-aristo Lg-m210 at the moment...ll
Click to expand...
Click to collapse
So I can't get passed the dump. I keep getting a timed out error. I even tried to format the user data using fastboot and it failed. And I am curious about the boot_COM. I didn't see any file in the partition list matching that. I did see the boot partition and many others that I didn't recognize. So kinda feeling that we are back to

Reckless459 said:
So I can't get passed the dump. I keep getting a timed out error. I even tried to format the user data using fastboot and it failed. And I am curious about the boot_COM. I didn't see any file in the partition list matching that. I did see the boot partition and many others that I didn't recognize. So kinda feeling that we are back to
Click to expand...
Click to collapse
No the file wont say that in lgup, it'll be named that after you create a new folder on desktop call it "Dump" then use the dev-patched lgup and Dump option, select the folder Dump on the desktop and select the little checkbox for all on partitions list and click start...
also you may be haveing issues because of the .dll your useing... will lgup flash a stock .kdz to the device?
if yes, I'd think the dump option would work fine...
for firmware look here : https://www.mylgphones.com/metropcs-lg-aristo-3-lmx220ma-x220ma-firmware.html
for direct download use this link
Code:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW88KEQ4C2VSAF0C3D54FH4/X220MA10e_00_MPCS_US_OP_0123.kdz

LgPWN'd said:
No the file wont say that in lgup, it'll be named that after you create a new folder on desktop call it "Dump" then use the dev-patched lgup and Dump option, select the folder Dump on the desktop and select the little checkbox for all on partitions list and click start...
also you may be haveing issues because of the .dll your useing... will lgup flash a stock .kdz to the device?
if yes, I'd think the dump option would work fine...
for firmware look here : https://www.mylgphones.com/metropcs-lg-aristo-3-lmx220ma-x220ma-firmware.html
for direct download use this link
Code:
http://pkg02.lime.gdms.lge.com/dn/downloader.dev?fileKey=FW88KEQ4C2VSAF0C3D54FH4/X220MA10e_00_MPCS_US_OP_0123.kdz
Click to expand...
Click to collapse
So yes it would load a stock formware but no it wouldn't allow me to dump even one partion. And the strange thing was that my list of options would chanhe sometimes. Like it would give me more options i.e. phonesettings. I even tried different cables and ports. It doesnt matter though i somehow hard bricked it so bad that it won't even. Boot to download mode and somehow fried my sim card to the point it wont work in any other phone. Im just waiting for metro to open so i can try again

Reckless459 said:
So yes it would load a stock formware but no it wouldn't allow me to dump even one partion. And the strange thing was that my list of options would chanhe sometimes. Like it would give me more options i.e. phonesettings. I even tried different cables and ports. It doesnt matter though i somehow hard bricked it so bad that it won't even. Boot to download mode and somehow fried my sim card to the point it wont work in any other phone. Im just waiting for metro to open so i can try again
Click to expand...
Click to collapse
OH WOW what a mess...
I would say it's the .dll in the LGUP causing pain here...
something you can try when you're ready to try again....
remove/uninstall devpatched LGUP and install regular store version
use the Common .dll
and add this file{ UI_Config.lgl } to your Common folder in the lgup install location ...
to make it easier I'll just zip up My common folder for you to replace yours
to do this
right click on lgup, select open file location...
navigate to the model subfolder you'll see things like
{ AllinOne } {Common} and {LGUP_LGNPST} folders...
at that point just right click and rename {Common} folder to {Commonbak},
then take my zip file I'm attaching and unzip it and inside will be Common folder...
just Copy / Paste that new Common folder to where the old one is..
set permissions of folder { read-only} and open the folder find file called { UI_Config.lgl }
and set it's permissions to READ ONLY . otherwise it'll be erased once you start LGUP.
and see If that changes anything with being able to Dump...
It's let me dump every LG i've plugged into it...
so I should think it should work for you too...

@Reckless459
is there nothing further?

LgPWN'd said:
@Reckless459
is there nothing further?
Click to expand...
Click to collapse
Dude...
First off let me say MertoPCS has the biggest pile of **** customer care department. I'm still waiting on my new device to comr from the warrenty department. I did however fix the sim issue (again metro sucks leaky bowels). I will definitely post any new developments as soon as the happen.
Oh also i did a dump on another phone (aristo 2) and had no issuses. And i saw what ypu meant with the boot_COM##. Thanks for the help.

LGUP dll
Sorry apparently i haven't reloaded this page in 12 hrs and their has been progressing i have 2 aristos im going to work on this also.
i will step in and help out ill read the updates and post further
---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------
LgPWN'd said:
@Reckless459
is there nothing further?
Click to expand...
Click to collapse
I had a question i would like to chime in here, can i do an extraction on the KDZ with lg extractor i see a boot image in it and flash that?

Nvitethedark said:
Sorry apparently i haven't reloaded this page in 12 hrs and their has been progressing i have 2 aristos im going to work on this also.
i will step in and help out ill read the updates and post further
---------- Post added at 09:43 PM ---------- Previous post was at 09:35 PM ----------
I had a question i would like to chime in here, can i do an extraction on the KDZ with lg extractor i see a boot image in it and flash that?
Click to expand...
Click to collapse
it may work,
when lgup is being a pain it's worth a try.
I say go for it. but to be certain I'd try flashing the extracted boot.img with partitions DL option in lgup once to make sure it flashes it b4 trying to patch it and flash it again...
Just my 2 cents.

LgPWN'd said:
it may work,
when lgup is being a pain it's worth a try.
I say go for it. but to be certain I'd try flashing the extracted boot.img with partitions DL option in lgup once to make sure it flashes it b4 trying to patch it and flash it again...
Just my 2 cents.
Click to expand...
Click to collapse
Aristo3 FW: X220MA10B "10b" came on the system stock
LGUP V1.14 - patched
DLL v1.0.28.17
The above dll is the only one I have found that will recognize the phone and load LGUP, I have also attempted to use uppercut: Error DLL for X220M10b is invalid install a valid dll
https://imgur.com/1Ptrv3n
however, once i attempt to dump phone reboots into download mode i get: Error: 0x2000, please use latest Dll LAF protocol version is not match dll=0 device 162512928
https://imgur.com/5I7GfOa
I attempted to use the LGUPC DLL from the kdz V 10E firmware and that did not recognize the device i also attempted to use your zipped commons.
any feedback on this?
I feel that i should use LG tool update to 0F then use the 0F kdz to attempt all this?

DOWNGRADE Don't UPGRADE
Nvitethedark said:
Aristo3 FW: X220MA10B "10b" came on the system stock
LGUP V1.14 - patched
DLL v1.0.28.17
The above dll is the only one I have found that will recognize the phone and load LGUP, I have also attempted to use uppercut: Error DLL for X220M10b is invalid install a valid dll
https://imgur.com/1Ptrv3n
however, once i attempt to dump phone reboots into download mode i get: Error: 0x2000, please use latest Dll LAF protocol version is not match dll=0 device 162512928
https://imgur.com/5I7GfOa
I attempted to use the LGUPC DLL from the kdz V 10E firmware and that did not recognize the device i also attempted to use your zipped commons.
any feedback on this?
I feel that i should use LG tool update to 0F then use the 0F kdz to attempt all this?
Click to expand...
Click to collapse
If at all posible find the OLDEST firmware possible in kdz and do a full flash of that .
and try your dll mod with that by extracting the dll from said kdz and renaming to what ever the one in Common folder is and keep the UI_Config.lgl in there to keep the extra options if possible...
It's all trial and error with this stuff, so keep at it.
DO NOT flash a firmware.kdz from a different model of the device as it'll flash aboot sbl etc and you'll end with a brick that can't be fixed.
and I've always liked { in my experiments} to use the partitions DL option even when downgrading etc to be able to NOT CHOOSE the boot-stack partitions...
but give it a shot and tell us how it go's.
we may be able to split a root-bounty if we come up with something working across users

LgPWN'd said:
OH WOW what a mess...
I would say it's the .dll in the LGUP causing pain here...
something you can try when you're ready to try again....
remove/uninstall devpatched LGUP and install regular store version
use the Common .dll
and add this file{ UI_Config.lgl } to your Common folder in the lgup install location ...
to make it easier I'll just zip up My common folder for you to replace yours
to do this
right click on lgup, select open file location...
navigate to the model subfolder you'll see things like
{ AllinOne } {Common} and {LGUP_LGNPST} folders...
at that point just right click and rename {Common} folder to {Commonbak},
then take my zip file I'm attaching and unzip it and inside will be Common folder...
just Copy / Paste that new Common folder to where the old one is..
set permissions of folder { read-only} and open the folder find file called { UI_Config.lgl }
and set it's permissions to READ ONLY . otherwise it'll be erased once you start LGUP.
and see If that changes anything with being able to Dump...
It's let me dump every LG i've plugged into it...
so I should think it should work for you too...
Click to expand...
Click to collapse
reinstalled a non-patched version of lgup and used your common folder and set read-only options attempted a dump got this:
https://imgur.com/FJPMUwv

Can I recover Tab3 7.0 Android 4.4.2 WiFi using Haimdall on FWUL and how is it done?

As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?

xdausernl said:
As Odin in Windows does not do the trick for me, flashing stock ROM onto the Tab3, 7.0 WiFi device, I'll now want to try using Haimdall on FWUL.
But to make that happen, I seem need seperate .img files as Haimdall works with seperate files instead of that big tar.md5 file like Odin in Windows does.
So the first question would be:
What tools do I need to get all these seperate .img files out of the stock ROM Odin uses??
In Haimdall I managed to detect the Tab3 device and download and save the PIT file successfully.
But when I try to write into 'recovery' partition using a renamed file (TWRP 3.0.0-0.img) recovery.img, the process failed.
The log shows successfull writing of the PIT file, but it failed on recovery.img with this error 'failed to confirm end file transfer sequence'.
Also, there's no progressbar showing on the Tab3 device, while writing.
I already tried other USB cables, same results.
So the second question would be:
What did I do wrong, or did I miss something?
Click to expand...
Click to collapse
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk

Droidriven said:
To extract the firmware down to the individual .img files, try this thread, it leads to another guide on another site.
https://forum.xda-developers.com/showthread.php?t=2138885
Keep in mind, this guide is a bit old, the basic process is still valid but some things may have changed in how Samsung firmware is put together, there may be some extra steps required for firmware from newer devices.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...

xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.

xdausernl said:
I have to edit the last post, because I can change the stock ROM file name as mentioned before and that did not cause any problems with the md5 hash.
At this point, I can also download all files (10) succesfully from Heimdall with the Samsung tablet.
The only problem is caused by replacing the 'system.img' file, as the tablet immediatly reboots after Heimdall released the device after download was successfully.
It could mean that after the succesfull download, the downloaded system.img file is deleted at immediate reboot of the tablet, which would also explain why there's no changes after tablet reboot.
With all the other 9 downloaded files from Heimdall, it took several seconds until reboot of the tablet.
Click to expand...
Click to collapse
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk

xdausernl said:
Thanks for your reply,
Right after I wrote this text, I came up with another approach ... to just rename the stock ROM extension 'tar.md5' to '.tar' and so I did, then I unzipped the file.
But thanks anyway ...
Inside I found several files and about 6 image files and the PBL.bin file.
For 4 partitions I found an image file, system.img, NVM.img, cache.img and hidden.img.
Guess what ... with Haimdall in FWUL the upload went successfully and there's also a statusbar on Tab3 while at download, where as Odin (any version) in Windows failed on me all the time.
All files needed to upload seperately though, all at the same time gave me this error 'failed to confirm end of file transfer sequence'.
For the boot.img file I couldn't find a partition.
Recovery.img and the PBL.bin file failed to upload using Haimdall with errors 'failed to upload' and 'failed to confirm end of file transfer sequence'.
I also tried to rename a TWRP image to recovery.img, but that upload failed as well.
At this point I only proved the hardware being OK, that is the USB cable and the USB port on the Tab3 device.
It seems like Android operating system crashes after the message windows from antivirus program 'program has stopped', it then shut down and reboot.
After login the same thing happens all over again ... like some sort of boot loop.
And there's just not enough time to change any of the system settings, nor to disable any apps due to all those message windows you have to click first.
Overall status being Android operating system is still faulty.
This means that I just may be able to fix this thing, I only need the right tools to get the job done.
And I can't believe there's no one out there that couldn't help me out ...
Click to expand...
Click to collapse
Droidriven said:
Try a windows PC and try flashing via Odin, it tends to work better than Heimdall.
Also, if you are trying to use a system.img that is different than the system.img in your firmware, your bootloader may not be allowing the different system to flash or boot on your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.

xdausernl said:
Thanks for your reply.
But I came to Heimdall because Odin3 in Windows and even JOdin3 in Linux failed.
My guess is that the installed system.img on the system partition the culprit was in this case, because the stock ROM was the correct one for my tablet.
If you don't have the correct software, you either cannot install it or you will get your device bricked.
My device seem to be software bricked, for that matter and that is due to either the root software, anti virus software or an combination of both.
Click to expand...
Click to collapse
Meanwhile I think I found a possible cause for failure using Heimdall-Frontend.
Heimdall-Frontend uses only extracted content of a stock ROM, in my case that's 10 files.
Although the download of the 'system.img' file completed successfully and Heimdall-Frontend releases the connected device, there's still a slightly different behaviour at reboot of Tab3.
Because after the release of the connected device, Tab3 then immediately goes into reboot.
That's not the case with all other downloaded files.
After releasing the connected device, it then takes a few second until the Tab3 goes into reboot.
So my guess is that at immediate reboot the downloaded 'system.img' file will then be deleted from the Tab3.
That would explain why after reboot nothing has really being changed.

Rooting Samsung J4 Core - only official binaries allowed

Hello, apologies if this isn't the right place to post this question but I'm at a complete lost and I'm desperately trying to fix the device. My goal was to simply root the device.
I tried following this guide but by the end of my first run of the guide I had errors with the contacts and phone android apps. But the device still wasn't root. I attempted it again only to break the device completely. I wasn't even able to open Android Recovery and only flashing the bootloader only did I manage to to back to the recovery screen. However, from here, I am unable to flash the firmware any further. I only get a message now notifying me: "only official released binaries are allowed to be flashed".
What I'm hoping to achieve with this question is to get some direct guidance on how to resolve my current error. I've followed a few guides and thread a few threads but nothing seems 100% applicable to my issue or the device.
Using Odin3_v3.13.1 and what I think is the stock firmware for J4 (following the download links on the guides) I do the following:
Unzip the binaries with 7zip ZS to uncompressed the various files, specifically the AP, BL, CP, CSC and HOME MD5 files.
I further unzip the AP file and drag the boot.img.lz4 into lz4.exe to just give me the img file.
I run that through Magisk Manager to create a patch file (on another phone) and reupload back to the pc.
I then take the patched file and drag it into lz4.exe to just give me the img.lz4 file
I then delete the original boot.img file and select all of the files and compress into a tar archive.
OR, even without doing any of that and just straight selecting the AP file without doing the patching, I either get a straight up FAIL! (Auth) from Odin and if that doesn't happen, I get the error on the phone itself saying that "only official released binaries are allowed to be flashed".
And that's where I'm just stuck. I know there are many guides, and I tried making sure I have the best one and knowing what to do, but I think I messed something up along the lines. Any assistance would really be greatly appreciated.
Thank you.