Last night I was trying to flash a custom rom on 5.0 or 5.1 lollipop(i forgot) on safestrap from 4.4.2 kitkat. But after doing so, and going through the flash menu, I then rebooted and the samsung boot logo came up and froze. It then rebooted itself and goes into recovery mode.
And while in recovery mode, the info in the left corner said that the version was
I545VRUFNK4.
Also I have tried flashing back to the stock rom and This is the error I get when I flash my the MJ7 stock rom(Or pretty much any other stock rom I've tried for i545)
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After trying and trying to fix it, the screen eventually goes into the "This firmware upgrade has encountered an issue. Please select recovery mode in kies and try again."
I've been looking for answers all day and last night but I haven't been able to find one. Recently, what I've found is that theres a possibility that I'm stuck in the NK4 bootloader or something? and that I need to flash that same firmware on the same version im on? sorry if I don't know that much.
I really need help fixing this because I've tried so much and I would love to hear some of your guys advice. Thanks.
nvm sike i fixed it lolz
Jtieu said:
nvm sike i fixed it lolz
Click to expand...
Click to collapse
Yeah but i have the same issue, how did you do it? lol i hope its not too obvious...
Related
So, I was attempting to root my Sprint Galaxy s3, using the CF-root 6.3 via Odin v1.85. All was going well, then just before the big finale, Odin crashes. Now my firmware is messed up on my new phone. I can get back into Downloading... mode, but if I try to re-flash with cf-root, I get this in Odin:
<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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And this on the phone:
Unsupport dev_type.
And when I reboot:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Is my phone bricked? How can I undo this?
Thanks.
If this is in the wrong section, I apologize.
Did you try root your US sprint s3 with a method for the international s3?
If so then search because someone made that same mistake last night.
In future don't flash anything for the inter national version on your American version.
Sent from my GT-I9300 using xda premium
I seem to have fixed it. Used Odin to install the clockwork mod, and the phone boots up normally now. Close call.
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.
Hi Devs,
I am stuck in a issue. I installed cm 12.0 (unofficial rom) to my Galaxy s3 GT-i9300 everything was working fine but suddenly it keeps on crashing randomly one day while calling my phone froze. I restarted the phone it stucked on SAMSUNG BOOT SCREEN.
I can go into download mode and recovery mode, currently using PhilzTouch 6 on recovery.
Things I have tried already.
Wiped Cache Partition
Wiped Data/Factory Reset
when i try to wipe cache or factory reset i get errors
E: can't mount /data or Formatting /sdcard/.android_secure
For some reason my phones internal memory is on the read only mode i tried to flash the stock rom as well so far no luck.
I tried 4 different stock roms none of them work they all stopped on nand write or setup connection
I followed the instruction below because thats what exactly happened to my phone but no luck when ever i try to load boot files into PDA it keeps failing.
http://forum.xda-developers.com/showthread.php?t=1840030
please guys i am tired and exhausted trying all different stuff guide me. I even tried PIT Files noting work. Thanks in advance
Try going back to stock/factory.
Boot in download mode (vol down+home+power).
Use Odin to flash stock recovery and firmware.
Once you are able to boot perfectly into touchwiz, can narrow down your points of failure and try again or try another ROM
blu88 said:
Try going back to stock/factory.
Boot in download mode (vol down+home+power).
Use Odin to flash stock recovery and firmware.
Once you are able to boot perfectly into touchwiz, can narrow down your points of failure and try again or try another ROM
Click to expand...
Click to collapse
Hi Blue,
Thanks for reply , so you meant to say i replace philztouch with stock recovery.
Correct me if i am wrong.
Replace philz with stock recovery and replace your rom with touchwiz. Figure out where you went wrong and then flash your custom rom again or flash a different custom rom.
Try flashing another recovery. Worked for me once
Thanks for Help
Can you send me link for GT-i9300 International Stock Recovery so i am installing exact thing it would be great help from you guys and i would really appreciate it.
blu88 said:
Replace philz with stock recovery and replace your rom with touchwiz. Figure out where you went wrong and then flash your custom rom again or flash a different custom rom.
Click to expand...
Click to collapse
Hi Blue i tried official recovery this what comes up and get fails
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
its problem with internal memory to read only is there any way to change it read write mod.
saqygee said:
Hi Blue i tried official recovery this what comes up and get fails
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
its problem with internal memory to read only is there any way to change it read write mod.
Click to expand...
Click to collapse
saqyee, you placed the stock recovery file in the PDA section right? DO NOT TOUCH THE PIT SECTION.
saqygee said:
Hi Blue i tried official recovery this what comes up and get fails
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
its problem with internal memory to read only is there any way to change it read write mod.
Click to expand...
Click to collapse
Nand write fail usually means emmc corrupt/damaged you could try the rescue firmware but this looks like hardware failure.
Sent from my LG-D855 using Tapatalk
Getting this error after trying to install a custom rom which didnt work , now trying to install the stock rom and in download mode , using odin 3.10.7 with the G925I firmware (from Australia however have had to download the indian international firmware)
odin keeps telling me its failed , is my phone stuffed or can I do something to get it back to the stock rom so I Can try a custom rom again?
Thanks in advance for the help!
<ID:0/006> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Sboot.bin is bootloader. You are flashing a firmware with incorrect bootloader or old bootloader should i say.
Is your phone network locked?
http://www.sammobile.com/firmwares/download/107097/G925IDVS3EPJ6_G925IXSA3EPGG_XSA/
Try to flash this.
Was you rooted before you tried to flash custom rom?
perfect thanks mate , that rom worked and everythings good!
s3lkies said:
perfect thanks mate , that rom worked and everythings good!
Click to expand...
Click to collapse
No problem mate. If you are flashing a custom rom you need to root first and flash twrp. If you need help let me know mate
Very simple and hard for me at the same time
Flashed twrp on my galaxy s6edge 925f and that was the only thing i did so far, after 1st reboot it started up, but on second time i tryed to restart phone and wiped system (think ) becouse it ways i dont have os installed, it stuck at samsung logo, smartswtich neither kies recognizes my phone (yes drivers are installed) have downloaded stock firmware and tryed to flash it via odin, but..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed
ok with odin 3.12 i have this error
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can please anyone help me out?
managed somehow make it to work, cloes please
if you have samsung kies also installed on your comp it wont work....
I have this problem , can you explain how you fixed it?
aryaazimi72 said:
I have this problem , can you explain how you fixed it?
Click to expand...
Click to collapse
If you have sboot.bin fail this happens when you try to downgrade. Just flash stock firmware through odin. Use odin v3.10.6. Of it sticks on Samsung logo it's normal can take up to 20 minutes for first boot
callumbr1 said:
If you have sboot.bin fail this happens when you try to downgrade. Just flash stock firmware through odin. Use odin v3.10.6. Of it sticks on Samsung logo it's normal can take up to 20 minutes for first boot
Click to expand...
Click to collapse
I dont think i am downgrading... im flashing a bl from a new rom but i had an old rom before this...
I have these errors :
aryaazimi72 said:
I dont think i am downgrading... im flashing a bl from a new rom but i had an old rom before this...
I have these errors :
Click to expand...
Click to collapse
Which rom are you on? And which BL are you flashing?
callumbr1 said:
Which rom are you on? And which BL are you flashing?
Click to expand...
Click to collapse
i tried crisscross and xtrestolite...
now im downloading omega.. maybe that workes...
aryaazimi72 said:
i tried crisscross and xtrestolite...
now im downloading omega.. maybe that workes...
Click to expand...
Click to collapse
Crisscross development has stopped. I recommend CarHD rom it is the best by far.
Make sure your flashing the roms through twrp