Bricked SM-J510FN Help - Samsung Galaxy J5 Questions & Answers

Hello everyone,
I bricked my phone…. It is a SM-J510FN and when I start it right now, it shows "An error has occured while updating the decive Software. etc." Smart Switch is not recognizing the decive anymore, I cannot enter TRWP and I tried to Flash the stock Rom with Odin but it fails with the following error :
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2878 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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I would highly appreciate any help since I am running out of ideas what to do....
Thanks in Advance!

ottavio22 said:
Hello everyone,
I bricked my phone…. It is a SM-J510FN and when I start it right now, it shows "An error has occured while updating the decive Software. etc." Smart Switch is not recognizing the decive anymore, I cannot enter TRWP and I tried to Flash the stock Rom with Odin but it fails with the following error :
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2878 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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I would highly appreciate any help since I am running out of ideas what to do....
Thanks in Advance!
Click to expand...
Click to collapse
Did you try flashing TWRP again? Bc you flash stock one! If you could enter twrp, flash some of ROMs for your device.

RootingPro-18 said:
Did you try flashing TWRP again? Bc you flash stock one! If you could enter twrp, flash some of ROMs for your device.
Click to expand...
Click to collapse
Thank you for your answer. I did try that but was unable to to boot into TWRP. I finally managed to Flash the stock ROM via Odin. The mistake I pointed out above was fixed by changing from a 3.0 USB to a 2.0 USB port. Weirdly Odin seems to create Errors when using 2.0 in some rare Occasion. For everyone encoutering the same I encourage you to check if you are using a 2.0 USB.
Thank you for the answer anyway. Thread can be closed.

ottavio22 said:
Thank you for your answer. I did try that but was unable to to boot into TWRP. I finally managed to Flash the stock ROM via Odin. The mistake I pointed out above was fixed by changing from a 3.0 USB to a 2.0 USB port. Weirdly Odin seems to create Errors when using 2.0 in some rare Occasion. For everyone encoutering the same I encourage you to check if you are using a 2.0 USB.
Thank you for the answer anyway. Thread can be closed.
Click to expand...
Click to collapse
i had no issues with 3.0

Related

help needed!!! stuck odin recovery on stock image

<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please any help????
nonliner said:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please any help????
Click to expand...
Click to collapse
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Edit: Use Odin 3.07 / 3.04
If u are flashing firware try using diffrnt firmware and see result may be better in cases due to new and old firmware
SOLVED!!!
DO NOT USE virtual machine on a Mac!
find a regular PC with win7
and do exactly what samersh72 says here: http://forum.xda-developers.com/showthread.php?t=2265477
SOLVED
SOLVED!!!
DO NOT USE virtual machine on a Mac!
find a regular PC with win7
and do exactly what samersh72 says here: http://forum.xda-developers.com/showthread.php?t=2265477

[Q] Need Help odin trouble

im sure there are alot of topics like this but last time i tried a move like this i soft bricked my phone so i need help :/
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
this is the error i dont know whats wrong didnt use a pit file and i kinda dont want to disconnect my phone now last time i did that it got soft bricked i did everything in the unroot guide (noob friendly) btw. using odin 3.10.6,samsung s4 gt-i9505
its all good now used odin 3.9 i think the 3.10 was faulty,the post can be closed or deleted

In serious need of some help :(

Hello all,
So ill make this short and sweet, I have an S5 the G900F and it wont boot, it just turns on, shows the Galaxy S5 logo, then appears to start the next Samsung logo but crashes instantly and restarts (does this on a loop)
I have attempted to use odin and flash using the latest firmware I believe to be correct for the phone, to which it fails at the end on "complete write operation failed". I then proceeded to try the recovery.tar file from the same rom and it worked (took about 10 seconds total) but im still getting the same loop.
Tried Kies and all that jazz, literally doesn't even see the phone so cant do jack, recovery mode doesn't boot, all I can get is download mode (home+voldown+power)
I would be ever so grateful if someone knows the answer to this as its driving me insane.
p.s. im by no way good with android so if im missing something blatantly obvious shout it out.
Thanks in Advance
Where am I going wrong?
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
itsenigma said:
Where am I going wrong?
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try this guide.
Or this little tutorial:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
Click to expand...
Click to collapse

Needing some serious help G900F

Hello all,
So ill make this short and sweet, I have an S5 the G900F and it wont boot, it just turns on, shows the Galaxy S5 logo, then appears to start the next Samsung logo but crashes instantly and restarts (does this on a loop)
I have attempted to use odin and flash using the latest firmware I believe to be correct for the phone, to which it fails at the end on "complete write operation failed". I then proceeded to try the recovery.tar file from the same rom and it worked (took about 10 seconds total) but im still getting the same loop.
Tried Kies and all that jazz, literally doesn't even see the phone so cant do jack, recovery mode doesn't boot, all I can get is download mode (home+vol down+power)
I would be ever so grateful if someone knows the answer to this as its driving me insane.
p.s. im by no way good with android so if im missing something blatantly obvious shout it out.
Where am I going wrong?
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in Advance
Which firmware are you using? Do you have a branded or unbranded phone? What happens if you try installing unlocked BTU firmware? This was a problem of mine when I had a branded phone and then I got the motherboard changed due to a display crack and then I couldn't install my branded firmware and only unlocked firmware like BTU. If I wanted to install my locked (DRE) firmware, it failed at the same point on odin like on yours (hidden write) . Idk if installing unbranded firmware helps, but atleast try it out

[Solved] Samsung Galaxy J5 (J500F) bricked !!

Hi guys
I have a bricked Samsung Galaxy J500F device.
Previously I have installed custom rom on this device and one day I was getting an error "Custom binary blocked by frp lock j5" . To resolve this issue I was trying to flash a stock rom through Odin but I'm getting error "Complete(Write) operation failed."
In android recovery I am getting this error message "E:failed to mount /system (Invalid argument) can't mount '/system '(Invalid argument)"
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2046 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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please suggest me a prior fix for this issue
Thanks
Ytx8 said:
Hi guys
I have a bricked Samsung Galaxy J500F device.
Previously I have installed custom rom on this device and one day I was getting an error "Custom binary blocked by frp lock j5" . To resolve this issue I was trying to flash a stock rom through Odin but I'm getting error "Complete(Write) operation failed."
In android recovery I am getting this error message "E:failed to mount /system (Invalid argument) can't mount '/system '(Invalid argument)"
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2046 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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please suggest me a prior fix for this issue
Thanks
Click to expand...
Click to collapse
Try to flash latest Marshmallow for j500f even from other countries
Mscreams said:
Try to flash latest Marshmallow for j500f even from other countries, if failed search for solutions on xda there is unbrick files
---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------
Try this one
https://mega.nz/#F!RRQhWCSS!4yrrnUkswxEHiqFI1tgzVQ
Click to expand...
Click to collapse
Man no! He isn't bricked he just has frp lock. Don't use the debrick.img for frp lock. Just a quick Google search will solve his problem.
Also if your going to use files that people upload then give credits.
garylawwd said:
Man no! He isn't bricked he just has frp lock. Don't use the debrick.img for frp lock. Just a quick Google search will solve his problem.
Also if your going to use files that people upload then give credits.
Click to expand...
Click to collapse
I have solved this issue by following these steps :
* (Re-Installed) Samsung Galaxy (Android USB Driver) from their website
* Tried flashing the device after reinstalling usb drivers and boom... it worked
Flashed the stock rom from Sammobile
Still, I was getting the same error for the first time then I tried again then it worked like a charm...
Thanks Guys for the suggestion.

Categories

Resources