Hi all i just tried to flash a offical rom with odin than it fails so i unplug it now whenever i switch on i see Firmware upgrade encountered an issue, Please select recovery mode in kies. I believed it is semi brick the reason that cause the brick probably because i select the wrong option in bootloader however i have not fiddel with the pit or partition. which is the best way to get out? i have been googling awhile but no clear definte answer
Just go to Download Mode (Vol Down+Home+Power) and flash a full firmware again, via Odin, this time don't do anything wrong
Regards.
ithehappy said:
Just go to Download Mode (Vol Down+Home+Power) and flash a full firmware again, via Odin, this time don't do anything wrong
Regards.
Click to expand...
Click to collapse
Hi ithehappy i have just tried and it failed agian here are some logs
<ID:0/011> modem.bin
<ID:0/011> param.lfs
<ID:0/011> Sbl.bin
<ID:0/011> zImage
<ID:0/011> boot.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011>
<ID:0/011> Receive Response form LOKE
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time i just tick pda phone and csc i have been trying to use http://forum.xda-developers.com/showthread.php?t=1075278 official rom according to the logs what do you think it may went wrong?
That's the correct thread. Don't know what is wrong!
You sure you are flashing a Full firmware, i.e- around 300MB size? Just extract it, you will get a .tar, add to the PDA section of Odin.
Regards.
X807 said:
Hi ithehappy i have just tried and it failed agian here are some logs
<ID:0/011> modem.bin
<ID:0/011> param.lfs
<ID:0/011> Sbl.bin
<ID:0/011> zImage
<ID:0/011> boot.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011>
<ID:0/011> Receive Response form LOKE
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time i just tick pda phone and csc i have been trying to use http://forum.xda-developers.com/showthread.php?t=1075278 official rom according to the logs what do you think it may went wrong?
Click to expand...
Click to collapse
Your phone is not bricked it's a fault from your phone
Give me more details so I can help you!
PS here are official firmwares >>> http://www.samfirmware.com/fwandroid.htm
wow thanks ! i just try to fiddling an now got it rebooted with nothing wrong: This is what i have done i have just choosen csc and pda and leave the phone without any option will that be fine?
is quite weird the phone basiclly updated to a new firmware lost the root but the clockworkrecovery is still intact, so i tried to root it again, and it works fine, so i think is possible to flash without selecting the phone option in odin??????????
You just need to select PDA in Odin, nothing else.
And when you flash a ROM, even the same old ROM you had, you will lose Root, you've to Re Root.
Regards.
Related
Hello,
I'm in trouble. I have a SGS2 with stock 2.3.4 and did the cfroot a while ago and all went well.
Today I got a notice from KIES that an update was available, and so I started the update which failed.
After that my phone won't start at all and got stuck on the screen which said that I should use KIES recovery mode. I tried that but it didn't worked.
So I have tried to reflash with the cfroot, but that also didn't help.
So I wanted to reflash the stock rom as described here http://forum.xda-developers.com/showthread.php?t=1075278
but that's also giving me errors.
Odin doesn't even write the rom it gave me this:
<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> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
Can anyone help me please ?? I need the phone for my work
Best Regards,
Stefan.
tjempeng said:
Hello,
I'm in trouble. I have a SGS2 with stock 2.3.4 and did the cfroot a while ago and all went well.
Today I got a notice from KIES that an update was available, and so I started the update which failed.
After that my phone won't start at all and got stuck on the screen which said that I should use KIES recovery mode. I tried that but it didn't worked.
So I have tried to reflash with the cfroot, but that also didn't help.
So I wanted to reflash the stock rom as described here http://forum.xda-developers.com/showthread.php?t=1075278
but that's also giving me errors.
Odin doesn't even write the rom it gave me this:
<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> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
Can anyone help me please ?? I need the phone for my work
Best Regards,
Stefan.
Click to expand...
Click to collapse
Pull out the battery, reinsert the battery after 30 seconds, go in downloadmode (volume up + menu button + power button) and reflash the stock rom you need with Odin. Do NOT tick repartition or anything. You`ll find the stock rom here http://forum.xda-developers.com/showthread.php?t=1075278. Do NOT use a pit file. Flash the rom in PDA. Good luck
tjempeng said:
Hello,
I'm in trouble. I have a SGS2 with stock 2.3.4 and did the cfroot a while ago and all went well.
Today I got a notice from KIES that an update was available, and so I started the update which failed.
After that my phone won't start at all and got stuck on the screen which said that I should use KIES recovery mode. I tried that but it didn't worked.
So I have tried to reflash with the cfroot, but that also didn't help.
So I wanted to reflash the stock rom as described here http://forum.xda-developers.com/showthread.php?t=1075278
but that's also giving me errors.
Odin doesn't even write the rom it gave me this:
<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> boot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
Can anyone help me please ?? I need the phone for my work
Best Regards,
Stefan.
Click to expand...
Click to collapse
Dear Stefan,
let me suggest:
1. Try to use another USB port.
2. Try to use another USB cable.
3. Try to boot into recovery mode (Volume UP + Home + Power, and hold the keys until the recovery menu appears), then choose factory reset and reboot.
4. Start Odin as Administrator and make sure that KIES (and no process of KIES) is running on your PC. Then try to flash the stock ROM again.
5. After flashing, try to boot into recovery mode (Volume UP + Home + Power, and hold the keys until the recovery menu appears), then choose factory reset and reboot.
Hope that it helps.
Good luck !
Solved !!!
YES !!!! IT WORKED !!!!!
I'm not sure which tip did the trick as I did all the things you both said and it worked !
I'm so happy !!!
YOU GUYS ROCK !!!!!
XDA is the best
Ok i need help so i have the telus samsung fascinate 4g and yes it is rooted its running 2.3.4 and i have put CWM on it but every time i try to boot into the recovery it goes to the stock recovery and when i try to install a rom on it i get that stupid E:signature verification failed or whatever it is how to i fit it so i can install roms
How did you load the cwm recovery onto the phone? If you didn't use the program odin, then you didn't do it right. The reason it boots to the stock recovery is because your cwm recovery didn't load. Pretty simple to fix, just download odin and read up about it (its very simple to use) and then flash this cwm recovery using the program : http://dl.dropbox.com/u/32493357/cwm4_fixed_for_cm7-ODIN.tar
Then boot into recovery and you will have cwm recovery!
ok so where do i put this file in odin?
darkninja66 said:
ok so where do i put this file in odin?
Click to expand...
Click to collapse
Put it under the pda section
Sent from my SCH-I500 using XDA App
Just a heads up if you did not know already, make sure you only use files that are compatible with telus.... flashing a fascinate rom on a telus version will leave you bricked.
ok so i put it in the pda section and i hit start and the phone it was in download mode and it registered but when i hit start i got this message
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hi guys, i have an i9100p currently runnning custom rom and i would like to flash the stock ICS rom from my carrier (orange) i downloaded Odin and the rom itself from samfirmware and also the flashguide for some help. the flashguide mentions putting each file in the correct place but this rom file only has 1 file(a ZIP file) also do i need to re partition etc.. i have looked elseware on XDA but only seemed to come across the guides where there is the Phone modem and CSC but as i have none of those files, i really need help... thanks guys
Extract the zip, you'll be able to find the needed files there.
curodot said:
Extract the zip, you'll be able to find the needed files there.
Click to expand...
Click to collapse
Theres just one MD5 file?
AntAust1513 said:
Hi guys, i have an i9100p currently runnning custom rom and i would like to flash the stock ICS rom from my carrier (orange) i downloaded Odin and the rom itself from samfirmware and also the flashguide for some help. the flashguide mentions putting each file in the correct place but this rom file only has 1 file(a ZIP file) also do i need to re partition etc.. i have looked elseware on XDA but only seemed to come across the guides where there is the Phone modem and CSC but as i have none of those files, i really need help... thanks guys
Click to expand...
Click to collapse
if it has only one big file then put in PDA section and flash, leave all the others to default values before pressing flash.
Double check the rom you have downloaded. People often flash i9100 roms to other variants.
bala_gamer said:
if it has only one big file then put in PDA section and flash, leave all the others to default values before pressing flash.
Double check the rom you have downloaded. People often flash i9100 roms to other variants.
Click to expand...
Click to collapse
thanks for your help! .. do i need to tick re partition or auto reboot or anything?
AntAust1513 said:
bala_gamer said:
if it has only one big file then put in PDA section and flash, leave all the others to default values before pressing flash.
Double check the rom you have downloaded. People often flash i9100 roms to other variants.
Click to expand...
Click to collapse
thanks for your help! .. do i need to tick re partition or auto reboot or anything?
Click to expand...
Click to collapse
Reading fail.
ctomgee said:
Reading fail.
Click to expand...
Click to collapse
just being sure, i bricked my old phone using odin a while ago so im cautious thanks for all your help
AntAust1513 said:
just being sure, i bricked my old phone using odin a while ago so im cautious thanks for all your help
Click to expand...
Click to collapse
go ahead and flash , and do please take some good time to read .
bala_gamer said:
go ahead and flash , and do please take some good time to read .
Click to expand...
Click to collapse
Yeah yeah i think im in bootloop (its been about 5 minutes) any ideas? its a stock from for my phone.
AntAust1513 said:
Yeah yeah i think im in bootloop (its been about 5 minutes) any ideas? its a stock from for my phone.
Click to expand...
Click to collapse
|Yes the dont post yet another bootloop post at the top of the page .
jje
WINNING. Sorted
XmitData fail
HI Guys, Flashing the ROM via Odin I get the following error:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img.md5
<ID:0/011> NAND Write Start!!
<ID:0/011> recovery.img.md5
<ID:0/011> system.img.md5
<ID:0/011> __XmitData_Read ..
<ID:0/011> XmitData Fail..
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have searched the net and unable to get any related issues, please help.
dabnis said:
HI Guys, Flashing the ROM via Odin I get the following error:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img.md5
<ID:0/011> NAND Write Start!!
<ID:0/011> recovery.img.md5
<ID:0/011> system.img.md5
<ID:0/011> __XmitData_Read ..
<ID:0/011> XmitData Fail..
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have searched the net and unable to get any related issues, please help.
Click to expand...
Click to collapse
Are you sure you are flashing the right ROM for your device?
I9100?
If yes:
Try this and/or this(unbranded 4.0.3 recommended).
So I just got a Galaxy Note II SCH-i605 (Verizon) and decided to root the phone. Unfortunately, I didn't unlock the bootloader before flashing the rom and the phone is currently soft bricked. No problem, before I started I had downloaded the stock rom from samsung-updates.com for the make and model of my phone. I begin to reflash the stock rom and about 10% in Odin displays an error and stops flashing the new rom. I attempted to download roms from other places for my phone but they all stop at the same spot when flashing (including the one found here).
Could someone kindly tell me what I'm doing wrong?
This is what the message log is displaying:
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'd go try and flash imnuts stock rom and follow the instructions to get back fully to stock. It is in the original dev section.
http://forum.xda-developers.com/showthread.php?p=34891181
Section 1b. Make sure you follow the steps for people in the L4 OTA. Your phone is failing at writing sboot because the new ota blocks that
Sent from the dark on a Note 2
kintwofan said:
http://forum.xda-developers.com/showthread.php?p=34891181
Section 1b. Make sure you follow the steps for people in the L4 OTA. Your phone is failing at writing sboot because the new ota blocks that
Sent from the dark on a Note 2
Click to expand...
Click to collapse
It's weird, I just tried reflashing the rooted OS and this time it wiped the old image completely and is working fine now. I really hate the "magically fixes itself" solution. Because I don't exactly learn anything from it. However thanks for the information because I'll be sure to note that before trying anything else.
SailorDeath said:
So I just got a Galaxy Note II SCH-i605 (Verizon) and decided to root the phone. Unfortunately, I didn't unlock the bootloader before flashing the rom and the phone is currently soft bricked. No problem, before I started I had downloaded the stock rom from samsung-updates.com for the make and model of my phone. I begin to reflash the stock rom and about 10% in Odin displays an error and stops flashing the new rom. I attempted to download roms from other places for my phone but they all stop at the same spot when flashing (including the one found here).
Could someone kindly tell me what I'm doing wrong?
This is what the message log is displaying:
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Just try flashing only the PIT file, it worked for me just by re partitioning it.
Thanks in advance for the help!
Can you get to Download Mode?
yes
Can you get into Recovery? If so, custom (version>) or stock?
yes. I just flashed twp on it. I can change this if needed.
What version of the software / firmware WERE you on?
I was on 4.4.2 OTA stock from tmobile but I did root it and had it rooted and running fine for 6+ months without issue.
What did you do to cause it to soft brick?
I have been getting prompted for an OTA update for a while and kept putting it off for fear of knox and the unknown behavior of me having it rooted. I then let my wife use my phone and she clicked approve for the update. The phone then, according to her, rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods found online that seemed straight forward (flash custom recovery, install new rom, or install Samsung approved stock rom, delete cache, etc), all my errors seem to be directed to the PIT according to google searches I have done. at this point I can acknowledge I am out of my depth and have no idea where to go next.
Model: SGH-M919
Model name: GALAXY S4
Country: USA (T-Mobile)
PDA: M919UVUFNH7
What versions of the software / firmware have you tried?
4.2.2, 4.4.2, 4.4.4 all from Samsung site.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT" and the google walk throughs suggested trying new PIT files.
What errors are you having?
from which location? odin or the device?
from the device:
secure check fail: PIT
from odin:
big red FAIL in the first box. message output is below.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
toosweetnitemare said:
Thanks in advance for the help!
Can you get to Download Mode?
yes
Can you get into Recovery? If so, custom (version>) or stock?
yes. I just flashed twp on it. I can change this if needed.
What version of the software / firmware WERE you on?
I was on 4.4.2 OTA stock from tmobile but I did root it and had it rooted and running fine for 6+ months without issue.
What did you do to cause it to soft brick?
I have been getting prompted for an OTA update for a while and kept putting it off for fear of knox and the unknown behavior of me having it rooted. I then let my wife use my phone and she clicked approve for the update. The phone then, according to her, rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods found online that seemed straight forward (flash custom recovery, install new rom, or install Samsung approved stock rom, delete cache, etc), all my errors seem to be directed to the PIT according to google searches I have done. at this point I can acknowledge I am out of my depth and have no idea where to go next.
Model: SGH-M919
Model name: GALAXY S4
Country: USA (T-Mobile)
PDA: M919UVUFNH7
What versions of the software / firmware have you tried?
4.2.2, 4.4.2, 4.4.4 all from Samsung site.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT" and the google walk throughs suggested trying new PIT files.
What errors are you having?
from which location? odin or the device?
from the device:
secure check fail: PIT
from odin:
big red FAIL in the first box. message output is below.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This typically would be an easy fix, but if 4.4.4 official doesn't straighten it out, it could be a big pain, most likely owing to the fact that you tried to run 4.2.2 on a phone that has had the official 4.4.2 version installed and/or the fact that you were messing with Pits for some reason. Downgrading newer Samsungs, especially since 4.3, is typically not recommended and in most instances is a really bad idea.
es0tericcha0s said:
This typically would be an easy fix, but if 4.4.4 official doesn't straighten it out, it could be a big pain, most likely owing to the fact that you tried to run 4.2.2 on a phone that has had the official 4.4.2 version installed and/or the fact that you were messing with Pits for some reason. Downgrading newer Samsungs, especially since 4.3, is typically not recommended and in most instances is a really bad idea.
Click to expand...
Click to collapse
Thank you for the information. That explains a lot.
Any suggestions to move forward? Thanks!
toosweetnitemare said:
Thank you for the information. That explains a lot.
Any suggestions to move forward? Thanks!
Click to expand...
Click to collapse
Have you tried 4.4.4 yet? If so, and it didn't work, please explain in detail what the error was or where it failed.
es0tericcha0s said:
Have you tried 4.4.4 yet? If so, and it didn't work, please explain in detail what the error was or where it failed.
Click to expand...
Click to collapse
yes I just tried M919UVUFNH7_M919TMBFNH7_TMB. Attached is a screenshot of odin. below is the output from odin.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
when turning on the phone without booting into recovery or download mode, I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I have tried recovery mode in Kies and it does not detect my device.
the little text in the upper left hand corner of the screen says:
odin mode
product name: sgh-m919
current binary: samsung official
system status: custom
knox kernel lock: 0x0
knox warrenty void: 0x1
cso-config-lsb:0x30
write protection enabled:
emmc burst mode enabled
Click to expand...
Click to collapse
entering download mode I get the same little text in the upper left corner of the screen as when just booting the device. The message in the middle of the screen has changed to "Downloading... Do not turn off target!!"
when I try to push the img for 4.4.4 while in download mode, I get the output from odin that I pasted above and the text in the upper left hand corner of the screen has been appended to state:
odin mode
product name: sgh-m919
current binary: samsung official
system status: custom
knox kernel lock: 0x0
knox warrenty void: 0x1
cso-config-lsb:0x30
write protection enabled:
emmc burst mode enabled
start [224, 1448]
bar [240, 1440]
Click to expand...
Click to collapse
and the blue loading bar has stopped moving.
please let me know if there is anything else I can give you for information. Thank you for looking into this with me.
It's odd that it fails after trying to do the recovery. I'd see if maybe I could find the stock recovery and just flash that and then attempt the full Odin restore afterwards. But I wanna say it's because of messing around with the Pit.
I think at this point, your options are:
Find a debrick img for your current firmware (or find someone with a rooted Tmo S4 on the same update and you can make one from it, and follow the basic guide here:
http://forum.xda-developers.com/showthread.php?t=2369125
while substituting the correct files for your phone.
OR, you'll need a JTAG service.
That's what I was afraid of. Thanks for the info.
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
toosweetnitemare said:
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
Click to expand...
Click to collapse
Interesting find. Can't imagine why that would be the trick. Every time I've ever used Odin (on many dozens of Samsungs), it's always been recommended to check that for a full update. Thanks for sharing in case I, or another member has the same thing happen.
Wait, .tar or like the system.img?
toosweetnitemare said:
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
Click to expand...
Click to collapse
Can you post the .IMG here please? im running through same issue.
es0tericcha0s said:
It's odd that it fails after trying to do the recovery. I'd see if maybe I could find the stock recovery and just flash that and then attempt the full Odin restore afterwards. But I wanna say it's because of messing around with the Pit.
I think at this point, your options are:
Find a debrick img for your current firmware (or find someone with a rooted Tmo S4 on the same update and you can make one from it, and follow the basic guide here:
http://forum.xda-developers.com/showthread.php?t=2369125
while substituting the correct files for your phone.
OR, you'll need a JTAG service.
Click to expand...
Click to collapse
Just for info. the Model: SGH-M919 will not boot from the SD card, Even if you have the correct debrick.img that was made from the same device.