Database Users

Verizon Galaxy Note 3 bricked?

I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> cache.img.ext4
<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)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.

Update!
I came accross this method, http://forum.xda-developers.com/showthread.php?t=2483380
I followed the instructions on flashing to stock with Odin and I didn't have any luck in getting it to work. I downloaded the MI9 tar.md5 file, and the pit file selected them in there proper spots in the program and ran it. I got this error.
Code:
<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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and this error on my phone
SW REV CHECK FAIL : (aboot)Fused 2 > Binary 1

This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.

Misterxtc said:
This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.
Click to expand...
Click to collapse
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."

luckychalmz said:
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Click to expand...
Click to collapse
You might need to flash MJE instead of MI9 with Odin.

Misterxtc said:
You might need to flash MJE instead of MI9 with Odin.
Click to expand...
Click to collapse
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.

luckychalmz said:
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.
Click to expand...
Click to collapse
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707

Misterxtc said:
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707
Click to expand...
Click to collapse
That one is definitely going faster. Thank you. I will try this one once it's finished.

luckychalmz said:
That one is definitely going faster. Thank you. I will try this one once it's finished.
Click to expand...
Click to collapse
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.

Misterxtc said:
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.
Click to expand...
Click to collapse
That fixed it, thank you. Appreciate your help.

luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Cool, I'm glad to help and direct you to the info that has been shared. Enjoy.

I know a much faster,simpler and less data-damaging wau
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!

technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.

Still having issue with Samsung Write Protection
fanatic4hockey said:
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.
Click to expand...
Click to collapse
technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
I was able to flash the PIT file with Odin like you said which enabled me to get back to recovery, but I am still having issues with the Samsung Write protection being enabled (which is preventing me from flashing anything with Safestrap including trying to fully wipe and restart). I found out after attempting to flash my verizon note 3 that the write protection was an option that needed to be unchecked on the phone before flashing. Now I can't change it without being able to login all the way into the phone. Are there any options out there to change the write feature outside of being able to actually load the phone, like ADB?

luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

vampirelife said:
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks similar to what I was getting from Odin. Did you have to uncheck the write protection in your phone settings before flashing anything? Someone told me that might be the cause of what happened with mine since I didn't even hear about doing so until I had already attempted to flash my phone.

im also getting a fail just after aboot. I originally attempted to install the deodex version on kitkat and originally was still able to access safestrap.
I have tried flashing every rom i can get my hands on over odin. ive tried making a recovery from my other note 3 via safestrap and swapping the micro sd over to this one. did not show up when i went to ss recover. so i booted to recovery cleared cache. still got aboot failed(auth) so i booted to recovery again and cleared everything except data. (including system) now i cant access SS any longer. get stuck on bootload screen or get verizon sofware assistant message. still unable to flash roms via oden i have tried everything but lollipop and odin versions 3.9 3.7 3.10
im am completely lost. im almost ready to ship it to someone to fix it for me.

I'm gonna bump this in the hopes someone sees it and can help me.

luckychalmz said:
I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Root_de_la_Vega.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
cache.img.ext4
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.
Click to expand...
Click to collapse
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
http://www.sammobile.com/firmwares/database/SM-N900V/
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
marcotheclepto said:
I'm gonna bump this in the hopes someone sees it and can help me.
Click to expand...
Click to collapse
Sent from my Note 3 via Tapatalk

donc113 said:
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
thanks, im just jumping straight to 5.0 and hoping for the best. half hour left on the download. fingers crossed
*update* it seems the newer version was the answer for me... now to find a way to root it on lolipop... whole point was originally to get hyperdrive and get some headphone software worth using.

[Q] S5 G900X Demo Unit - I can need your help please :)

Dear members,
As following: i have a demo unit which i am trying too install with a original firmware.
I make use of the following tutorial http://forum.xda-developers.com/showthread.php?t=2733083
Downloaded the firmware from The Netherlands for the G900F (G900FXXU1ANCE_G900FPHN1ANC7_PHN)
I've made a backup of the demo-software and set it back for now since i can't get this firmware working on my phone.
When i am trying too send the file with Odin i do get the following error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANCE_G900FPHN1ANC7_G900FXXU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hopefully somebody can tell me what i do wrong?
The phone was wiped totally.
In download mode it says: (after trying with odin)
ODIN MODE
PRODUCT NAME: SM-G900X
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: 0xf (CSB)
WRITE PROTECTION: Enable
UDC START
SECURE CHECK FAIL : sbl1
When i see the above and i look to ''write protection'' it says that i can't send a new firmware to my phone, is that right?
I do really appreciate your answers and i will send a small donation via paypal to the person who has the golden answer for me :good:
Thanks in advance!

