Hi!
!Total Newbie Alert!
I have a Galaxy S5 Active, SM-G870W. It was with Bell, but I unlocked and have been using another provider for some time now. I recently needed to install an app that needs root access, and figured I would be able to do the same.
In the distant past I had rooted some ancient android devices, so I read a bunch of pages, and feeling far too confident I pulled the trigger and tried to root my phone using the CF-Auto-Root tool from the firmware dot mobi website.
I entered SM-G870W, selected the only device option, hit Submit, Selected Android 6.0.1 (Build MMB29M.G870WVLU1CPF6), and continued to download a file:
cfar_samsung_sm-g870w_kltevlactive_mmb29m.g870wvlu1cpf6_t0.zip
I Extracted then launched the root.bat batch file, Odin Launched (Ver 3.12), I pick the AP as specified, and I get the following:
<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> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone stays at "Downloading... Do not turn off target!!"
I pulled the battery and rebooted into download mode again (Vol Down/Home/Power) and retried with the same file, and the same results.
I also tried powering up in recovery (Vol Up/Home/Power), but I get a message
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
Click to expand...
Click to collapse
At this point I am trying to get my device at least usable, I can restart in download mode no issue, but even after regenerating and redownloading, I am not able to get past this error.
I spent the last 6 or so hours going over posts here and elsewhere, with no luck, I tried Kies (Version 3.2.16084_2) and it says "The connected device is not supported by Kies 3" and the link to view supported devices on Samsungs site does not lead to any information. I also read somewhere that you can't root Android 6 images, but that post was 2014, and I found contradicting information elsewhere.
I would appreciate help on where to go from here, my priority is getting the phone working, rooted or not.
Thanks in advance!
Related
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> 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)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> 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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> 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)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> 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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
hello. have you tried another version of odin? im sure someone can help you revive your phone
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
hypnodaz said:
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
Click to expand...
Click to collapse
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
Have you tried using Odin V3.09 to flash 4.4?
hey_joe said:
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
Click to expand...
Click to collapse
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Mamba25 said:
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Click to expand...
Click to collapse
Don't follow that one.
Go here and download the right file for your phone's model, put phone in download mode and flash using odin in ap/pda slot.
Btw, have you tried flashing 4.4 using odin v3.09?
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
hypnodaz said:
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
Click to expand...
Click to collapse
I don't think this is the case because when I first tried flashing from 4.3 to 4.4.2 it tried for a few seconds then failed and been stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ despite resetting Odin and going back into download mode, tried reflashing but keep getting the 'FAIL' (logs posted in original first post).
Is there any reason why my phone is being detected as 'Samsung GT-S5690' in MobileGo? I'm thinking if Kies could detect it as the Note 3 again my problems would be solved.
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Mamba25 said:
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Click to expand...
Click to collapse
No it's not.
Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> 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)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> 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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
looks like u r trying to flash 4.3 & 4.4 one after one, now dont try 4.3 at all, make sure kies is not running in baground, disable antivirus if any.
I had the the same issue with kies myself, tried every trick in the book before I tried the method I mention above.. maybe it's an issue with the phone itself, or a certain batch of phones?
Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
...
Click to expand...
Click to collapse
The writing of stock 4.3 fails since your bootloader was updated by your failed attempt. You will probably never be able to write a 4.3 stock image.
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
xclub_101 said:
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
Click to expand...
Click to collapse
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
There is AP in 3.09 in place of PDA.
Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
xclub_101 said:
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
Click to expand...
Click to collapse
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
madsus said:
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
Click to expand...
Click to collapse
I've taken the phone to a repair shop recommended by Samsung themselves, they've had it a week now and I rang yesterday and they said it is the first Hong Kong Note 3 they've received and are waiting to hear from Samsung as to how to repair it. BIG YAWN!
Will keep you posted - miss my phone
Note 3 SM-N9005 firmware upgarade issue
Hi , i am having the same problem in my Note 3 i upgraded phronesis rom and after the phone was not detected in computer. so tried to flash custom kitkat rom again then it got disconnected and then showing error as firmware upgrade issue,
tried to download firmware and update by Odin, tired cmw recovery and tried many firmwares, Odin shows Failure and Kies dosent shown code or phone in emergency recovery , all ways failed, is it possible to make the phone work normal.
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.
I have been searching threads for 6 hours, but haven't found anything conclusive.
I rooted my phone a while back, but today I decided to install a new custom ROM. I backed up the ROM to my external SD and installed the new one through safestrap. However, when I tried to reboot, I just got stuck on a screen that says samsung and has an open lock.
I am able to get into download mode, but not into recovery. After I boot into download mode, it says write protection:enabled (not sure that is normal, but I thought I would mention it). I open up Odin and the drivers seem to load fine. I have tried a a few versions of ODIN and two different Stock ROMs, but it fails every time. On my phone, after it fails, I get a message that says SW Rev. Check Fail: fused 2, binary: 1.
In ODIN, I get the following:
<ID:0/003> Added!!
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? I'm getting kind of desperate.
Have you tried another USB cable?.
I have actually. The original cable and just another one I had. Also, tried it on 3 computers.
Should I be loading a PIT file? some places say to do it and others say not to.
marcymtz92 said:
Should I be loading a PIT file? some places say to do it and others say not to.
Click to expand...
Click to collapse
The problem is you're trying to flash mdl firmware and you're not on that version. It looks like you're on mf3. There is no Odin flashable mf3 firmware so I'd suggest you flash the nb1 tar file. See the general forum for the file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
You are freaking amazing. That file totally worked. Thanks so much.
marcymtz92 said:
You are freaking amazing. That file totally worked. Thanks so much.
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app
I, along with several other users, have been getting a SHA256 is invalid error when trying to do the root from this thread:
http://forum.xda-developers.com/att-note-7/how-to/root-complete-stock-ph1-setup-root-t3463187
The fail comes in at the step when trying to flash the Sprint userdebug firmware in the AP slot.
I tried using different computers, cables, and ODIN and all that happened was I managed to brick my phone (but then fix it by flashing the stock ATT files thankfully)
One thing I noticed is that the firmware is downloaded as an MD5 instead of a TAR file, but I assume this has no bearing on the error.
Does anyone have any solution to this problem? It seems there are many people who have been able to acquire root, so there must be some solution available.
Any help is greatly appreciated as root access will be incredibly beneficial!
This is what the log looks like in the Odin version provided in the post:
<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.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Luigiman765 said:
I, along with several other users, have been getting a SHA256 is invalid error when trying to do the root from this thread:
http://forum.xda-developers.com/att-note-7/how-to/root-complete-stock-ph1-setup-root-t3463187
The fail comes in at the step when trying to flash the Sprint userdebug firmware in the AP slot.
I tried using different computers, cables, and ODIN and all that happened was I managed to brick my phone (but then fix it by flashing the stock ATT files thankfully)
One thing I noticed is that the firmware is downloaded as an MD5 instead of a TAR file, but I assume this has no bearing on the error.
Does anyone have any solution to this problem? It seems there are many people who have been able to acquire root, so there must be some solution available.
Any help is greatly appreciated as root access will be incredibly beneficial!
This is what the log looks like in the Odin version provided in the post:
<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.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You have the wrong version of Odin. I replied to your comment in another thread with the link. But it's someone who uploaded a copy of the fixed Odin from one of the root threads.
It was post #168 or #186. I'm away from that tab now.
I know you have the latest version, but you need the other version that's cooked to work with this spirit root package
grmcrkrs said:
You have the wrong version of Odin. I replied to your comment in another thread with the link. But it's someone who uploaded a copy of the fixed Odin from one of the root threads.
It was post #168 or #186. I'm away from that tab now.
I know you have the latest version, but you need the other version that's cooked to work with this spirit root package
Click to expand...
Click to collapse
Well, this did in fact move me past the SHA256 Invalid error but I was presented with a new error:
<ID:0/005> 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/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: aboot
Then, my phone bricked. Again. Luckily I already fixed this once and I fixed it again.
At this point I assume I just have some unrootable version of the phone and can live with it I suppose.
Bricking a phone this expensive isn't fun despite the fact that I have fixed it.
they slipped a new bootloader in with the "green battery" icon update. this new updated bootloader checks and will not allow a downgrade in version. root method #patched
i took the update on my defective device, just to test this. you are lucky, i am unable to get my device back to ATT stock, i am bricked.
cordell12 said:
they slipped a new bootloader in with the "green battery" icon update. this new updated bootloader checks and will not allow a downgrade in version. root method #patched
i took the update on my defective device, just to test this. you are lucky, i am unable to get my device back to ATT stock, i am bricked.
Click to expand...
Click to collapse
Guess I'm bricked too.. same issues.. if a new update comes out, will that get loaded and allow the device to start working again? I thought bricked was the device not even turning on.
Mine turns on and everything works find except i have no cell reception at all - circle w/line through it. can seem to get it rooted and this all happened just after the last update but not sure if it was related. Samsung thinks I rooted the phone but I've never done that in my life so not I have no choice but to try in order to get a working phone back... but that doesn't seem to be working either.. ugh. $800 for a phone that worked for 8 months...
Same as you. Everything works but cell service
MellowJoe said:
Guess I'm bricked too.. same issues.. if a new update comes out, will that get loaded and allow the device to start working again? I thought bricked was the device not even turning on.
Mine turns on and everything works find except i have no cell reception at all - circle w/line through it. can seem to get it rooted and this all happened just after the last update but not sure if it was related. Samsung thinks I rooted the phone but I've never done that in my life so not I have no choice but to try in order to get a working phone back... but that doesn't seem to be working either.. ugh. $800 for a phone that worked for 8 months...
Click to expand...
Click to collapse
hAVE YOU BEEN ABLE TO DO ANYTHING
Luigiman765 said:
Well, this did in fact move me past the SHA256 Invalid error but I was presented with a new error:
<ID:0/005> 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/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: aboot
Then, my phone bricked. Again. Luckily I already fixed this once and I fixed it again.
At this point I assume I just have some unrootable version of the phone and can live with it I suppose.
Bricking a phone this expensive isn't fun despite the fact that I have fixed it.
Click to expand...
Click to collapse
But see, it failed at the aboot part.
Try flashing the combination file for your current bootloader version. Once that is installed try again.
Combination Files always ship with the revision 1 aboot for that binary version. And they are signed. So you can downgrade to a revision A aboot file by using the Combination files.
This might help. PrinceComsy's version of ODIN or Jester's version of ODIN are the ones usually used for AT&T devices with checksum errors.
(i.e When you see a build like 3CQB2 or 5BPK1 or something like that. The first digit on the build is the bootloader revision or binary version of the firmware. That second digit is the aboot revision. The last 3 digits are the time the build was created and its revision number.
When I had my AT&T Note 5, I had updated to Binary 3 aka Marshmallow. I couldn't go back to the binary 2, LP 5.1.1 builds to root anymore. Using the combination file for binary 3 I was able to flash a binary 2 AP file overtop of the rest of the binary 3 combination firmware. And it booted up just fine! I was able to downgrade and root because of the combination file.
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