<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1BOC4_G900VVZW1BOC4_CL3846539_QB4392815_REV00_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> 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)
I was trying to root the s5 by downgrading but ran into a slight problem. Everytime I start the phone it boots for 5 mins, then goes into stock recovery. I have tried multiple different stock roms and none seem to work. Any help would be awesome.
What version were you downgrading from?
I believe BOG5
ldeveraux said:
What version were you downgrading from?
Click to expand...
Click to collapse
BOG5 I believe. At first it was telling me that when I ever I tried to root it, it would fail and then on the screen this would pop up: SW Rev Check Fail : Fused 2 Binary 1. Now whenever I start up the phone it tells me that the update failed and I need to use verizon software repair assistant to fix it.
calebp123 said:
BOG5 I believe. At first it was telling me that when I ever I tried to root it, it would fail and then on the screen this would pop up: SW Rev Check Fail : Fused 2 Binary 1. Now whenever I start up the phone it tells me that the update failed and I need to use verizon software repair assistant to fix it.
Click to expand...
Click to collapse
Anything OE1 or newer (yours is newer) can't be downgraded
ldeveraux said:
Anything OE1 or newer (yours is newer) can't be downgraded
Click to expand...
Click to collapse
Is there a link to the original verizon firmware or what should I do?
calebp123 said:
Is there a link to the original verizon firmware or what should I do?
Click to expand...
Click to collapse
You can just flash your phone back with stock firmware you were previously on. You can search the development thread for it. Unless you took a backup before doing all this, that's what you would have done if you read first..
Related
(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
I'm trying to apply the correct firmware for my region UK and carrier which is EE but i can't seem to do this since it keeps failing on me when i start the process. This is the output from the logs.
Code:
<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/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Just some background info as to why and what i've done previously.
The problem is i can't update the software since it keeps on saying processing failed. After looking into this it may be linked to region of the device since the baseband versionis I9505XXUGNK4 and the CSC part is not a UK code which is why i'm guessing the phone can't be updated also on the phone screen it shows the following error message at the point at which it fails secure check fail sbl1
Also i used kingoroot to root the device and i have a superuser app install as well before using Odin but surely this can't be an issue can it?
Kingroot caused various issues before.
The thing is that Odin is very picky.
You should try other USB ports, preferably the ones in the back of the pc.
You should also try different cables, preferably the original one.
Also, different Odin and Windows versions.
GDReaper said:
Kingroot caused various issues before.
...
Click to expand...
Click to collapse
He mentions KingoRoot, not KingRoot.
tunds said:
...
Also i used kingoroot to root the device
...
Click to expand...
Click to collapse
Sent from my ASUS_Z00AD
I thought they are the same, just that people misspell the name >.<
ok let`s start from the start, i tried to root my note 3 sm-n9005 and failed to succeed.
i used the cf auto root guide, odin said success but my phone failed to boot and went straight to recovery mode.
then, i tried using odin 3.07/09/11/185 to rewrite into the stock rom, but odins says FAIL and gives nothing in return.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBPB1_N9005EVRGBPB1_N9005XXUGBOJ1_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> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
i just want get my phone back with android that above 4.4
please help :crying:
Looks like the ROM you are trying to flash is not made for your phone or the ROM is older than the ROM currently installed on the phone.
Are you using the original Samsung USB cable? Tried different USB cables and ports?
For Root note 3 use Towelroot by Chainfire.
Sent from my Limited Edition Note 3 LTE using Super Tapatalk
Download Official 5.0 ROM from Sammobile and flash it in Odin, after it try to root phone...
In dialog this looks like firmware file is damaged
The firmware doesn't look damaged, the firmware you are trying to flash has a bootloader that is older than the bootloader in the phone.
isn't chainfire's root method called cfautoroot?
download one more time...
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
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.