It is done now, download a custom recovery made by user: shebi
How can i change the bootloader image which says live demo unit?

I got a demo unit, installed stock s5 rom on it and had the same result. Then went on and installed cyanogenmod on it and everything worked but connecting to the mobile network.

wamelwamel said:
It is done now, download a custom recovery made by user: shebi
How can i change the bootloader image which says live demo unit?
Click to expand...
Click to collapse
Hi wamelwamel, I've been struggling with the exact same problem that you had, with my G900X. What did you do to solve the problem with yours?
D

does samsung galaxy g900f firmware work on samsung galaxy g900x
Answer me fast guys

[Q] Going back to stock from CM12

I have a Sprint Galaxy S4 (SPH-L720), non-spark edition.
It is currently running the Euroskank CM12 Feb 22 nightly.
Everything is working well, except I no longer have any voice/text service. Data (4G LTE), however, works.
Sprint has told me to update my profile/PRL, however, I don't think those options exist in CM12? So I've decided to go back to stock.
I downloaded the L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 file and am using Odin v3.09
It gets very far (>90%) in the install process before it fails:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Do I need a PIT file? Do I extract that from the L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar file?
The Odin screen now shows:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Click to expand...
Click to collapse
I also just finished downloading the L720VPUFNG2_L720SPTFNG2_SPR file, it similarly, also errors out.
When I reboot the phone, it says it's in Emergency Recovery Mode and to connect it to Kies, but Kies doesn't recognize the phone.
Any help is greatly appreciated!

I (half) figured it out.
Tried using a different computer (both Windows 7 machines) to flash back to stock (L720VPUFNAE_L720SPTFNAE_SPR using Odin 3 v3.09) and it went through!
Hit a boot loop, so I factory reset, updated the profile/PRL/activated the device, and everything worked for about 10 minutes.
Then Sprint told me of an OTA update, I installed it, and now I have no service (voice, text or data). There are service bars shown in the system tray, but attempting to even dial out gives me a "Mobile network not available" error.
With no service, I'm unable to update profile/PRL/activate. Unsure how to proceed from here other than maybe trying to flash a different ROM completely then going from there to stock?
I called Sprint and all the lady tried to do was sell me an insurance plan so that I could take it into the store and their technicians could look at it.

@MrCodedude, Try flashing KT's TW kernel or Negamann's r50

JhoonB51 said:
@MrCodedude, Try flashing KT's TW kernel or Negamann's r50
Click to expand...
Click to collapse
It was recommended elsewhere to put the phone in airplane mode, reset, then take it out of airplane mode. That didn't work, but reseating the SIM card did.
I haven't used this Galaxy S4 in awhile, I wonder if there's a problem with the SIM (or maybe the enclosure). I'll probably hold off on flashing a non-stock kernel to see if it still acts up.
I'll also be sad if this is the reason why voice/text didn't work in CM12.

[Q] Need help recovering a bricked SM-900W8

