So I was trying to root my phone. I've done this process many times before so I know the steps, just need the newest files. Bear with me as I don't know the terminology all that well, but you'll get the point.
I found a page that was showing how to root your A5, and supplied the files. So I connected my phone, used Odin how I should, installed the files, then after my phone reboot, at the bottom of the page, it stated that this will only work with 5.x.x. By the time I read this, it was too late. I have 6.0.1. Now my phone boots up and just hangs on the "Samsung Galaxy A5" screen with "recovery is not seandroid enforcing" and "set warranty bit: recovery". I can't get past that. I can't turn the phone off by holding the power, I'm only able to get back into the "volume down + home + power" screen. So I figured, "maybe installing the proper file over it will fix it!" It hasn't. I've tried many files but nothing will work.
I figured, I'll install Kies and install the OEM rom. Nope. Kies doesn't even recognize my phone now.
So I'm sitting here with a pretty fancy paper weight. It's not that heavy so it's not even that great of a paper weight...
I really need help getting my phone back up and running. I'd prefer it to be rooted but if that's not an option, so be it. Any help is appreciated!
SLWRTHNU said:
So I was trying to root my phone. I've done this process many times before so I know the steps, just need the newest files. Bear with me as I don't know the terminology all that well, but you'll get the point.
I found a page that was showing how to root your A5, and supplied the files. So I connected my phone, used Odin how I should, installed the files, then after my phone reboot, at the bottom of the page, it stated that this will only work with 5.x.x. By the time I read this, it was too late. I have 6.0.1. Now my phone boots up and just hangs on the "Samsung Galaxy A5" screen with "recovery is not seandroid enforcing" and "set warranty bit: recovery". I can't get past that. I can't turn the phone off by holding the power, I'm only able to get back into the "volume down + home + power" screen. So I figured, "maybe installing the proper file over it will fix it!" It hasn't. I've tried many files but nothing will work.
I figured, I'll install Kies and install the OEM rom. Nope. Kies doesn't even recognize my phone now.
So I'm sitting here with a pretty fancy paper weight. It's not that heavy so it's not even that great of a paper weight...
I really need help getting my phone back up and running. I'd prefer it to be rooted but if that's not an option, so be it. Any help is appreciated!
Click to expand...
Click to collapse
Dont panic, you're only soft bricked.
I take it you installed cf-autoroot?
Go to Sammobile.com and download the firmware for your device and region.
Follow the instructions on the firmware page to install and flash with Odin.
This will get you back up and running as normal again.
Next time read the WHOLE post, let that be a lesson to you! [emoji6]
ashyx said:
Dont panic, you're only soft bricked.
I take it you installed cf-autoroot?
Go to Sammobile.com and download the firmware for your device and region.
Follow the instructions on the firmware page to install and flash with Odin.
This will get you back up and running as normal again.
Next time read the WHOLE post, let that be a lesson to you! [emoji6]
Click to expand...
Click to collapse
Major lesson learned on this one. When I click "Download", I get to a page that says "Session has expired. Please logout and login again. Error: S1S" and can't get the file... My amazing luck continues.
Edit: Strangely enough, I was able to get it by going into incognito mode. Looks like this mode is good for something other than porn! Neat. Trying that now.
At first it didn't work:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I tried the newest version of Odin I could find:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<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> 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> sec.dat
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone rebooted and and what do you know, I got my phone back! Thanks for the help ashyx!
FINALLY
My pre-historic a500w is running mm 6.0.1.
I thought ODIN was going to overwrite the partitions, thus installing a fresh and virgin copy of MM 6.0.1....
But to my surprise it upgraded 5.0.1 to 6.0.1... All good except King Root who is *****ing....
looks like TWRP recovery is gone.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<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> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<<< System >>>
Manufacturer: samsung
Model: SM-A500W
Brand: samsung
Board: MSM8916
Device: a5ultebmc
Hardware: qcom
Platform: msm8916
Product: a5ultebmc
Serial: ......
Serial (RIL): ............
Installed RAM: 2 GB
<<< CPU >>>
SoC Model: Qualcomm Snapdragon 410 (MSM8916)
Core Architecture: 4x ARM Cortex-A53 @ 1190 MHz
Manufacturing Process: 28 nm
Instruction Set: 64-bit ARMv8-A (32-bit Mode)
CPU Revision: r0p0
CPU Cores: 4
CPU Clock Range: 200 - 1190 MHz
<< Telephony >>
Phone Type: GSM
Network Operator Name: TELUS
Network Operator Country: Canada
SIM Provider Code: ................
SIM Provider Country: Canada
SIM State: Ready
Network Type: Unknown
Data Connection State: Disconnected
Data Activity: None
Device Is Roaming: No
<<< Android >>>
Android Version: 6.0.1 (Marshmallow)
API Level: 23
Android Security Patch Level: 2016-07-01
Rooted Device: Yes
Android ID: ..............
Baseband: A500WVLU1BPG4
Bootloader: A500WVLU1BPG4
Build ID: MMB29M.A500WVLU1BPG4
Codename: REL
Fingerprint: samsung/a5ultebmc/a5ultebmc:6.0.1/MM````````````
ID: ...........
Incremental: A500WVLU1BPG4
Related
Evening all ,
Hopefully someone here can help , Im somewhat of a newbie to this but was currently running Xnote Rom on 4.3 , I tried to upgrade to N9005XXUGNG1 following steps read on a well known website.
I received a "invalid ext4 image" error from odin and now stuck in a soft brick state where i can only access download mode. I am currently trying to get out of this back to a stock phone. I live in the UK and am on EE 4G.
Thanks in advance
UPDATE: Tried flashing N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_HOME.tar.md5 with the following results:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hmm..
try this..
take battery out and put it back in after 30 seconds.. then boot to download mode..
use odin to flash the latest gng1 rom..make sure to tick update bootloader in odin
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Killberty said:
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Click to expand...
Click to collapse
Could you tell me which one , as the latest i can see is the GNG1 and i am not getting on well with that at present
xinfinityoO said:
hmm..
try this..
take battery out and put it back in after 30 seconds.. then boot to download mode..
use odin to flash the latest gng1 rom..make sure to tick update bootloader in odin
Click to expand...
Click to collapse
Same problem..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005H3GGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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)
Just to let you whats on my download screen too :
the little android man
ODIN MODE
PRODUCT NAME - SM-N9005
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX KERNAL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2 T2 R2 A3 P1
WRITE PROTECTION: ENABLE
UDC START
ODIN : INVALID EXT4 IMAGE
Hope this helps ... And thanks for trying to help :cyclops:
Sometimes I get the android man and others I get a phone with a warning symbol and a pc saying " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Killberty said:
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Click to expand...
Click to collapse
It worked , Thank you !!! :good:
TL;DR: My phone is in a bootloop. Attempts to flash back to stock or perform a factory reset haven't worked.
Originally posted on Reddit at r/AndroidQuestions and r/TechSupport. Please forgive me if this is an oft-discussed topic, but I've yet to find anything that's helped me.
A little background: I rooted my Samsung Galaxy s5 (Verizon) in August, 2014. No third-party ROM was installed; just root with Nova Pro, Gravitybox, and Xposed. I had no issues until about 2 months ago when my phone stopped rotating. It'd start rotating again after removing the battery, but eventually that stopped working, too, even in safe mode. I assumed I installed something weird, so I did a factory reset. That didn't fix the problem, though, so I intended to flash the stock ROM for a total reset. Earlier this week, my phone wouldn't connect to wifi. I powered off, removed the battery, and powered back on. And lo, le loop.
Solutions I've attempted:
1) Removing my microSD card. Didn't work.
2) Cache wipe. When I hold the power, home, and volume up buttons, I arrive at this screen. I'm not sure if I can get to the menu shown in the video. Factory reset and safe mode don't work, either. I'm guessing this is because I didn't set up a custom recovery? I'm honestly not familiar with CWM and TWRP.
3) Flash to stock ROM. I did exactly as this guide instructed. I put the ROM on the SD card, then flashed the firmware and kernel. Odin said it was successful and outputted this message (apologies for the wall of text):
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VZW_BOC4_RETAIL_FIRMWARE_ONLY.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> boot.img
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sdi.mbn
<ID:0/003> tz.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NI2_stock_kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)Upon completion, the phone just kept rebooting as it had before.
4) Flash to factory ROM. I downloaded the files for my phone mentioned in this tutorial, but they were in this format, so I'm not sure how to run this in Odin (which is looking for .tar, .md5, etc.).
IN CONCLUSION...
Thoughts? Opinions? Questions?
Did I make any mistakes when attempting the solutions above?
If you are collectively baffled, what are my options? My warranty is voided by my root, is it not? Is there an online service that repairs soft bricks for a nominal fee?
Thank you for your time.
Dear All Sifu,
I'm Chuan here from Malaysia, tonight is my 1st night 24 hours didn't sleep at all due to my phone unable to boot up , it show "Firmware upgrade encountered an issue".
Currently what I'm see if I'm enter Downloading Mode
SM-N9005
Current Binary : Samsung Official
System status : Custom
Reactivation : OFF
KNOX Warranty VOID : 0x1 (4)
Qualcomm Secureboot : enable (CSB)
Previously I'm from 4.4.2 version upgraded to 5.0 which is follow below link guidance - why I'm upgrade is because my Super SU unable to install Binary that time.
http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
I downloaded the firmware from the link above : N9005XXUGBOA5_N9005XEOGBOA4_XEO and Upgraded Android 5.0 successfully
But i want to Root my phone so i use http://kingoapp.com - Afterward Root it fail - Start got this issue unable to start and only show " "Firmware upgrade encountered an issue""
I'm tired as below solutions via using ODIN3 3.09 via enter the downloading mode
-Flash the Recovery CWM-recovery 6.0.4.4 - FAIL
-Flash the Recovery TWRP-2.8.6.0-hlte4.4.img.tar - FAILL
-Flash back the previous downloaded Android 5.0 Rom - FAIL
-Flash CF-Auto-Root-Hlte-smn9005 - FAIL
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOB6_N9005OXXGBOB4_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Really Appreciate all Sifu can give me some guidance .
hi please help me
i have a big problem in my Note 4 Samsung SM-N910C
i was rooting my phone by twrp... after some time i wanna delete root so i enter mY twrp then suddenly
wipe all
1-cach
2- Dalvik cach
3- System
4- Data
5-Internal storgae
6-Micro Sdcard
so i delete the phone system so it is not work again stuck only on twrp and when i try to install N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.zip from sdcard it failed
and when i tried to install from Odin 10 N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.tar.MD5
give me failed
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so please how to fix it
My phone stuck only on Samsung note 4
Not sure if this will solve the issue, but read what I put here: http://forum.xda-developers.com/note-4/help/soft-bricked-note-4-n910f-t3306402
Thought I bricked my n910f, and all is good now!
But i do not have any stock frimaware on my phone i already delete the system
webby93
my odin log data
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't either, I completely wiped it.
What i think happened with me is that odin did put the stock firmware on even when it said it failed after like 5 mins. Then the allsamsungrecovery fixed the rest to let it boot up.
The only issue could be that your odin doesn't seem to have got quite as far as mine did. Can you only enter download mode and that's it?
i can enter download mod
but when i select the frimeware stock
The odin data appear log failed
and on the phone appeared : “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
I'm really sorry, I don't think I'll be able to help any further. My knowledge is just from problem solving the few cases I've had to solve my self. Hopefully someone else can help you here.
Just Flash Lollipop 5.1.1 via odin which have coj5 or upgrade bootloader
you can't downgrade from coj5 bootloader you flash coh4 rom therefore you get error
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
flash this rom through odin complete stock and debloted firmware
download from here
https://docs.google.com/uc?id=0B8-hfA9ycQNoazRkV2xjNThWNWc&export=download
Best Regards,
Ok i have searched the site for an exact answer to the issue i have encountered, with not getting a specific answer to my question. If there is already a thread for my exact problem, or two to solve the two issues i have encountered, please share the link, thank you.
My Wife and I got her son a Galaxy J3 (SM-J320fn) open network, with a Giff Gaff sim, from Argos. Its his first phone and we wanted to see if he could look after it, and if so, we would get him a better model at Christmas. Now his dad wanted to put google family link on the device, and due to it being only android 5.1, this was not possible. This sparked a huge row between my wife and her ex, with him being a general ****. I have tinkered with PC's and X-box 360s before, and thought i could have a go at Rooting the device and installing a custom android 7 rom. I didn't go into this lightly, and read that XDA was the very best place to seek advice and guides. I read up on rooting the device i had, Odin,TWRP and the OS linage android 7 rom. I was comfortable, that although it was very in depth to my skill set, i felt i could do it. I followed the guide to rooting the J320fn, installing the drivers, and USB debugging, fired up ODIN as administrator and installed TWRP, from there i followed the guide to install the custom ROM after than.
all was fine. device was android 7 and google family link was installed. everybody was happy...
My step son left his phone in the school office after his football match after school the other day and the device powered down for the first time since i uploaded the custom rom. When powering up the device we got the custom binary blocked by FRP lock issue. ok... so i came back here to XDA to read a thread about that. i decided that maybe i should have looked into other parental apps instead of messing about with the phone. so i went down the root of restoring the stock firmware and to battle it out with the dad about using a different parental app. so i downloaded the stock firmware for the device, and put the device into download mode. i ran ODIN but the install failed and on the device the loading bar at the bottom was about 5mm into the download and nothing else moved... ****... ok... now what? i took out the battery, and then powered up again. "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" ... Oh man, now what. so i return back XDA to look at this. read the guide and went to KIES3 to install stock firmware, but kies doesn't seem to recognise my device model? i click the emergency firmware recovery, but lists no device to recover?
so now im searching frantically to solve this... i downloaded the stock firmware from SamMobile; J320FNXXU0ARA1_J320FNEVR0ARA1_J320FNXXU0ARA1_HOME.tar.md5 (which took like 17 hours.. meh) and that Fails in ODIN too...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> nvitem.bin
<ID:0/003> PM_sharkl_arm7.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then i read to try install TWRP again, which also didn't work either as that brought up the binary blocked by FRP again and Failed in ODIN.
"<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
So now i really don't know what to do... is it bricked? any and all help would be much appreciated.
Thank you
Rob