Database Info

[Q] I9103r doesnt want Rooted in Odin?Please Help

I have a big problem with Rooting my Samsung via ODIN. I'm using difirent version of odin -started v.1.85 up to 3.07 and in all i have the same problem. The information when I started to root ma samsung is like this below:
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> recovery.img
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the status in left upper window is of course FAILED
I'm using the 4.04 android version I9103XXLQ3.
I'm using Windows 7 64 bit in my computer.
If I understand correctly, when I want to upload new version of ROM like avatar rom, at first i must root my phone using Odin, and then it possible to upload the new Avatar 4.2.2 rom by the recovery mode from the sdcard.
There is a streng situation after I try to root my phone via odin and have the information like few lines above, when i tray to start my phone then I have the information in ma screen like this below whith the yellow triangle "exclamation".
Firmware upgrade encountered an issue.
Please select recovery mode in Kies and try again.
Can anybody could give me some advices how to fix this problem. I will be very appreciate
Thanks and sorry for my english at all

I9103-junior said:
I have a big problem with Rooting my Samsung via ODIN. I'm using difirent version of odin -started v.1.85 up to 3.07 and in all i have the same problem. The information when I started to root ma samsung is like this below:
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> recovery.img
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the status in left upper window is of course FAILED
I'm using the 4.04 android version I9103XXLQ3.
I'm using Windows 7 64 bit in my computer.
If I understand correctly, when I want to upload new version of ROM like avatar rom, at first i must root my phone using Odin, and then it possible to upload the new Avatar 4.2.2 rom by the recovery mode from the sdcard.
There is a streng situation after I try to root my phone via odin and have the information like few lines above, when i tray to start my phone then I have the information in ma screen like this below whith the yellow triangle "exclamation".
Firmware upgrade encountered an issue.
Please select recovery mode in Kies and try again.
Can anybody could give me some advices how to fix this problem. I will be very appreciate
Thanks and sorry for my english at all
Click to expand...
Click to collapse
check whether Kies is running in background?
close it. also u must follow soft brick tutorial.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using Tapatalk (VIP)
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™

Could you post Odin screen shot with all details how you are flashing...
Sent from my Nexus 4 using Tapatalk 2

screen shot from Odin
Hi
I attach an image from Odin. Any other suggestions welcomed.
Thanks
Peter

Disturbed™ said:
check whether Kies is running in background?
close it. also u must follow soft brick tutorial.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using Tapatalk (VIP)
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™
Click to expand...
Click to collapse
Hi
I removed the Kies from Windows, because it seemed to me that it can cause conflict when I''m starting flash my phone.But unfortunately, problem is the same.
Where I can find "follow soft brick tutorial". and what is it used for.
Thanks at all

If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.

Nikhil said:
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Click to expand...
Click to collapse
what a catch. we must have reading habits.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using XDA Premium 4
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™

Nikhil said:
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Click to expand...
Click to collapse
Hi, thanks a lot - solution with cwm ver.4.0.0.2 turned out to be the right way.I managed to upload to my phone this version of cwm but I wondering if this is only ver. that will by works on my i9103r?. Anyway now I am trying to upload new unofficial ROM and one question about that. Where can I find a instruction how to deal with this operation I now only that this is doing from the download mode using cwm. But that's all. Thanks in advance:good:

I9103-junior said:
Hi, thanks a lot - solution with cwm ver.4.0.0.2 turned out to be the right way.I managed to upload to my phone this version of cwm but I wondering if this is only ver. that will by works on my i9103r?.
Click to expand...
Click to collapse
No you can flash different versions also. Since you installed CWM v4.0.0.2, now onwards download flashable zip file of other recoveries and flash them.
Anyway now I am trying to upload new unofficial ROM and one question about that. Where can I find a instruction how to deal with this operation I now only that this is doing from the download mode using cwm. But that's all. Thanks in advance:good:
Click to expand...
Click to collapse
Visit [INDEX] Custom ROM/Kernel/MOD/Guide/Tool
links to various Roms are given there and instructions are given in respective Rom's OP.
Happy Flashing..

[Q] (Q) HELP....GT-N8010 bricked ?????????

