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.
Related
can someone please help me , i tryed to put a new rom on my phone and ended up with it giving me and error saying firmware upgrade encountered an issue please select recovery mode in kies, ive tryed to restore in kies but when i do it ends up saying device not found and failing, i can still get onto download mode
ive tryed diffrent odins and same error all the time the last thing i tryed was full wipe and rebuild still no joy
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Help is simple you are in the wrong forum this is I9300 .
Use the report button for moving the post .
Based on your previous posts you are either not following the instructions or need a service centre repair .
jje
SAMGS4 said:
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
Click to expand...
Click to collapse
Mh, is this normal for ODIN, having a single PDA file given?
@ SAMGS4: What exactly did you do? For me it looks like you put the same file in all file selection lines.
Do you still have access to phone's UI and can check the complete device properties?
I know this is the wrong device forum but if a mod moves this topic to the proper location, the replies got moved also.
someone please help
HSishi said:
Mh, is this normal for ODIN, having a single PDA file given?
@ SAMGS4: What exactly did you do? For me it looks like you put the same file in all file selection lines.
Do you still have access to phone's UI and can check the complete device properties?
I know this is the wrong device forum but if a mod moves this topic to the proper location, the replies got moved also.
Click to expand...
Click to collapse
thanks and ive just reported the post to be moved, and also i have no access to the phone, i can get it on the download mode and when it says about firmware upgrade kies update etc
Well ... there might be another reason why you can't flash the wanted file - the DL is corrupt. But ODIN checked the md5 hash and the file passed the test.
Did you try to flash another, earlier leaked, ROM for your phone?
Does the ROM match to your country / provider code? Maybe the ROM you try to flash doesn't match exactly to the phone you have; there are various SGS4 models.
someone please help
HSishi said:
Well ... there might be another reason why you can't flash the wanted file - the DL is corrupt. But ODIN checked the md5 hash and the file passed the test.
Did you try to flash another, earlier leaked, ROM for your phone?
Does the ROM match to your country / provider code? Maybe the ROM you try to flash doesn't match exactly to the phone you have; there are various SGS4 models.
Click to expand...
Click to collapse
just tryed a new rom and pit file and heres the results
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_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> 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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
my phone was on the (3g) three network uk its a gt-i9505 if someone could direct me to a rom and pit file for my phone i could try would be very much appreciated
heres my LAST ODIN FLASH TRY seems to for got bit further then last time and on my phone i got a little bit of a blue loading bar then it failed
SAMGS4 said:
my phone was on the (3g) three network uk its a gt-i9505 if someone could direct me to a rom and pit file for my phone i could try would be very much appreciated
heres my LAST ODIN FLASH TRY seems to for got bit further then last time and on my phone i got a little bit of a blue loading bar then it failed
Click to expand...
Click to collapse
While flashing using odin make sure no kies programme are running in the background
U can try different cable / usb ports etc will work and try using without pit,
U should use pit file as a last option for now u try without that and do as above will work
.
I Just tried a diffrent usb port and didnt use the pit file and it got a bit futher then first time but failed again here is the results <ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
someone please help
i just tried diffrent usb post and made sure kies or no firewall was on , didnt use the pit file like you said and phone got bit futher then first time but still failed here the results
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
U
SAMGS4 said:
i just tried diffrent usb post and made sure kies or no firewall was on , didnt use the pit file like you said and phone got bit futher then first time but still failed here the results
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img.ext4
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!
Added!!
Click to expand...
Click to collapse
Did u close all the kies programme from the background that must be the issue
Or uninstall kies and try
There should be 3 four kies file running in the background close all from task manager try restarting pc and try
someone please help
just uninstalled kies and tryed same as before
someone please help
i have a laptop with windows xp on it should i try on this??
OTE=SAMGS4;44354942]i have a laptop with windows xp on it should i try on this??[/QUOTE]
I'd give it a try. Update the drivers before you attempt it. I'm on three as well and have flashed the same firmware without problems. Have you tried flashing a recovery and wiping the phone. Internal SD etc? Wouldn't do it any harm
someone please help
symondo12 said:
OTE=SAMGS4;44354942]i have a laptop with windows xp on it should i try on this??
Click to expand...
Click to collapse
I'd give it a try. Update the drivers before you attempt it. I'm on three as well and have flashed the same firmware without problems. Have you tried flashing a recovery and wiping the phone. Internal SD etc? Wouldn't do it any harm[/QUOTE]
hi could you please give me a link to stock rom for three please as cant find one and what recovery would i flash?? thanks?
Mh, can you get into Recovery mode? If not, flash an alternate Recovery mod first. Try PhilZ Touch Recovery. It's being flashed within DL mode, fill only PDA field.
Ah, I didn't notice yet ... you use ODIN 3.04. That's an outdated version; maybe 3.04 can't handle an I9505.
Most current version is 3.07, get it here. In this post it's said ODIN 1.85 can already deal with an I9595; try this too.
Does ODIN run with Admin rights? Maybe there's a problem with your Windows UAC.
//HSishi
http://forum.xda-developers.com/showthread.php?t=2281367
That's the link for philz recovery. Download the latest .tar and flash in O.
Boot into recovery and wipe everything including the internal SD. Make sure you back up.
By the looks of it you are flashing the latest three firmware. MEA H3G.
I'd download the firmware again. You can get it from Sammobile.com. you'll need to register an account. Think its labelled as Hutchisons 3G
someone please help
i just tryed to flash PhilZ Touch Recovery and it failed, also ive tried all the odins and the one that seems to get me the furthest is the 3.04
someone please help
anymore ideas?? pls:crying:
Have you tried another PC, one with Win 7 or 8 on it?It doesn't look like a partition problem, it seems to get further through each time but keeps failing. Might be a problem with your PC...
Oh, and I use ODIN 3.04 to flash too...
(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
<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..
this model seems difficult (gt-i9506)
i tried to root it via towelroot, then kingoroot, these failed but then now the reboot is stuck on "firmware upgrade encountered an issue"
ive tried Kies firmware recovery but the download fails after 80%,
ive tried the sammobile download the ROM this too fails, network drops out tried this 3 times
i want to try Kies emergency recovery but cant find any recovery code
im stuck i dont know what to do now been researching for 4 hours cant find solution :crying:
could anyone please help?? am going crazy over this spent 2 days researching and finding nothing
Download a complete stock rom and flash it with ODIN. You have to uninstall KIES beforehand (they are conflicting).
thanks for reply...
i took kies off and this is what Odin is giving me...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMHF_I9506VAUAMH3_I9506XXUAMHD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the device says this.....
SW REV CHECK FAIL: [aboot]Fused 1 > Binary0
does this highlight anything that could be going wrong?
Not sure... but looks like the rom is not for that device. Are you sure you have a i9506?
on samsmobile GT-I9506/VAU/ Roms (i cant post link)
well the first ROM was 4.2 android (bottom of ROM list), so then tried 4.4 (top of ROM list) android it failed again but with different Odin errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNJ1_I9506VAUCNJ1_I9506XXUCNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
can anyone see the fault here...?? no error came up on the device, only on Odin this time
Did you restart after KIES de-installation? Was USB driver successfully missing (so you had to install one manually for ODIN)? If not, you probably still have drivers/files running from KIES.
Otherwise, try a different computer to double check its not the system.
If you originally updated to Android 4.4.x or later on this device, you cannot install 4.3.x or lower as Knox within the bootloader will actively prevent Odin from functioning. As to Odin, make sure you're using the original cable, are not using a hub, have Kies disabled or uninstalled, and use a different USB port. Odin sometimes is picky about the ports it uses.
If you can get the ROM issue resolved, use CF-Autoroot to root, keeping in mind that you will trip the Knox flag in doing so. Towelroot and other one-click root methods don't work on your device.
FIXED IT!!!!!!! :laugh::silly::good::cyclops:
Moved all operations to a different PC running XP with no kies on it
The error still occurred "write fail"
So instead i tried Odin 3.09 instead of 3.07 but most of all i changed usb cables, found an original cable off my mates Nokia
then boom!!! she starting writing!!!
Thankyou so much you legends, you are now my best friends forever!!!
Strangely the new flash, all my old previous data & apps are still on there??? somehow the network is not locked either which i was fearing being a vodafone ROM
still want to root it though
Flashing a ROM through Odin doesn't wipe the data partition, which is why your apps are untouched.
bear with me im new to this .
I have a s5 with 5.0 on it and i just want to use foxfi for hotspot again. i read that i have to go back to 4.4 to do so.
i went to sam mobile, registered and waited 3 hours for the file that was for 4.4 to load. then unzipped it. downloaded odin. installed odin . went into developer mode on phone. usb installer was selected if i recall then. powered down phone. held 3 buttons for download mode with phone disconnected. started odin. selected the tar. or md5 file that was decompressed then connected phone and selected start. i keep failing with this in the message
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
additional info on the phone
sm-g900v
android version 5.0
kernel 3.4.0 fri jul 31 2015
dont care about knox or warrenty related stuff just want to have wifi hotspot to work
G900V.....isn't that the Verizon variant?
If it is, it may be that (like with AT&T) they've locked your bootloader down and downgrading isn't possible.....
http://i.imgur.com/rVnFwJM.jpg
Is there a way to verfiy unlocked or not?
Just been reading up on Verizon's behaviour.........
It is standard practice for them to provide phones with locked bootloaders.......
If your device is Verizon branded (has all the Verizon bloatware apps), it's locked down........
http://i.imgur.com/rVnFwJM.jpg
Can it be unlocked?
Apparently it's all done through some sort of encryption which nobody has found a way around.....and you've got more chance of being able to walk to the Moon than you have of getting either AT&T or Verizon to release the decryption 'key'..........they're big players who want their own way and who have the 'muscle' to get it......
http://i.imgur.com/rVnFwJM.jpg