Need pit file to flash stock with heimdall. or JOdin3. The only one online "J5LTE_EUR_OPEN.pit" isn't working. I have "repartitioned" and lost my original.
pit file here
https://forum.xda-developers.com/galaxy-j5/help/bricked-samsung-galaxy-j5-j500f-t3769340
heimdall cli flash j5 2015 j500f stock 5.1.1
sudo heimdall flash --CACHE cache.img.ext4 --HIDDEN hidden.img.ext4 --ABOOT aboot.mbn --RPM rpm.mbn --QSEE tz.mbn --QHEE hyp.mbn --SBL1 sbl1.mbn --SYSTEM system.img.ext4 --BOOT boot.img --pit PIT-SM-J500F-12-09-2016_11-32-53.pit --no-reboot
Related
Ok, so I was running TWRP 2.8.5.0-trltedt and CM12 with its own kernel. N910G.
If I go to TWRP and install a custom Sh1twiz ROM via ZIP + nadia kernel it's fine and it works.
If I go to TWRP and wipe System, Dalvik and Internal Storage and then go into Download Mode and use Odin 3.10 to install an official ROM (N910GDTU1ANK3_N910GOLB1ANK3_N910GDTU1ANK3_HOME.tar.md5) from Sammobile then I get a:
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
The phone screen says:
Volume size is too big 92160 < 204800
ODIN: Invalid ext4 image
At this point if I restart the phone and try to enter TWRP (recovery) it doesn't work anymore, it goes into another screen that says:
"Firmware upgrade encountered an issue" etc.
If I go again into download mode and flash TWRP with Odin the flashing works.
Then, if I try to enter recovery it says something... I cant read it cause it happens too fast, but it's something related to "formatting", "cache", "wipe".
Then the phone restarts by itself and the phone seems to work.
However, if I go again in download mode and try to flash the original firmware with Odin, I get the same FAIL! (Ext4)... so this means the core problem was not fixed by TWRP.
I heard I may need to flash a PIT file with re-partition clicked?
But where do I find the right PIT file for N910G?
The thing is that even if the phone seems to work I am afraid that later I might find out that it doesnt work properly... after spending hours installing everything on it...
Hey guys. I tried to install the N910CXXU1BOC5 firmware on my Note 4 and this is what I get in Odin :
...
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
For the first time ever I can't flash with odin. What should I do ? I tried both 3.04 and 3.10.6 versions of Odin and both return "FAIL" as result and now I can't use my phone. Please help
GeorgEveS said:
Hey guys. I tried to install the N910CXXU1BOC5 firmware on my Note 4 and this is what I get in Odin :
...
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
For the first time ever I can't flash with odin. What should I do ? I tried both 3.04 and 3.10.6 versions of Odin and both return "FAIL" as result and now I can't use my phone. Please help
Click to expand...
Click to collapse
make sure you follow all the steps, remember you have to unzip the file you downloaded then you will be able to flash it via Odin, remember to click on PDA, and Re Partition have to be disabled, only Auto Reboot and F.Reset Time should be checked, good luck, cheers:fingers-crossed:
make sure reactivation lock is uncheck at security settings...
In the Official Firmware of Galaxy J5 2016 the following files are seen:
abbot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
hyp.mbn
NON-HLOS.bin
sec.dat
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
I want to make a 4-file ROM for j5 2016. So I should know in the above list which files relate to Boot(loader), which files relate to PDA, which files relate to CSC, and which files relate to Modem.
Can anyone guide me?
error flashing firmware.
system.img.ext4 FAIL! (Write)
how can i fix this ?
Ive been told if anyone can fix my issue it is you guys,
As mentioned the phone wont boot and is stuck on the logo/powered by android screen.
Everything is stock Samsung.
I can not access recovery mode but can access download mode.
I downloaded the lastest offical Samsung firmware for my model (SM-G950F. BTU. G950FXXS5DSJ1) and using Odin tried to flash.
This did not work, i have pasted the log below, but basically it starts but then doesnt progress. Nothing happens, the phone does not reboot or do anything for that matter other than stay on the downloading screen.
Any advice would be appriciated,
Cheers
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4162 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
Is the device model on bootloader the same as firmware?
I remembered that similar issue happens when there's a problem with the kernel (boot.img) either it wasn't flashed correctly, or is older than the actual firmware.
Have you tried Odin 3.13.3 which is specially for One UI?
https://www.and roidsage.com/2019/07/02/download-latest-odin-3-13-3-for-installing-and roid-9-0-pie-oneui-samsung-firmware-update-and-usb-drivers/
(Remove spaces)
Thanks for your reply,
I have tried both 3.13.3 (cant remeber when i downloaded from) and 3.13.1 found here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Neither worked.
Is bootloader and download mode the same thing? If so it says product name: SM-G950F which does correspond to the firmware ive downloaded.