Hi there,
I have a Samsung Galaxy Note 10.1 WIFI (GT-N8010). I had it rooted, custom ROM on it.....frequently forced closes so i decided to cleensweep the thing. Went into TWRP....did factory reset (wipe cache, Dalvik and System) and then formatted DATA.
So no OS anymore.
Then when i wanted to flash the custom ROM (from external SD like i always do) again.....it got stuck.......couldnt flash it it said. Okay.....so.....now what i thought. I tried the procedure of flashing with the galaxy Toolkit. Doesnt work because it waits for "debug enable"....but there is no OS.....so cant do that.
Then i made the biggest mistake i guess.
I flashed new firmware through ODIN.....but accidently for the GT-N8000. Strange that the procedure went well.
Then it came: the device got stuck on the Samsung logo.....no bootloop....just the logo. When i restarted the tablet it went strait to download mode (power and vol - normally) I dont even get the choice of cancelling or continue to download mode. The screen looks like this:
ODIN MODE
product name: gt-n8000
current binary: samsung official
system status: custom
(and then in gray) RP SWREV: A2
And NO custom binary download: no
When i go into recovery mode (power and vol+) it goes strait to the android with "downloading, do not turn off device"
WHAT HAPPENED ????
And does somebody know what to do PRETTY PLEASE
Hope you guys know what to do....or is it bricked ????
PS. It's still seen by Odin !
Greetz from the netherlands

I had the same problem as you, and I had to flash via Odin v3.09 a firmware 4.4.2 and it rebooted fine.

crombull said:
I had the same problem as you, and I had to flash via Odin v3.09 a firmware 4.4.2 and it rebooted fine.
Click to expand...
Click to collapse
just flashing 4.4.2 didn't do the trick. ...odin said "fail" when trying to flash the nand. I had to flash another pit file with it. Why that had to be done I don't know. ..just read it somewhere.
Thnx for the reply

PassieWater said:
just flashing 4.4.2 didn't do the trick. ...odin said "fail" when trying to flash the nand. I had to flash another pit file with it. Why that had to be done I don't know. ..just read it somewhere.
Thnx for the reply
Click to expand...
Click to collapse
I have a similar problem and can't flash original firmware via odin. could you send me the pit file you have used?
Thanks in advance!

I just sent you the pit file through mail
Hope it helps

Bricked since updated to KitKat - Odin flashes fail!!
PassieWater said:
I just sent you the pit file through mail
Hope it helps
Click to expand...
Click to collapse
Could I please have a secure PIT file for the GT-N8010 16GB bought in France? I've bricked my Note 10.1 after updating to the official Kitkat (N8010XXUDNE4_N8010OXXDNF1_HOME.tar.md5). I did a wipe data and cache and all seemed to be working fine for 2 days... but the tablet got stuck on a game and after a force close has been stuck in a bootloop with no access to recovery mode. I do manage to get into download mode and have tried to flash a number of times with different roms (going back seems to be impossible with KitKat) but to no avail as I keep getting an issue about 'no PIT partition'. I took it to a shop (as my warranty ran out a month ago - lucky me!) and they were also unable to flash the tablet so the issue does not seem to be the cable or the drivers (as Odin recognizes the tablet). I tried flashing with a PIT file (ticking re-partition with and without the kitkat rom) that I got on some website but I'm not certain it is the right one for my GT-N8010 and it also fails. Before I try a Nand erase I want to make sure that I have the right PIT file. By the way does the PIT file you have work with KitKat as the one I found seems to be for an outdated version of Android and as Kitkat doesn't enable one to go back to an older version of Android I'm in a catch 22 with only the Nand erase option left?
FYI, I tried flashing a recovery like TWP to try flashing custom roms but it also doesn't work.
Any other ideas? Should I tick Nand Erase and Phone EFS Clear. As the issue seems to be the kitkat bootloader is it possible to flash a bootloader? Can't find any trace of anything other than the tar files for GT-N8010 in Jelly Bean or KitKat. Anybody have a bootloader, PDA, CSC and Phone file for the GT-N8010? Can one attempt the following on a GT-N8010: http://forum.xda-developers.com/showthread.php?t=2610757&page=2 ?
Thanks for any help as I've been without my tablet for weeks now!!:crying:

Need PIT file for GT-N8010 16GB under Kitkat
Any PIT file please? Thanks!

Same problem here
PassieWater said:
I just sent you the pit file through mail
Hope it helps
Click to expand...
Click to collapse
can you send me that pit file too, please?

Me too!
I'd like that file too...
I just flashed the wrong bootloader file onto my N8010. Luckily it's still working!
Still looking for the correct KitKat bootloader, but I'd happily take the pit file and see if that works.
Pretty Please!

PassieWater said:
just flashing 4.4.2 didn't do the trick. ...odin said "fail" when trying to flash the nand. I had to flash another pit file with it. Why that had to be done I don't know. ..just read it somewhere.
I have the same problem... flashed 4.4.2 on a North American Galaxy Note 10.1 (2012) with Odin and am stuck in downloading mode.
Can someone send me the pit file I require? Please!
Click to expand...
Click to collapse

