Database Users

[HELP] Bricked phone, now Odin and Kies rejecting firmware reset

Last night I bricked my phone, trying to flash the stock modem (NAE) on mobile Odin. As of right now, it does not boot, simply being stuck at the SAMSUNG GALAXY S4 screen. It will not boot into recovery, instead rebooting to the same screen once more. Kies will not see the connection, and I have reinstalled it, the drivers, etc.
Odin does the same thing, but sees the connection. All I get is this after trying to flash the firmware (both with Auto Reboot and F. Reset Time on and off)
<ID:0/003> 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/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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
And the firmware that I am using is the "L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5." I don't know what to do, and I was thinking that someone could help me here.

Were you on NG2 perhaps? If so, you cannot go back to NAE and that would explain the Odin failure.
Go to www.sammobile.com and download the NG2.tar and give that a try.

If only I had thought of that (which I couldn't have)! Thanks, this worked. I was on the NC6 version of the ROM, and have downloaded/installed this. It works like a charm except one thing; the data seems to either not be working, or extremely slow at times. That, and the messaging does not appear to work. Wifi is the same way at times.

Novorone said:
If only I had thought of that (which I couldn't have)! Thanks, this worked. I was on the NC6 version of the ROM, and have downloaded/installed this. It works like a charm except one thing; the data seems to either not be working, or extremely slow at times. That, and the messaging does not appear to work. Wifi is the same way at times.
Click to expand...
Click to collapse
If you were on NC6 you have a triband model (720T) and need NG5.tar.

System software not authorized by Verizon Wireless has been found on your phone

I have a Verizon Note 3 that I rooted then unrooted. Verizon pushed a ota to my phone and now all I get is System software not authorized by Verizon Wireless has been found on your phone. I tried odin toflash back to stock but that fails. Any help would really be appreciated.
Thanks

Once you go to 4.4.4 you are out of luck with downgrading and rooting

I,m just trying to get working again. It tells me
software not authorized by Verizon Wireless has been found on your phone. Go to the nearest vz store. Only they have never seen it. At this point I don't care if I trip the knoxs . I'll run a custom if I have to.

Do a factory reset. Or just ignore the warning

I tried to do a factory reset. It won't let me. The best I can tell is vz locked it.

This is what I get when I try
ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900v_NC2_FW_Updated.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> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

4btyjjeep said:
This is what I get when I try
ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900v_NC2_FW_Updated.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> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You are trying to install an older firmware nc2. You cannot go back. You need to Odin nj6 4.4.4, if Vzw sent nj6 ota to your phone.

Or do a factory reset like I stated.

Factory reset would not work.

How did you try a factory reset?

I couldn't do a factory reset. The only thing I could do to the phone was put it in down load mode. The home button did nothing. The vz dealer said volume down, home button and power should do a reset. When the odin screen popped up they didn't know what to do.
I wasn't sure if i was on 4.2 or 4.4. Before the ota came through I was on 4.2. I could not get 4.2 to download with odin. I went to SamMobile and down loaded 4.4 . That did the trick. My phone is back working again.
Now when I put the phone in download mode now it doesn't say anything about the knox or warranty. Before it said knox 0x0 and warranty 0x1 . I'm not sure if it reset that part or not. I do know I will not let it do another ato again.
I want to thank everybody for their help. I could not have done with out this forum.
I would also like to thank edfunkycold for moving my thread to the right spot
Ed

Factory reset will delete user data, not system data.

Do a factory reset under settings

Caught in a Boot Loop after Rooting

Hi folks,
I have a Samsung Galaxy S4 SPH-L720, 16 GB, Black Mist, Sprint. I bought it from SamsClub this past August and it's connected to the Sprint network through FreedomPop.<Link removed>
FreedomPop doesn't matter in this situation though, but I thought the extra information may help.
This morning I wanted to try rooting it with SuperUS which was already on my phone. Somehow the operation failed and the phone needed to reboot. So I rebooted it, but it would just sit there.. loading. It couldn't get past the FreedomPop loading screen, I left it for about 20 minutes but it was still loading and the back of the phone was really hot. I tried booting into Recovery Mode and that worked so I did a system restore in hopes that that would fix all my problems, but it still wouldn't get past the loading screen. So, I tried clearing the Cache and the Dalvick cache and that didn't help either.
So.. I decided to try to return my phone to stock using Odin and stock Firmware. Everything was going great, but then Odin stopped and said the operation failed. Here's the log.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now what do I do? I do not want to have to buy a new phone.
Thanks for any help.
-Chuck

Fixed
I figured out what I was doing wrong. Turns out I had the wrong stock firmware, once I used the correct firmware it restored and it's working again.
-Chuck

Samsung J3 - J320FN UK EE bricked?

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

(FIXED) Note 4 N910G eMMC Could not start in normal boot dm-verification failed

FIXED IT with ODIN and stock firmware MM 6.0.1 after 2 crazy days !
Thanks for all people posted their issues over the net with their own solutions. So I thought I want to share how I solved my issue and the Note 4 N910G is running beautifully smooth and fast again on stock rom MM 6.0.1 *Except one small issue I place at the bottom of this post and hopefully someone can help to answer*
My Note 4 N910G Australia had all issues that you and I can actually find from Google, thanks to Samsung for these amazing problems - phone gets frozen or restart by itself randomly whole day - only after I just upgraded my Note 4 to the newest upgrade for MM 6 ROM by Samsung.
- Flash read failure
- ODIN: Flash write failure
- eMMC failed to read: eMMC Write Fail
- dm-verification failed
- Could not start in normal boot.
ddi: mmc failure
- No pit binary
- Unable to come to normal Recovery (that means broken Recovery screen which asks you to connect Kies - another useless software at the moment for Note 4)
- Very slow to start Download mode with ddi: failed
- Kies failed to connect or recovery
- SmartSwitch failed to connect or recovery
- ODIN failed to flash TWRP
- ODIN failed to flash whatever firmware I could have found on Earth (4.4.4, 5.0.1, and 6.0.1 and many others I could find for Australia, Singapore, India) including all possible REPAIR firmware
- Unable to do the recovery with FonePaw (although I could do with it the first time and recovered my Recovery mode then it failed all other times)
- Unable to flash with SamsungToolPro Z3X software.
- Stuck logo Samsung at the start after the successful recovery back to stock ROM.
- Quickly came back to the same ddi:failed problem after installing the MM 601 stock ROM.
OMG, look back these fool things I am wondering why SAMSUNG still is my phone. LOL.:laugh:
Now make it short for all of you, I did feel hopeless at some points after reading hundreds of different online topics and solutions which none could fix my issue, yeah, including several downloaded firmware and software tools that human made on earth for Samsung mobile, also I paid some $ for one downloaded firmware named REPAIR 6.0.1 which was useless for me at the end.
BTW, my simple advice is: Do not give up when you try to believe that you can get the phone working back as long as it still can come to Download Mode (and even not be able to come to Recovery mode).
What I did at the last action (surely you can try everything as what I tried above which ended up nothing worked) - please don't claim me if it might not work for you, or you damage your phone completely by heating it up.
1. Heat up the phone by a hair dryer at close distance and high speed/very hot level in about 10 minutes, the phone was hot like a baked cake that you can’t hold in hands. (don’t heat the front LCD panel to avoid a damaged LCD, just heat the back opened panel)
2. Leave 10 minutes to cool down but still feel warm enough in hands.
3. Restart in Download Mode (you should see it comes up VERY VERY FAST in ODIN mode on the phone and without errors, compared with the very slow start and load of errors in Download Mode before heating up the phone).
4. Connect to ODIN (I used ODIN 3.11.1 but I truly believe others would work)
Laptop USB 3.0 and a good cable (not sure original cable or not but I don’t think it is the original one, and I believe that any good cable that can show the phone in ODIN at first plug would work). Also I do think that USB port 3.0 or 2.0 would not make difference in my case.
1st attempt: Install REPAIR 4.4.4 kitkat firmware: FAILED at last step
2nd attempt: Install REPAIR 5.01 India firmware: FAILED at the last step
3rd attempt: Install REPAIR 6.0.1 firmware (bought online): FAILED at the last step
<ID:0/006> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> persist.img.ext4
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Write)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
5. Do the flash with the single MM 6.0.1 XXXXX. TAR.MD5 stock firmware
FINALLY I got it worked with
N910GDTS1DPD2_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar.md5
(I believe that other stock MM 6 firmware would work but I did not download the others)
<ID:0/006> 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/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Then got stuck at Samsung logo.
Get back to Recovery => Wipe Cache => Wipe Data/Reset
Booted normal to stock ROM.
Then failed again quickly with ddi: mmc failed.
Tried to restart and get back to the working phone, then quickly install WakeLock V3. Nothing wrong after that.
Now working flawless, fast, and smooth again.
Installed various software to run as usual without problems.
Installed CM Launcher and runs fast.
Passed well all Antutu Benchmark tests included Stress Test.
DONE.
* There is still one issue: it will be hard to re-start the phone IF I turn off the phone from the software, I have to leave battery out few minutes and try to start it a few times (even if it may restart twice with a completly black screen) before getting back to normal working phone. In fact this symptom happened already about 1 year ago since the time I updated to MM firmware, so it may be the special gift from Samsung for all Note 4 users. I may try to downgrade to Kitkat or Lollipop and see how it goes.
Not sure why and hope someone can help to answer this.

Dude it seems like your motherboard has the dreaded emmc issue but you got very lucky through sheer persistence.
I think your best bet is to buy a new motherboard from Ali baba as many others have done because it's unlikely things will improve from here.

Apex Predator said:
Dude it seems like your motherboard has the dreaded emmc issue but you got very lucky through sheer persistence.
I think your best bet is to buy a new motherboard from Ali baba as many others have done because it's unlikely things will improve from here.
Click to expand...
Click to collapse
No worries because most important files are in SD card and get backup frequently. I will keep using and watching it first until it is gone then I will buy a different phone.
Today it runs very fast and smooth without any frozen or restart by itself.
I already did a full test with Antutu Benchmark and full Stress Test via Antutu, both turned out excellent as it was a new phone more than 2 years before.

Update: After a few days, the phone runs constantly well with the same simple setup: MM Stock ROM + all updates to all types of bloatwares in the stock rom + WAKELOCK runs at Partial setup.
I do have both normal Samsung genuine battery and a 10,000mAh Zerolemon battery, both of them are running well with the above setup.

Here is a 100% hardware fix for this issue that anyone can do with no tools or specia
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI