Gs5 verizon soft bricked! Urgent! - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Hi,
I have a SAMSUNG GALAXY S5 VERIZON and I treid to restore it to its stock rom using ODIN.
I have used every version of odin and I keep getting the same message:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANCG_G900VVZW1ANCG_G900VVRU1ANCG_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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried multiple PC's multiple cables and multiple STOCK MD5 files.
I am Able to get to download mode and recovery boot.
I have tried almost every troubleshoot posted online so far.
On download screen I get SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1
URGENTLY NEED HELP!
Thanks guys

Need to know what build you were on before you attempted all of this. If you were on BOE1 or BOG5, you cannot ODIN back to a previous build. You will have to ODIN the same build you were on when you started this.

Most likely I had one of the two. I'll try to odin to same build.
My phone was on Android 5.1.1 stock.

YES! It worked. Thank you so much! I really appreciate taking the time to help me. Good to know people are still willing to help out!

Hi I am having the same problem but I cannot find the stock file for 5.1 or 5.0.1. or whatever the newest version is if anyone could help out

Dark Karas said:
Hi I am having the same problem but I cannot find the stock file for 5.1 or 5.0.1. or whatever the newest version is if anyone could help out
Click to expand...
Click to collapse
Here you go. This is factory stock, it will locked your bootloader.
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527

I am having the same issue as the OP but mine is 5.0 and was BOG5. Can you please help me fix it or explain to me how I can? I am a noobie at all of this.

Hollieanne said:
I am having the same issue as the OP but mine is 5.0 and was BOG5. Can you please help me fix it or explain to me how I can? I am a noobie at all of this.
Click to expand...
Click to collapse
If you're having the same problem, the solution is the same: Use Odin to flash the BOG5 system restore image that was linked in the post above yours.

Related

[q] need help with my s4 gt-i9505

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...

[Q] How to root after the latest update ?

Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration

failed root n9005

Hye all....
I need help in rooting n9005.....i did it almost 10 time,but keep failed msg on odin.....i also try use cf auto root....same thing happen......my detail about my device was in the image.....hope u guys can help me......
Thanks in advance
Need more info.
You need specific cf-auto root: CF-Auto-Root-hlte-hltexx-smn9005
What Odin version did you use? 3.07 or 3.09, or?
What did you check in Odin?
Have you tried this guide? http://forum.xda-developers.com/showthread.php?t=2704363 or what were your steps?
I use odin 3 v185 and odin 3 v3.09......
The file is the right one already for n9005
As i don't know the fail message suggest download again ,
Here is the log message from odin....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
poje84 said:
Hye all....
I need help in rooting n9005.....i did it almost 10 time,but keep failed msg on odin.....i also try use cf auto root....same thing happen......my detail about my device was in the image.....hope u guys can help me......
Thanks in advance
Click to expand...
Click to collapse
Your file could be broken.You should download again and do the things with order.It is really simple actually.
And next time someone asks you to post the files or info, do it. Just saying you have the right ones doesn't mean you do. I thought I had the right files for something just the other day (and I've done this for a long time)... but turns out I didn't.
Good luck with it then.
cyberboob said:
And next time someone asks you to post the files or info, do it. Just saying you have the right ones doesn't mean you do. I thought I had the right files for something just the other day (and I've done this for a long time)... but turns out I didn't.
Good luck with it then.
Click to expand...
Click to collapse
Sorry bro,i was downloading 3 cf root file already,all same happen.....i will post the file here later for u to check it.....coz now im not on pc,have work outation....maybe in 24 hour i will post the file here.....hope u can help me

[Q] unbrick error with odin

Hello guys,
Today I tried to unbrick my cm11. I want back official stock rom but I have some troubles with ODIN.
I tried each version of ODIN and still I fail to pass.
ODIN error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505OXXGNG2_I9505XXUGNG8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Click to expand...
Click to collapse
I tried with a PIT file and without. still didn't succeed
PaLiT said:
Hello guys,
Today I tried to unbrick my cm11. I want back official stock rom but I have some troubles with ODIN.
I tried each version of ODIN and still I fail to pass.
ODIN error
I tried with a PIT file and without. still didn't succeed
Click to expand...
Click to collapse
Hi,
.pit might be broken (I guess). Grab a copy of a good .pit file and flash it together with your firmware. If still doesn't, your device might be Hard Bricked.
krasCGQ said:
Hi,
.pit might be broken (I guess). Grab a copy of a good .pit file and flash it together with your firmware. If still doesn't, your device might be Hard Bricked.
Click to expand...
Click to collapse
You need to calm down with saying it is hard bricked. This is not the first time I see you post this warning about hard brick. I see you are a new member and it's good that you try to help people. But it is almost impossible to hard brick our device.
Try a different usb port, diferent cable etc.
the problem has been solved guys thanks!

Help with downgrading to android 4.4.4 on SM-G900V?

To start out, I will say that I am not the best with this kind of stuff and do not know THAT much about rooting/flashing ROMs and what not. I have read many posts about how to go about doing this and here is what I tried. I downloaded Odin 3.11.1 and the most recent Android 4.4.4 version (USA) from SamMobile. I turned my phone off and put it into download mode. After this, I started Odin, and pressed VOL up on my device to continue. Odin said "Added". I selected the file to flash in the AP section (G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar.md5) and hit start. This is what came up in Odin:
<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> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried this many times with all the USB slots on my PC and with 3 different cords. I have also tried different versions of Odin. I'm not sure if any of that would change anything, like I said, I do not really know what I am doing. Am I doing something wrong here? Any help is greatly appreciated! Thanks, Hunter.
geezlaweezuz said:
I have tried this many times with all the USB slots on my PC and with 3 different cords. I have also tried different versions of Odin. I'm not sure if any of that would change anything, like I said, I do not really know what I am doing. Am I doing something wrong here? Any help is greatly appreciated! Thanks, Hunter.
Click to expand...
Click to collapse
You cannot downgrade from BOE1, BOG5, BOK3, BPB1, DPD1, or DPF4. As of BOE1, the bootloader was fused to prevent downgrading.
If you do have a downgrade-able firmware still installed on your phone, then the most likely remaining problem is that the file you're trying to flash is corrupt or incomplete: compare the md5 hash
You can do a partial downgrade to kk 4.4.2 you will still have pb1 bootloader but it does work in s5 verizon general there is a thread by brens123 called I booted into ncg on pb1 bootloader you might be able to subsitute the nk2 firmware instead of ncg firmware using his guide

Categories

Resources