Lucky me! Flashing the wrong bootloader probably didn't work. I was able to flash a stock KitKat rom yesterday and my device still seems to have a working pit file.
Details: German Note 10.1 GT N8010 updated to KitKat, but the pit file seems to be older. Any other info needed?
This is how I got the pit file.
Code:
sudo heimdall download-pit --output Samsung-Note-10.1-PIT.txt
I had trouble opening the result in a text editor, so I'm not sure, I got it right. You'll probably have to rename it... Let's see, if I'm allowed to upload.

mendacium said:
Lucky me! Flashing the wrong bootloader probably didn't work. I was able to flash a stock KitKat rom yesterday and my device still seems to have a working pit file.
Details: German Note 10.1 GT N8010 updated to KitKat, but the pit file seems to be older. Any other info needed?
This is how I got the pit file.
Code:
sudo heimdall download-pit --output Samsung-Note-10.1-PIT.txt
I had trouble opening the result in a text editor, so I'm not sure, I got it right. You'll probably have to rename it... Let's see, if I'm allowed to upload.
Click to expand...
Click to collapse
Thanks... Any idea what the name of the original PIT file is?
(I believe it should have the .pit extension. I hope I can rename this file accordingly?)

Sorry, no.
Heimdall doesn't seem to care how the file is named. I'd hazard a guess, that it's similar for most Samsung devices.

help please. .
Hi
Any chance of sending me the PIT file. . I did the same! :'(
Thanks in advance .
.

PLEASE HELP, cant ODIN back to stock

Everything was fine. tried the minuit (or however you spell it) mod. Ended up in a boot loop. i can get into download mode fine. Downloaded the stock firmware to odin back and start over, but when i try, it checks the MD5 just fine. starts the "setupconnection" then i get a fail "can't open the serial(COM) port.
Am i doing something wrong here? Any help at all would be greatly appreciated!

What firmware version were you on before bootloop and what version are you trying to ODIN?

jlaholton said:
Everything was fine. tried the minuit (or however you spell it) mod. Ended up in a boot loop. i can get into download mode fine. Downloaded the stock firmware to odin back and start over, but when i try, it checks the MD5 just fine. starts the "setupconnection" then i get a fail "can't open the serial(COM) port.
Am i doing something wrong here? Any help at all would be greatly appreciated!
Click to expand...
Click to collapse
You need odin 3.10.6 and make sure you downloaded the latest stock firmware .tar. when flashing, don't move the phone, cord or laptop (if thats what you have).
Sent from my SM-G925P using XDA Free mobile app

Me too. The odin stuck at <ID:0/010> NAND Write Start!!
My stock ROM is OE2 and want to flash OF7, the original stock ROM has been rooted and TWRP installed.

lwang9 said:
Me too. The odin stuck at <ID:0/010> NAND Write Start!!
My stock ROM is OE2 and want to flash OF7, the original stock ROM has been rooted and TWRP installed.
Click to expand...
Click to collapse
Wipe system and try again

Soooperstar said:
Wipe system and try again
Click to expand...
Click to collapse
TWRP has been replaced to the original recovery firmware. It couldn't read the internal storage.

lwang9 said:
TWRP has been replaced to the original recovery firmware. It couldn't read the internal storage.
Click to expand...
Click to collapse
Are you able to factory reset from stock recovery?

Soooperstar said:
Are you able to factory reset from stock recovery?
Click to expand...
Click to collapse
I failed to use ODIN flash the entire stock ROM which is over 3gb tar.md5 file. Could I download the stock recovery only and flash by ODIN? Also, I am not sure if PIT file helps. I couldn't find PIT file download yet.

lwang9 said:
I failed to use ODIN flash the entire stock ROM which is over 3gb tar.md5 file. Could I download the stock recovery only and flash by ODIN? Also, I am not sure if PIT file helps. I couldn't find PIT file download yet.
Click to expand...
Click to collapse
Not completely understanding you. Are you saying Odin is failing when trying to Odin latest firmware?

Yes, I failed to flash the latest firmware by ODIN 3.10. I read another post mentioned PIT file to flash to avoid this issue. However, I don't know where I could download the PIT file for this phone.

lwang9 said:
Yes, I failed to flash the latest firmware by ODIN 3.10. I read another post mentioned PIT file to flash to avoid this issue. However, I don't know where I could download the PIT file for this phone.
Click to expand...
Click to collapse
Are you on the latest Odin version and are you using the correct firmware?

Yes, I did.

