Samsung J3 - J320FN UK EE bricked? - Samsung Galaxy J3 (2016) Questions & Answers

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

Related

[Q] Soft-bricked Verizon Galaxy Note 3

(Previous thread can be seen here)​
Hi all,
Thank you for whom reads this thread. - Very recently I tried to root my Samsung Galaxy Note 3. The method I was using was the Kingo application that isn't prohibited on the forum which I now know. At this point I am unsure what to do, besides flashing this but I am unsure if this method will work. Plus I do not know how to flash this or where to even begin.
Basically in short, I tried doing the following:
Root with the Kingo root application that I got from the official site.
After I used Wanam Exposed to customize my stock ROM.
Played on my phone for a bit and then I got a random error: "Unfortunately, System Ui has stopped"
I posted a thread about this issue (without much detail on what I was doing) and I was recommended to flash these stock files which didn't work. Here is the following errors while I try to flash the file in Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I do not know what to do. I am not hard bricked but I assume I am soft bricked because my phone will not boot into my system because of the error I posted above. If anyone can get me on the right track this would be great. Thank you.
the same thing has happened to me before and i plugged my phone into the computer and used the built in verizon upgrade center and went to the repair section
Storm.hf said:
(Previous thread can be seen here)​
Hi all,
Thank you for whom reads this thread. - Very recently I tried to root my Samsung Galaxy Note 3. The method I was using was the Kingo application that isn't prohibited on the forum which I now know. At this point I am unsure what to do, besides flashing this but I am unsure if this method will work. Plus I do not know how to flash this or where to even begin.
Basically in short, I tried doing the following:
Root with the Kingo root application that I got from the official site.
After I used Wanam Exposed to customize my stock ROM.
Played on my phone for a bit and then I got a random error: "Unfortunately, System Ui has stopped"
I posted a thread about this issue (without much detail on what I was doing) and I was recommended to flash these stock files which didn't work. Here is the following errors while I try to flash the file in Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I do not know what to do. I am not hard bricked but I assume I am soft bricked because my phone will not boot into my system because of the error I posted above. If anyone can get me on the right track this would be great. Thank you.
Click to expand...
Click to collapse
Could you please link me to the software
Sent from my GT-P5113 using xda app-developers app
I think your phone may have had firmware that was later than what you were trying to flash. From what you posted you were flashing mi9 which was the first one with initial released phones. They would explain the soft brick. Then there was update MJ7 and now there is MJE. I would suggest finding the MJ7 tar file and try that and see if that will fix the soft brick. If same results then try MJE.
Hope this helps.
Tap'n & Talk'n on my Note 3

Help Dead S5 G900F after trying downgrade

Hello...
Please if someone could help me and guide me to rescue my brand new S5 G900F :crying:
Starting to get desperate here... as I did not backup my EFS was going to do it after rooting
Here are the steps I did to get into trouble:
Upgraded to Stock Poland G900FXXU1BNL2 Loolipop to the phone everything was fine... except some app crashes as Facebook so decided to return to 4.4
So put the phone into recovery mode did a full wipe and loaded G900FXXU1ANJ1 from poland too with odin
The phone booted and looked all ok so turned it off after first boot withouth even touching the language settings.
Put again into dowload and decided to run CF-Auto to root the phone
Here everything started and Fail! message appeared at ODIN.
So turned of the phone and now the phone auto boots with message "Firmware upgrade encounter an issue. Please select recovery mode in Kies & try again."
So put the phone in download mode and try to put again stock 4.4 G900FXXU1ANJ1 again but got fail message during system.img.ext4 writting multiple times.
Then tryed to go back to Loolipop same issue multiple times...
Then finally try with lollipop after restarting computer, changing usb port, unziping again the firmware, etc...but from off state removed battery then putting back, then connecting the usb cable so from the "Firmware upgrade issue" screen hit the start and the firmware finally succedd the process.
The phone boot normally ....but I'm such and IDIOT that I said ok why not get back to 4.4 as it worked first time...
So put the phone back into download mode and try to load 4.4 stock rom G900FXXU1ANJ1 again but FAIL! appeared again and now I cant get pass it even after trying what solved the issue before...
Please help ideas etc ???
Now if I try to load 5.0 G900FXXU1ANJ1 it fail at the begining of system.img.ext4 writting...
If I try with 4.4 G900FXXU1ANJ1 from "Firmware Upgrade issue" screen the best I could get was half of the system.img.ext4 writting once before getting FAIL message again but most time it fails at the begining too.
These is what I'm getting from Odin now every test...
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL2_G900FXEO1BNL1_G900FXXU1BNL2_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> 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> 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)
Thanks a lot for your time in advance for helping me...
Let me know if you need more info or anything please.
SOLVED!
GREAT NEWS
Solved myself on the last try before heading to bed crying hehehe
What I did for the record to others...and dont actually as why it worked...but it did...
Leaved the phone without battery almost half hour, then shutdown computer, unziped the 5.0 stock rom once again to have one fresh copy, open odin loaded rom wait till md5 check, then change usb port once again, then put battery to phone, then connect cable as soon as odin recognized it hit start and pray.
WORKED...
So the phone restarted as normal etc but there was the app updating screen...after it the phone was like dumb and some poland message only displaying. So turn it of, put on recovery, did cache clear and then complete wipe and restarted, Now everything is back to normal...
Phone now on 5.0 and staying so at least I find a way to backup my efs folder and stop sacking from these time mistake. I will only downgrade if safer method available or teste or maybe updating to the new 5.0 G900FXXU1BNL7 that just get out and forgeting about the downgrade well what I wanted was to open LTE bands... maybe some day...also available on 5.0 LTE band opening
For know happy having it back working
Good that you solved it and even better that you explained how you solved it! :good:
Seems like your phone wants you to stay on 5.0, hehe.
Sent from my SM-G900F using Tapatalk
Looks like he wants 5.0 stock untouched really bad...
As today I had another episode with it... LOL
It got BNL7 over OTA yesterday after all everything went perfect... but today I try to root it using CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug, etc. just like instructions but at the end of process FAIL!
Had to put again stock BNL5 to recover it.
Don't know what to do or I should wait for update on the CF-Auto to use it. In the manual I found said it should work on BNL7 but looks like it does not.
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

