Related
Hi guys,
My friend flashed my phone and there was a problem with the backup of the original firmware (for some reason) so we did not do it.
Unfortunately days after updating (and only days after I got the phone) there was a hardware problem in the form of a pink discolouring (leak?) in the screen which has spread from a tiny pink dot to the majority of the lower half of the screen. Due to this I need to return the phone for repair hence the need to return it back to factory firmware.
I have tried flashing to older firmware in order to upgrade my phone with Kies (and bricked my phone in the process forcing me to make a jig ) however even after flashing to 2.1 Update 1 and trying to trick Kies with the patcher there does not seem to be an update available from Vodafone Australia for the device.
Could a kind fellow aussie please help me out by uploading a backup of the original Vodafone Australia Samsung Galaxy S firmware, I assure you that your kind deed will not go unrewarded.
Thank you!
I9000DTJG4|2.1|2010 July|Download
I9000DTJP5|2.2|2010 November|Download
Vodafone FW: HVJH1 – http://www.multiupload.com/U7OG0XQYJF
Vodafone JH1 CSC only: http://www.multiupload.com/ZJ6TMSF0H7
password: asgardxda
Wow, I feel like such a noob.
After spending so much time trying to find this firmware I was convinced that it was not out there but now I can see where you have found it.
Thank you so much! As promised I will have to reward you, feel free to PM me your PayPal e-mail address so that I can give you a small token of my appreciation (Or to a cause of your choosing if you prefer.
Thanks again.
Ran into some trouble with the following error.
E:Cant mout /dev/block/st110
(invalid argument)
E:copy_dbdata_media:cant mount DBDATA:
copy default media conent failed.
Had to flash JM9 with repartitioning then the Vodafone firmware with no repartitioning as shown in THIS THREAD.
Everything is good now, taking my phone in for warranty for an LCD issue tomorrow .
Let me know how it goes.
I'm on Virgin, but I just want to know if they do make any excuses (and they would love to) so that I could have a good comeback if my phone happened to have the same fate as yours.
Cheers
aditya104 said:
Vodafone FW: HVJH1 –
Vodafone JH1 CSC only:
password: asgardxda
Click to expand...
Click to collapse
Thanks heaps for this.. Do you happen to have the Froyo ROM HVJP3 ?
Forum_Member said:
Thank you so much! As promised I will have to reward you, feel free to PM me your PayPal e-mail address so that I can give you a small token of my appreciation (Or to a cause of your choosing if you prefer.
Thanks again.
Click to expand...
Click to collapse
Check your PM
Need some help, Trying this method to bring my firmware back to 2.1 AUS Voda but after first flashing JM9 with 512 pit, i try to flash ADD_VAU.tar but Odin keeps failing with the following message:
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VODA_AU_CSC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
fix it by running Odin in compatability for XP SP3 and also as an admin. should work
Check this out
Hey guys
I have got my SGS flashed to JM9, however when I flash it to JG4, it fails every time. Would someone be able to tell me exactly what file to load in what section in Odin to make sure I've done it all right?
Chris
Hi all. I am helping a friend restore his phone back to standard to send back to voda.
I am assuming when you say flash jm9 you are talking about this.
http://forum.xda-developers.com/showthread.php?t=802909
also once this is done how to you go about flashing the voda firmware? do you just flash the ADD_VAU.tar in odin? also if this is correct what section do you flash it in. PDA? Sorry bout this just not really sure.
was going to use
Vodafone FW: HVJH1
Do i need to use Vodafone JH1 CSC only as well?
Thanks in advance.
so i bricked my s4 and it is in download mode..
and found my stock rom. tried to flash it through ODIN
followed everything and it says FAIL.
idk what to do?
my phone basically says
Could not do normal boot (in red)
ODIN MODE (in red)
Product Name: SGH-1337
Current Binary: Samsung Official
System Status: Official
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224,1440] (in red)
SW REV. CHECK FAIL : fused : 2. Binary : 1 (in red)
h ttp://imgur(dot)com /vuf0KpF
Mk2/mf3 correct files?
mf3 rooted SHOstock 2.3
overuletill
Brooklynsour said:
Mk2/mf3 correct files?
mf3 rooted SHOstock 2.3
Click to expand...
Click to collapse
thank you for replying. im sorry im new at this and dont really know what youre saying.
i had a coworker try to install and flash a rom for me through mobile odin.. and idk what happened but he said its bricked on the download screen.
he told me to go home and download odin, and the stock rom and flash it, which im trying to do but it keeps failing.
it is 3 am so im going to go to sleep.
but please please someone help me. this is driving me nuts. i shouldve just let my phone the way it is but the dude at work seemed like he knew what he was doing
Try this:
BEWARE, THIS WILL SET YOUR PHONE BACK TO STOCK YOU WILL LOSE ALL OF YOUR DATA
So, I was in pretty much the same situation as you are in. Here's what I did
First, Download, and install Odin 1.85 (here's a direct Download Link):
https://www.google.com/url?sa=t&rct...soCwCQ&usg=AFQjCNF7sF0f2yJp0IxHp1ISlP2fzGKhtw
Extract it to a good location. Your Desktop will work
Next, Download the ORIGINAL Jellybean Stock Files from this thread:
http://forum.xda-developers.com/showthread.php?t=2504311
(here's a direct link: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE )
Then, extract the files that is within the MF3 Tars file into their own seperate file.
Open up Odin 1.85
Make sure that your Phone is connected (It will be under the ID:COM, section).
Click Bootloader, and browse to the file location in which you saved the MF3 Tar Files.
Select the file named: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
For PDA, use: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
*NOTE: IT MAY FREEZE UP A LITTLE BIT. BE PATIENT!!!!
For Phone, use: MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
For CSC, use: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
Then Click Start, and Hope/Pray.
Good Luck
cbjjensen said:
Then Click Start, and Hope/Pray.
Good Luck
Click to expand...
Click to collapse
omg this is actually working i think!!! omg will update!
thank you so much!
DoYouEvenTraps said:
omg this is actually working i think!!! omg will update!
thank you so much!
Click to expand...
Click to collapse
---------- Post added at 10:14 AM ---------- Previous post was at 09:43 AM ----------
Any update?
Could you please let everyone know whether you were able to get your phone back to normal?
tronac said:
Could you please let everyone know whether you were able to get your phone back to normal?
Click to expand...
Click to collapse
Had root and uninstalled it. Used the link and flashed through Odin and I'm perfectly stock again!! I can get OTA updates.
Keep those files in storage and they come in handy as long as it can boot to DL mode it can be restored
cbjjensen said:
BEWARE, THIS WILL SET YOUR PHONE BACK TO STOCK YOU WILL LOSE ALL OF YOUR DATA
So, I was in pretty much the same situation as you are in. Here's what I did
First, Download, and install Odin 1.85 (here's a direct Download Link):
https://www.google.com/url?sa=t&rct...soCwCQ&usg=AFQjCNF7sF0f2yJp0IxHp1ISlP2fzGKhtw
Extract it to a good location. Your Desktop will work
Next, Download the ORIGINAL Jellybean Stock Files from this thread:
http://forum.xda-developers.com/showthread.php?t=2504311
(here's a direct link: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE )
Then, extract the files that is within the MF3 Tars file into their own seperate file.
Open up Odin 1.85
Make sure that your Phone is connected (It will be under the ID:COM, section).
Click Bootloader, and browse to the file location in which you saved the MF3 Tar Files.
Select the file named: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
For PDA, use: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
*NOTE: IT MAY FREEZE UP A LITTLE BIT. BE PATIENT!!!!
For Phone, use: MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
For CSC, use: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
Then Click Start, and Hope/Pray.
Good Luck
Click to expand...
Click to collapse
If this worked for you, hit the thanks meter.
- Trying to get my rep up!
So rooting a phone is useless then..I mean if samsung does not recommend it.....I am not trolling BTW..just asking a question thats bugging me..do we or do we not.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
r1tesh said:
So rooting a phone is useless then..I mean if samsung does not recommend it.....I am not trolling BTW..just asking a question thats bugging me..do we or do we not.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Hmm.. I wouldn't call it useless. It all depends on what you're trying to get out of your phone. If your idea of the 'perfect phone' is one that requires root, and custom Roms, then rooting becomes less useful. Notice I said less useful, and not useless. There are still things that can be done on a rooted phone, that cannot be done on a stock, unrooted phone. There are some apps that require root. For example: diskdigger, titanium backup, and tons more - that's just what I can think of on the spot.
Rooting still has a purpose outside of having a custom ROM, but what you can do with it does become limited with MF3 and blocked bootloader.
Rooting is still useful. You gain more control over your phone. You can freeze applications and use xposed for customization. There are a lot of apps that require root that help so much with speed and performance
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I know it totally sucks..even with the 4.3 mk2 firmware cant root...there are ways but they suck..its so sad to see phat roms I cant rock cause I am restrited due to locked BL...?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Trying this method now, Odin seems to stop at <ID:0/003> SetupConnection.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_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..
EDIT: Problem solved. (Didn't reboot with VOL DOWN+Home+Power) Back to stock!
@cbjjensen great explanation man should post it on shocks post of the tar files... CBj.... Blue jackets?
Sorry for my useless answer I was asking if you used the right files on right firmware
mf3 rooted SHOstock
Can someone please re upload... The rar file keeps messing up..
cbjjensen said:
If this worked for you, hit the thanks meter.
- Trying to get my rep up!
Click to expand...
Click to collapse
Great way to Tell
cbjjensen said:
BEWARE, THIS WILL SET YOUR PHONE BACK TO STOCK YOU WILL LOSE ALL OF YOUR DATA
So, I was in pretty much the same situation as you are in. Here's what I did
First, Download, and install Odin 1.85 (here's a direct Download Link):
https://www.google.com/url?sa=t&rct...soCwCQ&usg=AFQjCNF7sF0f2yJp0IxHp1ISlP2fzGKhtw
Extract it to a good location. Your Desktop will work
Next, Download the ORIGINAL Jellybean Stock Files from this thread:
http://forum.xda-developers.com/showthread.php?t=2504311
(here's a direct link: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE )
Then, extract the files that is within the MF3 Tars file into their own seperate file.
Open up Odin 1.85
Make sure that your Phone is connected (It will be under the ID:COM, section).
Click Bootloader, and browse to the file location in which you saved the MF3 Tar Files.
Select the file named: BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
For PDA, use: PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
*NOTE: IT MAY FREEZE UP A LITTLE BIT. BE PATIENT!!!!
For Phone, use: MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
For CSC, use: CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5
Then Click Start, and Hope/Pray.
Good Luck
Click to expand...
Click to collapse
Hurrah Its works for like a Charm, should every one who had the problem, followed the instruction and will be bring a smile on your face
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...
I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:
K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...
amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.
You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers
Hi there,
This is what I get in Odin
<ID:0/003> 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/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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?
In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Are you trying to Root ur phone or Flash Stock ROM?
Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.
amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?
All,
I've spent the better part of the last two days trying with zero success to downgrade my Verizon Galaxy S4 SCH-I545 from 5.0.1 to 4.4.2. I've read dozens of pages on various forums, both on general instructions for the procedure as well as pages relating directly to the fault I'm seeing. In short, I get the Complete(Write) operation failed error in Odin. The reason I'm trying to do this is a general disappointment in Lollipop, it has slowed the phone down (I need to kill off all apps at least once a day just to keep performance up) and I've enjoyed none of the "benefits" of Lollipop on the phone. It's been so bad I've deliberately ignored all requests my Tab 4 makes to upgrade to Lollipop.
I've tried the firmware reflash using Odin 3.04 as well as 1.85. I've tried both versions on two different computers, one running Windows 7 Home, the other running XP. I've run them standard, and on Win7 as Administrator. Fresh reboots. The Win7 has Kies (not running) and the WinXP computer has never had Kies, just downloaded the current Samsung USB drivers. I've tried running two different firmwares downloaded from Sammobile, on each machine, with every combination I can think of. I'm using the factory USB cable plugged directly into the motherboard on each machine. I've varied the moment I plug the phone into the cable based on various recommendations, waiting until Odin is already running, or getting the phone in download mode first then plugging in, etc. I've also tried re-running the update again immediately on failure, and again after rebooting the phone back into Download mode, trying multiple times in a row without closing down Odin, and then alternately restarting everything after each failure. Basically I've tried pretty much everything I've read, and it feels like I'm following the rules of an old gypsy woman, if I update the phone at midnight while swinging a dead rooster over my head, standing on my left foot only, all will go ok. Only nothing goes ok.
This is the complete error I get in Odin 3.04:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The first four lines happen almost immediately. Then it seems to wait or hang for about 45 seconds (meanwhile one CPU maxes out), afterwards the rest of the lines pretty much spit out instantly. On the phone the display changes slightly, one little tick mark appears on the progress bar, then nothing else. The phone appears to be locked and needs a very long hold of the power button to shut off. These symptoms appear identical regardless of which computer I use, or which version of Odin I use, which makes me suspect the phone is the culprit rather than the software/hardware of either computer. I figure if I had, for example, a corrupted firmware file it would fail somewhere down the line in the install, or even after it's dumped the file to the phone.
One thing that worried me (and I NEVER found any mention of this in any directions) is the amount of available space on the phone. With the bloatware on the phone (7.07GB of "miscellaneous files"?!?) I only have 2.76GB free on the internal memory, and the firmware file is 2.4GB. I'm assuming that it all needs to copy to internal memory first. After my first failed attempts I checked space available and I had less than 2.4GB free. After clearing cache and a few apps I got it up to 2.76GB.
USB debugging is on, battery level is full or high on the phone, reactivation lock is off, the phone connects to either computer just fine and interfaces with Windows Explorer, I can see and access files on the phone via My Computer without any error.
I saw one page describing using Heimdall as a wholly different idea, it seemed MUCH more complex and my gut reaction is it looks like it would be easier to brick the phone. Is there some manual way I can dump the firmware to the phone and get it to read the file such that it doesn't require a computer?
Anything else to suggest? In general I still like the phone and don't have a great deal of interest in upgrading, but it's getting frustrating enough that I'm considering junking the phone.
Thanks in advance,
Ryan
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
GDReaper said:
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
Click to expand...
Click to collapse
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Diddler77 said:
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Click to expand...
Click to collapse
Got pissed and disconnected it after about 45 minutes. Switched to my desktop/Win7 machine. With the bigger monitor I could see that the whole time it was sitting on "Leave CS" it wasn't doing a thing, it now gave me the option to hit the 'Start' button at the bottom of the screen. I LOVE applications that don't let you resize to fit odd sized monitors (like my old Netbook).
So, I hit 'Start', and it pretty much immediately fails. Some of the error messages are differerent though, here's the whole thing:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I find most interesting is the 5th and 4th line from the bottom, Write start followed by FAIL! (Auth). I interpret it as Odin failed to get authorization from the phone to perform the write function. Any other ideas? Going to try Odin 3.10.6 next.
Diddler77 said:
Going to try Odin 3.10.6 next.
Click to expand...
Click to collapse
Yeah, same problems on both computers, both new versions of Odin. Did notice something this time around on the phone's screen that I hadn't noticed before, though it seems to happen in all versions of Odin. Two lines appear on the phone when I hit 'Start' in Odin:
START [224,1440]
SW. REV CHECK FAIL : FUSED : 8, BINARY : 6
The numbers after FUSED and BINARY are very difficult to read. Above is my best guess. Any of them may be a 0 or an 8.
Thanks!
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
GDReaper said:
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
Click to expand...
Click to collapse
That I have not tried. From what I gather I need a PIT file specific to the model. Any idea where I can get it? In terms of the end result, what's the difference between using the PIT and re-partitioning compared to what I've been trying? Like, why do both options exist?
Thanks!
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
GDReaper said:
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
Click to expand...
Click to collapse
Dont the firmwares originally come with pit files ?
Deathvirus said:
Dont the firmwares originally come with pit files ?
Click to expand...
Click to collapse
From what little I gather from the simple Odin instructions page, some firmwares are packaged with additional files. The two versions I've downloaded from sammobile for my device type only contained a single tar.md5 file when unzipped.
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader. The bootloader being locked is primarily designed to prevent root, but it also has the effect of preventing downgrades. If it didn't have that capability, users could simply flash a bootloader that could be compromised, obtain root, and remove the bloatware.
You posted your question in the International S4 forum, and international devices don't lock their bootloaders, which is why no one has really picked up on this until now. The only reason I picked up on the possibility of it being your bootloader is because I own an international device yet live in the US, so I'm acutely aware of the locked bootloaders foisted upon us by AT&T and Verizon.
It is my understanding that Odin fails after trying to flash aboot.mbn because the ROM being flashed has a bootloader that is older than the bootloader currently installed on the phone.
Some models of the s4, such as the Canadian version (sgh-i337m) can be flashed from stock LP to stock KK using Odin without issue.
You're right about the age of the bootloader being a reason why downgrading fails. You're also right that most devices can downgrade without issue. However, the OP's device is not one of them. He happens to have one of the models with a locked bootloader, and to the best of my recollection, the locked bootloader means you cannot downgrade, period.
Strephon Alkhalikoi said:
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader.
Click to expand...
Click to collapse
If this is true, I'm really ticked off. What a waste of time. You'd think that somewhere, on ANY of the forums and websites someone would have mentioned that my device is crippled in this manner. Every single site makes Odin sound like the silver bullet.
Why is there even firmware available for Verizon GS4's then?
Understand I'm not ungrateful for the advice, I do appreciate it. Just venting.
-sigh-
100% true, and it's not limited to Verizon either. AT&T also locks the bootloader. As to mentioning it, it likely is mentioned in the AT&T and Verizon S4 General forums, but you won't find that information here. As I mentioned, this is the International S4 forum, and we don't have locked bootloaders to deal with.
I know it sucks, but this is what we deal with in the US. That's why for my next device I went with a Nexus.
I don't have a PIT file for OF4 firmware on the SM-S975L (Straight Talk variant) so the downgrade failed as for OP, I'm stuck in download mode with a yellow triangle.
Yeah, Verizon released this phone to Straight Talk evidently. I'm locked tight and basically hard bricked. Wicked pissed, too. Since Kies says phone model not supported. CANNOT restore.
Nexus it probably is. This phone was a waste of money.
Or at least...that was until I found a hack that let me install the old Jellybean kernel! http://forum.xda-developers.com/gal...ariant-of4-t3279890/post64511525#post64511525
Only problem is, sure, you can get your kitkat kernel back, but I wasn't successful probably because NB1 firmware was Verizon firmware at the time of my flash so my CSC didn't work, but since they're both JellyBean I got root. But as long as they're the same carrier my hack should work. Link me your firmware, I can let you try. It'll trip the hell out of KNOX though. I used Odin 3.07. It requires some by-hand hex editing. When you gain root you can disable Knox to flash other things with SuperSU.
@LupineDream: Of course you weren't successful in changing kernels. The SM-S975L is not a CDMA (i.e. Verizon) phone, but uses T-Mobile towers. The SCH-R970G is the other Straight Talk S4 and it used Sprint as a carrier. Verizon does not allow MVNOs access to their LTE network, which is how you can tell that you're NOT on Verizon.
The bootloader on Straight Talk S4 devices is not locked down like the OP's bootloader. Otherwise it would not be possible to install custom ROMs to the device. I have a distinct feeling that your hack will not work. Not because it's incorrect as you clearly had success, but because of the locked bootloader on the device, which is designed to prevent the very thing you successfully accomplished on your Straight Talk device.
To restore your phone to working condition, download the S975L firmware from sammobile and flash it through the BL slot in Odin. Then sell it and get a Nexus.
Hey, if I found a workaround for obtaining root on the ATT variant, users of that phone now have an fstab and an (almost complete) list of partitions and mount points for a device tree. So I hope that information at least made their lives better. In knowing they can indeed flash a kernel with said workaround. The device list, fstab, and mount points are all in my root guide now. Since after reflashing the boot image by itself the device boots again and has maintained root status, though with broken WiFi which can be fixed with a custom kernel. Oh well, at least users of my phone get a custom ROM., at least if you've got the ATT variant. All the info is in my thread for ATT variants. I' don't have my stock kernel, however. But it isn't an issue as for what I've provided, I think its enough to get a custom one for the ATT variants. Still going to sell and get my Nexus. But left it with a bang I suppose. I'll hack a locked bootloader until I'm blue in the face if it means I got root. You are indeed right, though. It isn't for ME to keep around, but please note that before I was even able to flash a kernel, I had to hack it. It was displaying secure boot status and would not allow flashing of anything. I was told they where all locked. I was never able to root OF4 before because of "locked conditions" where NB1 refused to flash before my hack.
I'm going shopping soon. Maybe I'll get the Verizon variant on the side to see if I can force my way in through another one of these types of loopholes. After all, my device would not flash a kernel before I did what I did to it...I was able to disable knox and allow kernel flashing by doing so. Through SuperSU. That bit was set before I did what I did to the device. All it takes is flashing of the NB1 kernel to Verizon through tricking knox it's official firmware and enough know-how to get the system to boot well enough to be able to inject root.
My device still won't flash non-official firmware or recovery. Because of a verification check in the kernel. I tried. Sig fai on kernel. But, now that Knox can be disabled, all it takes is an if/of dd flash of modified aboot in adb and then anything is possible at that point. I looked into loki_tool for always passing signature check passed to hardware knox. And clearing out EERAM before knox gets a chance to react. Loki'fied aboots satisfy knox pretty well I'd say.
The ROM displayed there iis for the Verizon variant by the way. I found Verizon-related apks in system.img.ext4. Even without the modem, it still won't flash. Have a download, rename it, extract the tar and hex edit look through the file. Yep, that's a verizon variant ROM.
One question, however, is does hardware knox do a checksum on aboot? That would pretty much make this argument a moot point.
Ask Chainfire. He needed to know about how Knox functioned so he could get SuperSU to disable it.
I have the unlocked S8 from Samsung and I'm missing VVM and WiFi calling. I looked at several guides on here and other sites and nothing works to be able to flash it to Verizon. When I go into Odin and try to flash the factory binary I get the following in Odin. There has to be an easier way to get these features on this phone. I've spent hours on this and now I have to restore my phone again. Yes I have the latest Samsung drivers and latest Odin that is recommended per the guides.
<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.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Beyond frustrated now, now I can't even get my teamviewer 2 factor authentication back.
Go to updato.com
Download the latest fw for the G950W
Delete .md5 off the end of every file after extraction
Use MODDED Odin and flash them all. (CSC, NOT HOME CSC)
Go back to update.com
Download latest VZW firmware for the G950U
Delete .md5 off the end of every file after extraction
Use MODDED Odin and flash them all. (CSC, NOT HOME CSC)
Post flash it will boot into recovery and install stuff. Watch for it to turn off, soon as it does hold Volume Up + Bixby button to get back into recovery. It'll say No Command for a minute, wait... When recovery pops up wipe data a couple times then reboot.
You should have a Verizon S8
I'd like to try it and I did download the Verizon firmware and attempted to flash without the HOME but Odin still fails. Not sure if I'll attempt again it takes hours to get all my apps back
Sent from my SM-G950U1 using XDA-Developers Legacy app
Using modded Odin?
Try a different cable or port. Seen MANY failures remedied by using a different cable
Use modified odin
Tried the stock cable and another one and modded and unmodded one. Even re-downloaded Odin and tried a prior version. Running Windows 10 and even tried compatibility mode and ran as administrator.
GrandMstrBud said:
Tried the stock cable and another one and modded and unmodded one. Even re-downloaded Odin and tried a prior version. Running Windows 10 and even tried compatibility mode and ran as administrator.
Click to expand...
Click to collapse
Did you do step by step as @joe3681 suggested?
First flash the Firmware for 950W
Then flash the Firmware for Verizon and etc.
Have all your drivers installed and restarted computer after install?
Did you install the system wide adb found here on XDA?
With all that i never have any troubles...
The first step is to flash the factory binary. I was never able to. Yes I've restarted a few times. Adb devices recognized the device just fine. I've flashed many phones prior to this one.
i got an S8 from Verizon, and i checked the IMEI and it says its unlocked. So, technically speaking, my S8(G950U) is a factory unlocked S8 with verizon FW on it?
I have a G950U1 with VZW. I use Google Voice for visual voicemail. https://support.google.com/voice/answer/165656?hl=en
Sent from my SM-G950U1 using Tapatalk
GrandMstrBud said:
The first step is to flash the factory binary. I was never able to. Yes I've restarted a few times. Adb devices recognized the device just fine. I've flashed many phones prior to this one.
Click to expand...
Click to collapse
Did you ever get to flash Verizon on your unlocked S8? I'm trying to do the same thing as you, and was wondering if you had any success. Thanks
No everything I tried failed. Debating on selling it and going with a device that works with VZW with all features. IDK why it can't work, you can use an unlocked iPhone and it works fine with VVM and WiFi calling.
BS that you have to pay to download this from sammobile.
GrandMstrBud said:
BS that you have to pay to download this from sammobile.
Click to expand...
Click to collapse
free servers are down for the weekend.
mweinbach said:
free servers are down for the weekend.
Click to expand...
Click to collapse
I didn't even attempt when I seen the time to download plus the fact free downloads won't go over 2GB. This has been so frustrating I'm about to sell it and get one through Verizon or a google device. I can't believe there isn't an easy way to switch carriers.
GrandMstrBud said:
I didn't even attempt when I seen the time to download plus the fact free downloads won't go over 2GB. This has been so frustrating I'm about to sell it and get one through Verizon or a google device. I can't believe there isn't an easy way to switch carriers.
Click to expand...
Click to collapse
download from updato.com or go and find a software called SamFirm and download them directly from Samsung Servers.
This is so frustrating, tried new computer new cables redownloading firmware and still fails.
GrandMstrBud said:
I didn't even attempt when I seen the time to download plus the fact free downloads won't go over 2GB. This has been so frustrating I'm about to sell it and get one through Verizon or a google device. I can't believe there isn't an easy way to switch carriers.
Click to expand...
Click to collapse
There is, and many have done it. There is something either wrong with your computer, your cables, or your device. Just because adb works does not mean there isn't a problem devices use many different ways to connect and adb and download mode aren't the same