lwang9 said:
Yes, I did.
Click to expand...
Click to collapse
What Odin version are you using? What phone do you have, and what firmware version are you trying to use? What firmware are you on now?

Soooperstar said:
Are you on the latest Odin version and are you using the correct firmware?
Click to expand...
Click to collapse
My Odin version is 3.10 and the firmware I downloaded from Sammobile.
sammobile.com/firmwares/download/50549/G925PVPU2BOF7_G925PSPT2BOF7_SPR/

lwang9 said:
My Odin version is 3.10 and the firmware I downloaded from Sammobile.
sammobile.com/firmwares/download/50549/G925PVPU2BOF7_G925PSPT2BOF7_SPR/
Click to expand...
Click to collapse
And you have the sprint s6 edge? You didn't answer all my questions

used one of these when i had recent problem.
edit: try to use the same firmware your currently on (what i did) and the thing that worked for me was using an older sammy usb cable. Beleive it or not the original one kept failing on me. i had a thicker black one that was from my s4 maybe or note 2 i think and used that one and boom went thru. good luck

los82 said:
edit: try to use the same firmware your currently on (what i did) and the thing that worked for me was using an older sammy usb cable. Beleive it or not the original one kept failing on me. i had a thicker black one that was from my s4 maybe or note 2 i think and used that one and boom went thru. good luck
Click to expand...
Click to collapse
Thanks!!! It worked. Just grab another USB cable. The original one kept failing on me either. The issue has been solved. Thanks again.

Galaxy SM-J700P - wont' boot after loading Superuser

Just trying to root. Everything went fine until I loaded Superuser. Now, upon reboot, I get the Samsung logo, then the Virgin mobile animation, but it hangs there. I can get into TWRP, I can get into DL mode. Not sure what to try next.
I was reading to maybe flash the stock tar? Should I do that before I go and try custom?

Gamestress said:
Just trying to root. Everything went fine until I loaded Superuser. Now, upon reboot, I get the Samsung logo, then the Virgin mobile animation, but it hangs there. I can get into TWRP, I can get into DL mode. Not sure what to try next.
I was reading to maybe flash the stock tar? Should I do that before I go and try custom?
Click to expand...
Click to collapse
Flash stock recovery

Don't panic, happens all the time
Just take a logcat and post it up here..
As the user above me said, don't flash stock recovery, it would most probably be flashing a stock firmware

http://forum.xda-developers.com/galaxy-j7/development/samsung-stock-recovery-700p-read-t3454061
Follow instructions to fix bootloop
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
believe it or not i made this to fix the bootloop into TWRP.... apparently TWRP bugs the phone to keep booting into recovery

Still hanging
Ugh.. got the file, extracted.. under BL.. ran fine, up top says PASS. Still hanging at the VM animation.
<ID:0/006> Added!!
<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> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
EDIT.. oh wait do I do a factory reset after then?

UPdate hah
Ok, I'm at least in to the phone again after doing this:
http://forum.xda-developers.com/galaxy-j7/how-to/root-samsung-galaxy-j7-sm-j700p-t3430185
^^^^^^^^^^^^^^^^^^^^^^^^^^ worked! ^^^^^^^^^^^^^^^^^^^^^^^^^^^
It's taking me thru set up again, so not sure if I'm actually rooted. But at least I dont have a brick, .... yet.
OK, DL'd a root checker..and Congratulations! Root access is properly installed on this device!
Whew!

SykkNyzz said:
http://forum.xda-developers.com/galaxy-j7/development/samsung-stock-recovery-700p-read-t3454061
Follow instructions to fix bootloop
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
believe it or not i made this to fix the bootloop into TWRP.... apparently TWRP bugs the phone to keep booting into recovery
Click to expand...
Click to collapse
My Phone model is SM-J700H/DS.
the phone is not booting after flash SuperSU.
i do get in TWRP and Downloading Mode.
will this solution will fix it ?

Are you on marshmallow? Which version of SuperSu have you flashed?
Sent from my SM-J700F using XDA-Developers mobile app

dodo2244 said:
Are you on marshmallow? Which version of SuperSu have you flashed?
Sent from my SM-J700F using XDA-Developers mobile app
Click to expand...
Click to collapse
this version :
UPDATE-SuperSU-v2.46.zip
android 6.0.1 (marshmallow)
BuildNumber : MMB29K.J700HXXU2BPG4

iTaisHi said:
My Phone model is SM-J700H/DS.
the phone is not booting after flash SuperSU.
i do get in TWRP and Downloading Mode.
will this solution will fix it ?
Click to expand...
Click to collapse
You need to find the device version for your stock recovery. In theory it will work, but since I only own j700p that method fixed my bootloop back then for only constantly booting back to TWRP. They recently fixed that error for ours with rebooting in the TWRP program.