This morning I updated my Note 3 (SM-900W8 on the Canadian Rogers network) to 5.0.
I had rooted this device before then, and had used Titanium Backup to backup all my apps/data. When the initial OTA update failed, someone pointed out that it was because the phone was rooted. So, figuring I had this backup in hand, I factory-reset my phone and went through the update - though I used the Samsung KIES app as it was quicker to download the firmware update than over my phone's WiFi.
Once the phone was on 5.0, I went to restore the backup... and found that Titanium Backup only works when the phone is rooted. Oops.
So, I figure that I need to root my phone again. I find instructions on how to root a note 3 and start to work through it. I go to the link for "Download appropriate CWM or TWRP recovery for your Note 3" and find the one that says "KitKat/Lollipop Android 4.4.2 CWM Recovery" and pick the one "SM-N900W8 Canadian Note 3 – CWM Recovery", because 5.0 is 'Lollipop' and my phone is the SM-N900W8. I attempt to use this with Odin, and Odin reports 'FAIL!' and the phone is stuck on "Downloading - Do not turn off target !!'. I give this a while just in case things take a while to happen... and nothing does, so I figure it did fail. I have no alternative but to turn off the phone now.
And restarting it, the phone comes up in "ODIN MODE" with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The messages at the top of my phone on this screen are:
Code:
ODIN MODE
PRODUCT NAME: SM-900W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD : ENABLE
UDC START
I connect the phone up again, select the Recovery tool in Kies... and the phone is not detected. No matter what I try.
So then I try and download the official firmware N900W8_RWC_N900W8VLU2DOC4_N900W8OYADOC4 from Samsung Updates and try to use Odin to recovery it that way.
Again, the update fails... time and time again.
The Odin messages output is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLU2DOC4_N900W8OYADOC4_N900W8VLU2DOC4_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> 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)
I now have a bricked phone, and no idea how to fix it.
What can I do?

frysco said:
What can I do?
Click to expand...
Click to collapse
1. Reflash STOCK firmware 5.0 for your device: HERE. Factory reset your device when finish of boot.
2. Use TWRP (You can flash this ONE via ODIN) and root your device then.
3. Don't restore your data of android 4.4.2.

I've managed to fix things.
From other searching around, it seems that trying to use Odin via VMWare Fusion on a Mac is a 'known issue' where it gets stuck at this point.
Installed a trial version of Parallels and a basic Win XP install, re-flashed and it WORKED!

[FIXED] J7 pro J730G/DS not booting

Texts in odin mode
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-J730G
CURRENT BINARY: Samsung OFFICIAL
SYSTEM STATUS: Custom
RMM STATE : Prenormal
FRP LOCK : OFF
OEM LOCK : OFF
Secure Download : Enabled
WARRANTY VOID: 1 (0XO30c)
AP SWREV: B:5 K:2 S:3
This is the phone of my friend, i had installed TWRP and was on A7 rom, It all started when the battery of the phone reached to 0% it switched off, and after charging and turning it on, It said only official binaries can be flashed (Not exact same but similar) and i tried to boot to twrp but it dosen't boot, so i treid to install twrp by odin mode, it failed saying same error. I treid to flash stock rom it shows error on odin
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<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> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in phone it shows KERNEL REV CHECK FAIL DEVICE:2, BINARY:0
and when i tried to install stock recovery it says
<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> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and same error on phone.
Can anyone help me with that, i want to install stock rom and magisk.
Solved: I have tried different Odin and Odin v3.13 helped me out as other version doesn't support .lz4 compression format.

You can't downgrade if you flash stock firmware, try latest official rom

darkiiwi said:
You can't downgrade if you flash stock firmware, try latest official rom
Click to expand...
Click to collapse
Downloading, Hope i works

Update: I downloaded latest official firmware and it is stuck in shoot.bin.lz4
I have attached photo of it

CherryFarmer8 said:
Update: I downloaded latest official firmware and it is stuck in shoot.bin.lz4
I have attached photo of it
Click to expand...
Click to collapse
if you stuck at sboot.bin.lz4. It means you need to use higher version of odin or try to install higher version of samsung drivers, hopefully my solution can help

Tomjerryrocket said:
if you stuck at sboot.bin.lz4. It means you need to use higher version of odin or try to install higher version of samsung drivers, hopefully my solution can help
Click to expand...
Click to collapse
This issue is already fixed and i have also edited this post already, i wonder you didn't noticed.
Anyway thanks for your attention.

i cant fix my SM-J730G/DS
HOW DID YOU FIX IT CAN YOU TEACH ME? im hoping that you could help me.. keep on failing on flashing
---------- Post added at 10:01 AM ---------- Previous post was at 09:35 AM ----------
can i ask what firmware did you use, can i have the link?
when i power on, my phone says at the top of the screen " only official release binaries are allowed to be flashed" and then turning off again. Hoping for help.. God Bless...

Hi i have the same problem now, can you tell me how you fixed it? i have the exact same error as you. Thank you i hoping for your response