Hi!
This is my device what I bricked:
Samsung SM-J500F/DS
Here is what Idid:
Rooted the device and everything was fine until I flashed with SlimROM for SM-J500F Nougat 7.1.2.
The device did not started anymore.
Now, I downloaded from Samsung web site a stock ROM this:
J500FXXU1BQH1_J500FOXX1BQG2_XEH
After this flash the phone started but had no network and some error popped up.
I decide to reset to factory, but that didn't solved the problem, what I actually expected.
The I was realized does maybe I messed up and interchanged the downloaded rom, and I flashed my phone with
a wrong baseband version and now the fon can not start, but I get a message on the screen:
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I was trying with Smart Switch software, but the app can not start the flashing cos it gives me an error something like "unknown device attached" or similar.
Odis can recognize the phone but can not flash the device. It hung at "Get PIT for mapping" but some time on some other point.
Probably I messed up accidentally when I was flashed my phone with the wrong version of stock rom.
I didn't checked before what was my original baseband version.
What can i do now?
I searched for a rom for my phone with dual sim but I can't find any, even on the official Samsung site.
Is it ok if I flash my SM-J500F/DS with the rom of SM-J500F? without the DS .
Tanks for any suggestion and/or help.
At the moment I got this error from Odin"
<ID:0/015> Added!!
<ID:0/015> Odin engine v(ID:3.1401)..
<ID:0/015> File analysis..
<ID:0/015> Total Binary size: 2053 M
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> NAND Write Start!!
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> __XmitData_Write
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/015> Removed!!
My best regards.
Problem solved.
Flashed back to a lover version of ROM and then updated to the actual stock ROM.
Now everything is fine.
jodank said:
Problem solved.
Flashed back to a lover version of ROM and then updated to the actual stock ROM.
Now everything is fine.
Click to expand...
Click to collapse
Hi,
Where can I download the TWRP for that model?
For you what is the best rom for it?
Thanks in advance and best regards,
P.A
Related
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.
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...
Hello,
I borrowed my roommates Verizon S4 (SCH-I545) and I soft-bricked it. I had a different carrier and needed to root/unlock it, and after a day I was unable to send texts or use data, so I tried to install a recovery to flash a ROM.
However, once I tried to install a recovery, it would not longer boot and would say "Software Update Failed" and it tells me to use the Verizon Software Repair Assistant.
So, I tried using Odin to flash the stock, but I ran into trouble because this phone is on 5.0.1. On Odin, I would have the COM marker light up yellow, so I know the phone was at least recognized.
I also tried to find a Verizon Repair exe file (using windows), and I think I found one for Samsung, but it does not recognize the device being connected (even though Odin does)
Is there anything I can do to save this phone and return it to my roommate?
Fail Log:
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
shivpaulchadha said:
Hello,
I borrowed my roommates Verizon S4 (SCH-I545) and I soft-bricked it. I had a different carrier and needed to root/unlock it, and after a day I was unable to send texts or use data, so I tried to install a recovery to flash a ROM.
However, once I tried to install a recovery, it would not longer boot and would say "Software Update Failed" and it tells me to use the Verizon Software Repair Assistant.
So, I tried using Odin to flash the stock, but I ran into trouble because this phone is on 5.0.1. On Odin, I would have the COM marker light up yellow, so I know the phone was at least recognized.
I also tried to find a Verizon Repair exe file (using windows), and I think I found one for Samsung, but it does not recognize the device being connected (even though Odin does)
Is there anything I can do to save this phone and return it to my roommate?
Click to expand...
Click to collapse
Do you know what baseband version is on the phone? When Odin initially failed for me it was because the phone was running 5.0.1 and I tried installing the earliest software. Then I downloaded the newest firmware (OF1) and flashed it successfully.
Snowby123 said:
Do you know what baseband version is on the phone? When Odin initially failed for me it was because the phone was running 5.0.1 and I tried installing the earliest software. Then I downloaded the newest firmware (OF1) and flashed it successfully.
Click to expand...
Click to collapse
can u give me the link Firmware OF1 pls :'(
AnggaKun said:
can u give me the link Firmware OF1 pls :'(
Click to expand...
Click to collapse
Turns out I could not find the firmware on here to download so I went too the site SamMobile and performed the painfully slow download from there
Snowby123 said:
Turns out I could not find the firmware on here to download so I went too the site SamMobile and performed the painfully slow download from there
Click to expand...
Click to collapse
when im download at sammobile, the file when im wanna ekstract it always corrupt file
help me im got bootloop on of1, can if im try instal oc1 firmware?:good:
AnggaKun said:
when im download at sammobile, the file when im wanna ekstract it always corrupt file
help me im got bootloop on of1, can if im try instal oc1 firmware?:good:
Click to expand...
Click to collapse
Installing an older firmware likely will fail. Moreover, your download was likely incomplete. That is the most common cause of the file being labeled corrupt. There are other sites you could find the firmware , but the other sites have a weaker reputation
Snowby123 said:
Installing an older firmware likely will fail. Moreover, your download was likely incomplete. That is the most common cause of the file being labeled corrupt. There are other sites you could find the firmware , but the other sites have a weaker reputation
Click to expand...
Click to collapse
im trying to flash.. but stuck
log odin
[/COLOR]<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.1101)..
<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> aboot.mbn
stuck in there
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