SykkNyzz said:
You need to find the device version for your stock recovery. In theory it will work, but since I only own j700p that method fixed my bootloop back then for only constantly booting back to TWRP. They recently fixed that error for ours with rebooting in the TWRP program.
Click to expand...
Click to collapse
thanks SykkNyzz and Dodo,
Problem Solved,
i had falshed the wront SuperSU version.
falshed again v2.68 and that solve the problem.
i took it from here:
http://rootmygalaxy.net/flash-supersu-using-twrp-recovery-root-any-android-device/

Bravo!
Sent from my SM-J700F using XDA-Developers mobile app

SoNiC_bOoM15 said:
Just take a logcat and post it up here..
As the user above me said, don't flash stock recovery, it would most probably be flashing a stock firmware
Click to expand...
Click to collapse
Bro, with whom are u messing with ? see his thanks meter

SykkNyzz said:
They recently fixed that error for ours with rebooting in the TWRP program.
Click to expand...
Click to collapse
Who fixed the error, Teamwin? Is there a commit?

ashyx said:
Who fixed the error, Teamwin? Is there a commit?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/development/twrp-3-0-2-0-beta-j700p-2016-fixed-t3485766 @Starchild2k did.

SykkNyzz said:
http://forum.xda-developers.com/galaxy-j7/development/twrp-3-0-2-0-beta-j700p-2016-fixed-t3485766 @Starchild2k did.
Click to expand...
Click to collapse
I'm not sure what you're pointing me to as I don't see a reference to it in that thread?

The fixed TWRP that doesn't cause an issue in j700P

SykkNyzz said:
The fixed TWRP that doesn't cause an issue in j700P
Click to expand...
Click to collapse
We must be referring to different issues. Thanks anyway.

download the original 6.0 firmware of the j7 and flash it with the help of odin

First flash the original firmware of j700f download it from sam mobiles website,the again install the twrp file as flashing firmware remove it. Then download the super su file from the given link and only download if u have j700f or otherwise it might brick again
https://bitbucket.org/Serverbee/downloadbee/downloads/BETA-SuperSU-v2.74-2-20160519174328.zip

I535 bricked on download mode

Hello XDA!
I have a S3 I535 bricked on the "downloading mode", no matter what I do it always ends on the download screen, no way to access to recovery. I have tried with Odin, Heimdall and all advices in this and other forums.
The error is always the same:
Heimdall
=======
Without repartition:
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
With repartition:
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Odin
====
With and without repartition:
<ID:0/010> Get PIT for mapping..
<ID:0/010> There is no PIT partition.
In the phone: "Odin : flash read failure"
I'm using the right SCH-I535 PIT file (16Gb)
As I understand, these programs need the PIT information to write at the right address in the memory map of phone. Right? But for some reason my cell can't provide it or change it. However there are ways to "read" the PIT file and get the "base address" for a specific partition. The question: there is a way to force Odin, Heimdall or fastboot to flash a particular image partition to its known address?
Something like this:
heimdall flash --recovery recovery.img --base 0x1234abcd
Is it possible, would it works and solve my problem?
Thanks!!

what tar.md5 are you trying to flash? I hardbricked one of these a while back and had to use the debrick.img to fix it, but if you can get to DL mode, then you shouldnt be THAT boned... yet...

youdoofus said:
what tar.md5 are you trying to flash? I hardbricked one of these a while back and had to use the debrick.img to fix it, but if you can get to DL mode, then you shouldnt be THAT boned... yet...
Click to expand...
Click to collapse
A 4.4.2 stock rom from: gsm-file
I already tried debrick images, nothing changes. It always fail on PIT step.
Thanks

mikefncu said:
A 4.4.2 stock rom from: gsm-file
I already tried debrick images, nothing changes. It always fail on PIT step.
Thanks
Click to expand...
Click to collapse
youre trying to odin a tar.md5 built for a different phone? i ask because i dont understand what you mean by "from: gsm-file"

youdoofus said:
youre trying to odin a tar.md5 built for a different phone? i ask because i dont understand what you mean by "from: gsm-file"
Click to expand...
Click to collapse
Sorry, gsm-file is a website with stockroms, google it, I can't put the link because Im a new member.

mikefncu said:
Sorry, gsm-file is a website with stockroms, google it, I can't put the link because Im a new member.
Click to expand...
Click to collapse
oh, no worries. have you tried getting the file from www.sammobile.com/firmwares ? its the most legit source for the file, takes FOREVER, but its from the source. You might have bad downloads