S4 GT-I9506 is stuck on Firmware upgrade encountered an issue

this model seems difficult (gt-i9506)
i tried to root it via towelroot, then kingoroot, these failed but then now the reboot is stuck on "firmware upgrade encountered an issue"
ive tried Kies firmware recovery but the download fails after 80%,
ive tried the sammobile download the ROM this too fails, network drops out tried this 3 times
i want to try Kies emergency recovery but cant find any recovery code
im stuck i dont know what to do now been researching for 4 hours cant find solution :crying:
could anyone please help?? am going crazy over this spent 2 days researching and finding nothing
Download a complete stock rom and flash it with ODIN. You have to uninstall KIES beforehand (they are conflicting).
thanks for reply...
i took kies off and this is what Odin is giving me...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMHF_I9506VAUAMH3_I9506XXUAMHD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the device says this.....
SW REV CHECK FAIL: [aboot]Fused 1 > Binary0
does this highlight anything that could be going wrong?
Not sure... but looks like the rom is not for that device. Are you sure you have a i9506?
on samsmobile GT-I9506/VAU/ Roms (i cant post link)
well the first ROM was 4.2 android (bottom of ROM list), so then tried 4.4 (top of ROM list) android it failed again but with different Odin errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNJ1_I9506VAUCNJ1_I9506XXUCNK1_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
can anyone see the fault here...?? no error came up on the device, only on Odin this time
Did you restart after KIES de-installation? Was USB driver successfully missing (so you had to install one manually for ODIN)? If not, you probably still have drivers/files running from KIES.
Otherwise, try a different computer to double check its not the system.
If you originally updated to Android 4.4.x or later on this device, you cannot install 4.3.x or lower as Knox within the bootloader will actively prevent Odin from functioning. As to Odin, make sure you're using the original cable, are not using a hub, have Kies disabled or uninstalled, and use a different USB port. Odin sometimes is picky about the ports it uses.
If you can get the ROM issue resolved, use CF-Autoroot to root, keeping in mind that you will trip the Knox flag in doing so. Towelroot and other one-click root methods don't work on your device.
FIXED IT!!!!!!! :laugh::silly::good::cyclops:
Moved all operations to a different PC running XP with no kies on it
The error still occurred "write fail"
So instead i tried Odin 3.09 instead of 3.07 but most of all i changed usb cables, found an original cable off my mates Nokia
then boom!!! she starting writing!!!
Thankyou so much you legends, you are now my best friends forever!!!
Strangely the new flash, all my old previous data & apps are still on there??? somehow the network is not locked either which i was fearing being a vodafone ROM
still want to root it though
Flashing a ROM through Odin doesn't wipe the data partition, which is why your apps are untouched.

[Help] Getting errors in odin when trying to return to stock rom!

Hey guys ive been trying to find a fix for this for weeks now, there has to be a android guru out there that knows how to fix this. but anyways i flashed twrp and rooted my device sucessfully and got the custom rom to install without a hitch and the bootloader is also unlocked. but the issue is that in the new rom i cant get my 4g lte connection to work whatsoever so i decided to go to sammobile and downlaod the stock rom for my device the SM-S902L straight talk galaxy s5. i put my phone into odin mode/fastboot mode and load up the stock rom in the ap slot in odin, i hit start and always get the following error
I really hope you can help me with these. I am begging my data is not lost, I have lots of useful things... Im hoping i wont lose that.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195UBUBNA2_I9195CHOBMK1_I9195UBUBNA2_HOME.tar.md 5 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> sbl2.mbn
<ID:0/003> sbl3.mbn
<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)
the device reads SW REV CHECK FAIL: [aboot]"Fused 3" > "Binary 2"
Anyone know what these errors mean and what to do?

unroot galaxy s4 Odin fail

I am trying to return my Galaxy s4 SGH-1337 to the original - to unroot it. I rooted it but then the wifi didn't work. I tried to fix the wifi issue but after many hours of trying, I decided to just reinstall the original firmware. I downloaded the I337UCUAMDL_I337ATTAMDL_ATT.zip, expanded it and ran it with Odin and it failed. Following is the message stream from Odin.
If anyone can help me with this I would really appreciate it. BTW - I can't download anything directly to the phone because wifi is not working.
Odin message stream:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try again with:
Another USB port
Another USB cable
Another PC
Another Windows version
Another Odin version.
Your phone was issued by AT&T and looks to have a locked bootloader and the ROM you are trying to flash is too old.
ROM is too old
audit13 said:
Your phone was issued by AT&T and looks to have a locked bootloader and the ROM you are trying to flash is too old.
Click to expand...
Click to collapse
Audit13,
How do I unlock the bootloader and get a more recent ROM? Thanks.
The bootloader on the i337 cannot be unlocked once it has been locked.
Look here more information: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642

Categories

Resources