Database Users

[Q] Bricked Galaxy Tab 4 7.0 Stuck in Odin

Hello everyone! Its been a while since my rooting days(HTC ONE) and I'm a bit if not very rusty . I recently bought a Galaxy Tab 4 7.0. I attempted a root process through Odin and of course...it failed. Now I am stuck in the download mode and no matter what combination of buttons I use it returns there. I tried to see if I can get the original firmware through samfirmware.com for t230NU but to no avail. Any suggestions? I'd really appreciate it as I need the tablet. :fingers-crossed:

[email protected] said:
Hello everyone! Its been a while since my rooting days(HTC ONE) and I'm a bit if not very rusty . I recently bought a Galaxy Tab 4 7.0. I attempted a root process through Odin and of course...it failed. Now I am stuck in the download mode and no matter what combination of buttons I use it returns there. I tried to see if I can get the original firmware through samfirmware.com for t230NU but to no avail. Any suggestions? I'd really appreciate it as I need the tablet. :fingers-crossed:
Click to expand...
Click to collapse
stock firmware
http://forum.xda-developers.com/showthread.php?t=2778374
root
http://forum.xda-developers.com/showpost.php?p=53020637&postcount=87

Android Terminal Emulator cant find mrw
ShinySide said:
stock firmware
http://forum.xda-developers.com/showthread.php?t=2778374
root
http://forum.xda-developers.com/showpost.php?p=53020637&postcount=87
Click to expand...
Click to collapse
Thank you ShinySide for all your help! I was able to root successfully however when I try to replace vroot with Superuser with the terminal its unable to find the mrw file. I did extract and place the folder to the internal storage. I tried putting the file on the sdcard and that did not work either. What i ended up doing was downloading Superuser from the playstore. Will this have the same effect and will it update the binary correctly? My last question is-My Tab4 is says its a model T230NU but when i registered it n Samsung it shows SM-T230NZWAXAR...will the stock firmware conflict since the build is T230NUUEUOANE2?
Sorry for all the newb questions. I'm so glad I was able to unbrick my device and root though...Thank you so much!

[email protected] said:
Thank you ShinySide for all your help! I was able to root successfully however when I try to replace vroot with Superuser with the terminal its unable to find the mrw file. I did extract and place the folder to the internal storage. I tried putting the file on the sdcard and that did not work either. What i ended up doing was downloading Superuser from the playstore. Will this have the same effect and will it update the binary correctly? My last question is-My Tab4 is says its a model T230NU but when i registered it n Samsung it shows SM-T230NZWAXAR...will the stock firmware conflict since the build is T230NUUEUOANE2?
Sorry for all the newb questions. I'm so glad I was able to unbrick my device and root though...Thank you so much!
Click to expand...
Click to collapse
Post the exact terminal output. You shouldnt have any issue
Theres 2 model numbers. One for the white one for the black. Your tab 4 is SM-T230NZWAXAR which is the white one. SM-T230NYKAXAR is the blacks model number. It doesnt matter which you have its the same firmware. Samsung is just reading your full model number,

hi, iam the same problem, just 3 days ago my tab 4 7" (white) was stuck in a blacl screen with a yellow triangle, said: firmware upgrade encountered an issue, please select recovery mode in kies & try again.
The problem here is i cant enter in DOWNLOAD mode, in other tutorials said, for cellphones, that i need to put over the battery, but, in a tablet, how can i do this? i download a firmware from sammobile, my model number said SM-T230NU , i cant find the american version (i purchase this in radioshack USA) but i downlod the mexican version of Telcel, but nothing, OdIn always find an error, watch:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
THIS IS ANOTHER try:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please i need help.
and about the post of ShinySide (http://forum.xda-developers.com/showthread.php?t=2778374 ) what is the diference about NE2 firmware and ND9 firm?

nismo87 said:
hi, iam the same problem, just 3 days ago my tab 4 7" (white) was stuck in a blacl screen with a yellow triangle, said: firmware upgrade encountered an issue, please select recovery mode in kies & try again.
The problem here is i cant enter in DOWNLOAD mode, in other tutorials said, for cellphones, that i need to put over the battery, but, in a tablet, how can i do this? i download a firmware from sammobile, my model number said SM-T230NU , i cant find the american version (i purchase this in radioshack USA) but i downlod the mexican version of Telcel, but nothing, OdIn always find an error, watch:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
THIS IS ANOTHER try:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
please i need help.
and about the post of ShinySide (http://forum.xda-developers.com/showthread.php?t=2778374 ) what is the diference about NE2 firmware and ND9 firm?
Click to expand...
Click to collapse
Your problem is you are trying to flash the wrong firmware. Youre trying to flash a firmware meant for data/service enabled tabs. Check my first post in this thread. Flash one of those.
Just bug/kernel fixes.
btw if youre seeing that message, you are in download mode.

Cant find mrw file
ShinySide said:
Post the exact terminal output. You shouldnt have any issue
Theres 2 model numbers. One for the white one for the black. Your tab 4 is SM-T230NZWAXAR which is the white one. SM-T230NYKAXAR is the blacks model number. It doesnt matter which you have its the same firmware. Samsung is just reading your full model number,
Click to expand...
Click to collapse
i have tried several times and still the same result. I get this message and then the tablet reboots. The Superuser app I downloaded from the Playstore did update the binary and all. However i would like to know what I did wrong for future reference with the mrw file. Thanks!

ShinySide said:
Your problem is you are trying to flash the wrong firmware. Youre trying to flash a firmware meant for data/service enabled tabs. Check my first post in this thread. Flash one of those.
Just bug/kernel fixes.
btw if youre seeing that message, you are in download mode.
Click to expand...
Click to collapse
thanks for the answer, but, excuse about my question, in u`r post about the firmwares, i just download this: Latest Firmware Version Download NE2, (the first link posted) but said me the same message in odin, (FAIL) i dont know if the options in ODIN are bad, i choose auto rebot and F.Reset Time.
or, need i erase the termination md5 with only .tar?

[email protected] said:
i have tried several times and still the same result. I get this message and then the tablet reboots. The Superuser app I downloaded from the Playstore did update the binary and all. However i would like to know what I did wrong for future reference with the mrw file. Thanks!
Click to expand...
Click to collapse
Do a search for each of those file names and give me the exact file names and locations. Someone else mentioned on another thread they had to ediit the script because they were a little different for some reason for them.
nismo87 said:
thanks for the answer, but, excuse about my question, in u`r post about the firmwares, i just download this: Latest Firmware Version Download NE2, (the first link posted) but said me the same message in odin, (FAIL) i dont know if the options in ODIN are bad, i choose auto rebot and F.Reset Time.
or, need i erase the termination md5 with only .tar?
Click to expand...
Click to collapse
Na those options wouldnt matter. That first time you flashed, loke_1st.bin flashed successfully then loke_2nd.bin failed. You might need to find a pit file for the tab 4 7inch and re-partition the device. Only one tho.... to get the pitfile you need hiemdall and hiemdall isnt compatible with the tab 4. least not yet. I saw a post a while ago for creating a pitfile on a device. Let me see if I can find it and see if itll work on my tab and create one and Ill post it if I can find it and create one
Okay this is all i can find. Just one issue...I have straight linux and no windows on my pc so I cant use or try to use it to get the pit, so 2 options if you want to try repartitioning it, try using this tool in download mode or find someone with windows willing to try to get the pitfile from their device
http://forum.xda-developers.com/galaxy-s2/orig-development/tool-updated-09-06-14-efs-professional-t1308546

ShinySide said:
Na those options wouldnt matter. That first time you flashed, loke_1st.bin flashed successfully then loke_2nd.bin failed. You might need to find a pit file for the tab 4 7inch and re-partition the device. Only one tho.... to get the pitfile you need hiemdall and hiemdall isnt compatible with the tab 4. least not yet. I saw a post a while ago for creating a pitfile on a device. Let me see if I can find it and see if itll work on my tab and create one and Ill post it if I can find it and create one
Click to expand...
Click to collapse
OK, thanks for the support, i will considering make a donation for this $$
so, in conclusion, iam really ina hole with this issue, no? i dont know how i can get brick in this form my tablet, only 3 weeks with it and is stuck...
i dont know much about this and samsung devices, but, need i another file apart of the firmware? the Pit file?

nismo87 said:
OK, thanks for the support, i will considering make a donation for this $$
so, in conclusion, iam really ina hole with this issue, no? i dont know how i can get brick in this form my tablet, only 3 weeks with it and is stuck...
i dont know much about this and samsung devices, but, need i another file apart of the firmware? the Pit file?
Click to expand...
Click to collapse
Check my previous post. I had just edited while you were responding Haha I have the donation link up because some people asked if I had one when I was compiling Carbon for s4's. I never accept them tho so its just there for "show" Ahaha
Its just one file. Contains all the partition block sizes, names, etc etc and willl delete everything and repartition the devices partitions, etc etc
Im guessing the loke bins are the bootloader. And since one flashed for you, it might be failing at a check point.

ShinySide said:
Check my previous post. I had just edited while you were responding Haha I have the donation link up because some people asked if I had one when I was compiling Carbon for s4's. I never accept them tho so its just there for "show" Ahaha
Its just one file. Contains all the partition block sizes, names, etc etc and willl delete everything and repartition the devices partitions, etc etc
Im guessing the loke bins are the bootloader. And since one flashed for you, it might be failing at a check point.
Click to expand...
Click to collapse
Hi again Shinyside,
today was a great day for my tablet jeje, its ALIVE again¡¡¡¡¡¡
what i made?
Just desinstall KIES, and reboot the Pc, install again the drivers for samsung, after, download again the Original firmware from your Link ( chrome://mega/content/secure.html#!I49V3YZB!LkqiYAvZF0dyL0YMbVMGlGWIhn7BQbFi84z4CIFQhKw
i downoad again because, sometimes in large files, the download is corrupted for X reason, unzip this in desktop (i dont know if this is good or not).
the next step was plug to charge for 1 hrs the tab 4, with the black screen turn on, Open Odin 3.07 , wait 2 minutes and upload the ND5 file previous downloaded, plug the TAB 4 in the Pc with (this is important) the OEM cable, i was plugin with other micro usb in the past attempted, so, just when Odin finish to charge 100% the firmware, just press START and wait a couple of minutes, the tablet autoreboot and now is alive.
but... i dont know but when my tab turn on again, all apps, pictures,etc was there so, i dont know if my tablet only was bricked temporarily or not completely bricked..... i dont know, only know that i have a tab again and thanks Shinyside for all support.
So, your link about donation is working or not? i want to invite u a beer, minimum :silly:
i want leave the Odin record about this, if anybody have the same problem:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> param.lfs
<ID:0/003> DTim.Primary
<ID:0/003> DTim.Recovery
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> NVM.img
<ID:0/003> cache.img

nismo87 said:
Hi again Shinyside,
today was a great day for my tablet jeje, its ALIVE again¡¡¡¡¡¡
what i made?
Just desinstall KIES, and reboot the Pc, install again the drivers for samsung, after, download again the Original firmware from your Link ( chrome://mega/content/secure.html#!I49V3YZB!LkqiYAvZF0dyL0YMbVMGlGWIhn7BQbFi84z4CIFQhKw
i downoad again because, sometimes in large files, the download is corrupted for X reason, unzip this in desktop (i dont know if this is good or not).
the next step was plug to charge for 1 hrs the tab 4, with the black screen turn on, Open Odin 3.07 , wait 2 minutes and upload the ND5 file previous downloaded, plug the TAB 4 in the Pc with (this is important) the OEM cable, i was plugin with other micro usb in the past attempted, so, just when Odin finish to charge 100% the firmware, just press START and wait a couple of minutes, the tablet autoreboot and now is alive.
but... i dont know but when my tab turn on again, all apps, pictures,etc was there so, i dont know if my tablet only was bricked temporarily or not completely bricked..... i dont know, only know that i have a tab again and thanks Shinyside for all support.
So, your link about donation is working or not? i want to invite u a beer, minimum :silly:
i want leave the Odin record about this, if anybody have the same problem:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> param.lfs
<ID:0/003> DTim.Primary
<ID:0/003> DTim.Recovery
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> NVM.img
<ID:0/003> cache.img
Click to expand...
Click to collapse
Sweet good deal man. Glad you got iit back up and running. I didn't even think about the cable. We an issue with using some different usb cables on the s4 too. But glad you got it back up and running. And yeah it works

the next step is, how to root my tab 4......

nismo87 said:
the next step is, how to root my tab 4......
Click to expand...
Click to collapse
Check post 2

ShinySide said:
Check post 2
Click to expand...
Click to collapse
Hope this is ok area to post this in. I am having a problem with Tab 4 T230NU wifi only. I am trying to get to download mode to flash with Odin, but I can not? It flashes on with screen. "Firmware Upgrade encountered an error an issue. Please select recovery mode in Kies & try again. " It just flashes then turns back on... I tried holding home and volume up. Home and volume down. home and volume up and down in the middle. I tried volume up, volume down. I have charged this for quite a while also, few hours. I also have a Jig that works with the s3 to go to download mode, that did not work.
I think if I can get to download mode I can get working again, but have not been able to get to that. Any help please? Thank you in advance.

jaredlappa said:
Hope this is ok area to post this in. I am having a problem with Tab 4 T230NU wifi only. I am trying to get to download mode to flash with Odin, but I can not? It flashes on with screen. "Firmware Upgrade encountered an error an issue. Please select recovery mode in Kies & try again. " It just flashes then turns back on... I tried holding home and volume up. Home and volume down. home and volume up and down in the middle. I tried volume up, volume down. I have charged this for quite a while also, few hours. I also have a Jig that works with the s3 to go to download mode, that did not work.
I think if I can get to download mode I can get working again, but have not been able to get to that. Any help please? Thank you in advance.
Click to expand...
Click to collapse
You are in download mode

Help!
Okay so I've been trying to root my Galaxy Tab 4 and everything I attempt fails, its stuck on ODIN mode and I cant seem to root it, recover it or anything. I need help

Devon S said:
Okay so I've been trying to root my Galaxy Tab 4 and everything I attempt fails, its stuck on ODIN mode and I cant seem to root it, recover it or anything. I need help
Click to expand...
Click to collapse
D,
while in odin reflash your custom recovery for your device with auto/restart checked.
odin will remain stuck in that mode until it restarts after successfully flashing an image.
m

This worked for me I was in soft brick I don't know if this will for you
1.download Odin v3
2.download twrp (sm-t230)
3.connect your tab to your PC and turn it on (make sure you have drivers installed)
4.you should see ADDED! ON ODIN (if you don't see it you probably didn't install the drivers correctly) click PDA and select the twrp rar file 5.wait for it to flash it (your tab may or may not reboot wait for Odin to say done or succeeded)
6.download a stock ROM for your tab
7.move the stock ROM onto a SD card
8.put SD card into tablet and mount it
9.tap install and look for the stock ROM
10.you may need to clear dalvik cache and/or data
I hope it helped. Pm me if you need help were to get the drivers and the stock ROM I'll be glad to help!
Sent from my SM-T230 using XDA Free mobile app

[Q] 900V Odin Mode Loop - About to lose my mind

Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.
I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.
He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!
Thanks!

jmorehouse said:
Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.
I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.
He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!
Thanks!
Click to expand...
Click to collapse
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware with Odin so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.

ludeawakening said:
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.
Click to expand...
Click to collapse
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?

jmorehouse said:
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Click to expand...
Click to collapse
Tried flashing your stock rom and below is the output from Odin...
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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)

jmorehouse said:
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Click to expand...
Click to collapse
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.
And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.
---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------
jmorehouse said:
Tried flashing your stock rom and below is the output from Odin...
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117#none

ludeawakening said:
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.
And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.
---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers #
Click to expand...
Click to collapse
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Is it a factory cable? If it is redownload the file.

Yes sometimes the cable does make a difference. You can try downloading the file again, although, getting a bad download from XDA is pretty rare. I'm not familiar with Odin failing to flash a file. I've never had it happen to me.
Sent from my SM-G900V using XDA Free mobile app

jmorehouse said:
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is a stock cable. Installed the latest version of the drivers taken from Samsung Kies 3.2.14113.3 (2014-11-20) for Windows and got the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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)

I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?
Sent from my SM-G900V using XDA Free mobile app

ludeawakening said:
I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
That is correct. It shows it on COM3.

I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app

ludeawakening said:
I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Please and thank you. I am going to try and get another laptop to try it on.

jmorehouse said:
Please and thank you. I am going to try and get another laptop to try it on.
Click to expand...
Click to collapse
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.

jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.

ludeawakening said:
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.
Click to expand...
Click to collapse
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app

Savagerun said:
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. If I do step in to help, I'm the type that will not give up on someone until either the issue is solved, or it's deemed that there is a hardware issue or something and nothing can be done. I remember what it was like being lost on trying to do this stuff. I researched and studied for a long time on how Android works, so I might as well put all that gained knowledge to good use by helping people now. And that's what an awesome community like XDA does, we help each other.

jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.
If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19

ludeawakening said:
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.
If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19
Click to expand...
Click to collapse
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?

jmorehouse said:
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?
Click to expand...
Click to collapse
You can find a video in this thread http://forum.xda-developers.com/showthread.php?t=2784290
Sent from my SM-G900V using XDA Free mobile app

Bricked - Tried Everything, Please Help

Ok fellas, I'm definitely bricked here. I went to flash TWRP (before brick) and that's when it happened. Using Mac with VM Fusion, I'm able to flash my Samsung Tablet fine with this same machine fyi.
So if I just turn the phone on it goes the the Samsung Galaxy S5 initial screen and is stuck. (def no boot loop)
I've downloaded the stock firmware (yes it's the correct one) and all Odin's 3.07 - 3.10. (ran as administrator)
I've uninstalled \ reinstalled usb drivers several times, Kies is completely uninstalled.
The problem in ODIN (any version I use), is that I add the firmware, run it and get the same thing every time:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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)
Any ideas on how to fix this thing?

DirtDigler said:
Ok fellas, I'm definitely bricked here. I went to flash TWRP (before brick) and that's when it happened.
So if I just turn the phone on it goes the the Samsung Galaxy S5 initial screen and is stuck. (def no boot loop)
I've downloaded the stock firmware (yes it's the correct one) and all Odin's 3.07 - 3.10. (ran as administrator)
I've uninstalled \ reinstalled usb drivers several times, Kies is completely uninstalled.
The problem in ODIN (any version I use), is that I add the firmware, run it and get the same thing every time:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<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)
Any ideas on how to fix this thing?
Click to expand...
Click to collapse
I hope you are using windows pc not mac, if using windows try in another pc or in your pc block antiviras temp.
Good luck

jdomadia said:
I hope you are using windows pc not mac, if using windows try in another pc or in your pc block antiviras temp.
Good luck
Click to expand...
Click to collapse
Yea I'm using VM Fusion on top of the Mac. It's actually flashing now when using a dedicated Windows box... that's just strange because I'm able to flash my Samsung 10.1 tablet fine with the VM Windows instance. Oh well. Lesson learned.

DirtDigler said:
Yea I'm using VM Fusion on top of the Mac. It's actually flashing now when using a dedicated Windows box... that's just strange because I'm able to flash my Samsung 10.1 tablet fine with the VM Windows instance. Oh well. Lesson learned.
Click to expand...
Click to collapse
Glade your problem solved.

DirtDigler said:
Yea I'm using VM Fusion on top of the Mac. It's actually flashing now when using a dedicated Windows box... that's just strange because I'm able to flash my Samsung 10.1 tablet fine with the VM Windows instance. Oh well. Lesson learned.
Click to expand...
Click to collapse
Can you boot in recovery by pressing and holding combination of buttons?

DirtDigler said:
Ok fellass
Click to expand...
Click to collapse
Next time ask your questions in Q&A that's what it's there for.

Hey guys... My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install cwm recovery. But cwm was not available for my device so i tried to flash cwm of some other device from the rom manager. It was of xolo q700.But now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device is qualcomm based so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
Sent from my XT1022 using XDA Free mobile app

verma_ayush said:
Hey guys... My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install cwm recovery. But cwm was not available for my device so i tried to flash cwm of some other device from the rom manager. It was of xolo q700.But now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device is qualcomm based so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
You realize that you are in a Samsung Galaxy s5 forum right? You will need to find information and files directly related to your specific phone.

verma_ayush said:
Hey guys... My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install cwm recovery. But cwm was not available for my device so i tried to flash cwm of some other device from the rom manager. It was of xolo q700.But now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device is qualcomm based so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
Click to expand...
Click to collapse
Try asking here, you're in the wrong place http://forum.xda-developers.com/showthread.php?t=2577489

Try jodin for mac.. Connect to different usb port... Make sure you have downloaded correct file...
Sent from my GT-I9300 using XDA Free mobile app

lingowistico said:
Try asking here, you're in the wrong place http://forum.xda-developers.com/showthread.php?t=2577489
Click to expand...
Click to collapse
Thankx buddy but that is not of much use. Everyone is just asking no has provided the solution for providing custom rom......lol. Thi device did'nt even have specific forum.

verma_ayush said:
Thankx buddy but that is not of much use. Everyone is just asking no has provided the solution for providing custom rom......lol. Thi device did'nt even have specific forum.
Click to expand...
Click to collapse
Yes, exactly. That's why that thread is the most appropriate for YOU. Because there is no dedicated forum for your phone. Or you can start a new thread in here http://forum.xda-developers.com/android/help . That's it. Good luck :good:

Deleted

[Q] Stuck while flashing stock rom I-9505

Hello. I tried to get back to official stock rom so I flashed my Galaxy S4 I-9505 with I9505XXUFNB8_I9505BTUFNB3_BTU and a pit file. the flashing starts but it suddenly stops and now my phone is bricked. PLEASE HELP!!! how do i get back to my official stock rom now?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_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> 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> 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> 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)

A little reading goes a long way
http://forum.xda-developers.com/showthread.php?t=2265477

DSA said:
A little reading goes a long way
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
I have followed this guide, any idea where might have I gone wrong?Because I have absolutely no clue I've flashed my device before but never had such issues.

ashekin.nahid said:
I have followed this guide, any idea where might have I gone wrong?Because I have absolutely no clue I've flashed my device before but never had such issues.
Click to expand...
Click to collapse
This happend coz you are trying to downgrade your device. Try to flash the latest firmware (only the firmware coz you don't need .pit file atm) for your device and you will see how it works ok

I have a similar problem, having tried with both I9505XXUHOJ2_I9505YXYHOK1_I9505XXUHOJ2_HOME.tar.md5 and I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2_HOME.tar.md5 (and not using a PIT file). I have tried multiple times, but I always get to the Samsung boot animation (white SAMSUNG, with a few animated blue stars moving away and fading - repeat) but it never gets any further - stuck. Any ideas please?

fjuniper said:
I have a similar problem, having tried with both I9505XXUHOJ2_I9505YXYHOK1_I9505XXUHOJ2_HOME.tar.md5 and I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2_HOME.tar.md5 (and not using a PIT file). I have tried multiple times, but I always get to the Samsung boot animation (white SAMSUNG, with a few animated blue stars moving away and fading - repeat) but it never gets any further - stuck. Any ideas please?
Click to expand...
Click to collapse
Did you wipe everything before flashing?
And are you sure it's the right rom for your phone? There was somebody who thought his phone was an I9500 (because that's what was written on the sticker under the battery) but it was actually an I9505.

GDReaper said:
Did you wipe everything before flashing?
And are you sure it's the right rom for your phone? There was somebody who thought his phone was an I9500 (because that's what was written on the sticker under the battery) but it was actually an I9505.
Click to expand...
Click to collapse
Yes, I wiped in TWRP before flashing the file in ODIN - ART / System / Data / Internal Storage / Cache. Not sure whether you mean that I should have, or shouldn't have!
Yes, it is a UK S4 i9505.

fjuniper said:
Yes, I wiped in TWRP before flashing the file in ODIN - ART / System / Data / Internal Storage / Cache. Not sure whether you mean that I should have, or shouldn't have!
Yes, it is a UK S4 i9505.
Click to expand...
Click to collapse
Why is there an md5 extension to the tar files? Firmwares should only have tar as extension as far as I know.

GDReaper said:
Why is there an md5 extension to the tar files? Firmwares should only have tar as extension as far as I know.
Click to expand...
Click to collapse
That is what was in the zip files from http://www.sammobile.com/firmwares/database/GT-I9505/
Exactly as I pasted in the earlier post. Both files of about 2.5GB. ODIN seemed fine with it and took them in the AP slot (ODIN 3.1.0.7). The Open filter includes *.md5, *.tar, *.smd etc.

[SOLVED] Bricked my Samsung Galaxy J5

I've completely bricked my Samsung Galaxy J5.
I've rooted my device with Odin using CF Autoroot. That went fine.
Then I went on and tried to install TWRP recovery with Odin. This went fine. Then I wanted to install CM 12.1. This ****ed up my phone. I forgot to enable developer options and OEM unlocking. Apparently this is something new since Android 5.1. NOT A SINGLE TUTORIAL MENTIONED THIS!!!
So back to stock firmware. It took 1 hour (!) and like 9000 ads (had to disable Adblock) to download the stock firmware. If you don't want to see adds and download full speed. Samsung must be run by a bunch of lomperds. Holy ****.
It finally downloaded and it seemed to work. Untill at the end:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXU1APC4_J500FNVFG1APC4_J500FNXXU1APC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the phone:
Code:
Volume Size is too big 143368 < 489600
ODIN: Invalid ext4 image
This appears to be a partition problem. So I tried to repartition with a random pit file I found on the internet (I guess Samsung really wants to loose customers). I got the next error:
Code:
Secure check fail: pit
Now I'm stuck. I can only get into download mode. Maybe I need a proper pit file?
Solution: Buy a real phone with linux support. Burn this one.

If you can get into download mode the phone is redoversble, did you ever make a nandroid backup that you can flash with Odin?
Sent from my SM-N910V using Tapatalk
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
(Recoverable)
Sent from my SM-N910V using Tapatalk

I had the same problem once. I don't remember much but what I did was :
Go into download mode by pressing volume down and power and home button.
Go into Odin and flash the latest version of the stock rom (go to sammobile website to download it).
Now reroot the phone using the latest chainfire root files(available on chainfire website).
Flash twrp 3.0.0 or any better version. Version 3 works best on my j500f.
Also if you are still getting the pit file error, it may be because of the corrupt tar file you are using in Odin. So download the latest rom from sammobile. If you still get the error, try rebooting your computer to see if it helps.
Goodluck!
Sent from my SM-J500F using XDA-Developers mobile app

Thanks for your replies.
Go into Odin and flash the latest version of the stock rom (go to sammobile website to download it).
Click to expand...
Click to collapse
That is what I did. It gives me next error:
Code:
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
Rebooting didn't fix the problem.
I think it is related to the fact that there is something wrong with the partitioning. If only Samsung would provide the right files to fix this...
I should have known that this process would fail since I had to install WINDOWS in order to work with Odin. Wtf?
I've rooted several HTC phones before without any problem. This is complete nonsense.
Samsung made too many mistakes imho. I'm not gonna spend another afternoon figuring out that I cannot fix my phone. I'm gonna send this phone where it came from and I'll probably buy a phone that has proper support. Maybe a Nexus.
Samsung never again.

TheOnlyRealChosenOne said:
Thanks for your replies.
That is what I did. It gives me next error:
Code:
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
Rebooting didn't fix the problem.
I think it is related to the fact that there is something wrong with the partitioning. If only Samsung would provide the right files to fix this...
I should have known that this process would fail since I had to install WINDOWS in order to work with Odin. Wtf?
I've rooted several HTC phones before without any problem. This is complete nonsense.
Samsung made too many mistakes imho. I'm not gonna spend another afternoon figuring out that I cannot fix my phone. I'm gonna send this phone where it came from and I'll probably buy a phone that has proper support. Maybe a Nexus.
Samsung never again.
Click to expand...
Click to collapse
Did you buy a new phone? If no, i know the solution

H3XabyT3LV said:
Did you buy a new phone? If no, i know the solution
Click to expand...
Click to collapse
Yes. Bought the Nexus 5X.
But maybe it's a good idea the post the solution anyway. Some users might be helped by it.

TheOnlyRealChosenOne said:
Yes. Bought the Nexus 5X.
But maybe it's a good idea the post the solution anyway. Some users might be helped by it.
Click to expand...
Click to collapse
Refund it and follow my steps -
If you remember ur model number, its chance to unbrick it
1. Go to sammobile
2. Go to search ROMs
3. Type in ur phone model
4. A list should appear? Right?
5. Search the country where you live - if its not in the list choose the country that is close to yours.
6. Download & flash with odin
Sent from my SM-J500FN using XDA-Developers mobile app

H3XabyT3LV said:
Refund it and follow my steps -
If you remember ur model number, its chance to unbrick it
1. Go to sammobile
2. Go to search ROMs
3. Type in ur phone model
4. A list should appear? Right?
5. Search the country where you live - if its not in the list choose the country that is close to yours.
6. Download & flash with odin
Sent from my SM-J500FN using XDA-Developers mobile app
Click to expand...
Click to collapse
U even read brah?
So back to stock firmware. It took 1 hour (!) and like 9000 ads (had to disable Adblock) to download the stock firmware. If you don't want to see adds and download full speed. Samsung must be run by a bunch of lomperds. Holy ****.
It finally downloaded and it seemed to work. Untill at the end:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXU1APC4_J500FNVFG1APC4_J500FNXXU1APC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the phone:
Code:
Volume Size is too big 143368 < 489600
ODIN: Invalid ext4 image
This appears to be a partition problem. So I tried to repartition with a random pit file I found on the internet (I guess Samsung really wants to loose customers). I got the next error:
Code:
Secure check fail: pit
Click to expand...
Click to collapse

TheOnlyRealChosenOne said:
U even read brah?
Click to expand...
Click to collapse
Dude, that is the fix for that hidden.ex4 stuff.
I had this problem myself, and I fixed it by this method. Not trying to be rude here.
Sent from my SM-J500FN using XDA-Developers mobile app

The fix will be easy , after flashing the whole firmware it will only fail once the whole process is done 99%
so the fix will be flash custom recovery (TWRP/CWM) since you already said yourself that you are going to root your phone.
then now you can now boot your phone.
FIX:Flash custom recovery after Flash failed firmware
Another will be : Recovery firmware using Smart Switch (Google it yourself)
Another will beIT partition for your Device
Thanks me for my own experimentation (Y)

can body slove this problem

alikashan said:
can body slove this problem
Click to expand...
Click to collapse
Did you even read the comments? Even the title of the thread says solved. Put on your glasses and start reading

garylawwd said:
Did you even read the comments? Even the title of the thread says solved. Put on your glasses and start reading
Click to expand...
Click to collapse
Nothing of this crap is working! I istalled twrp and rebooted to it! Deleted all except that one witch has IMEI info and then flashed via odin! Now? Phone works! I'm kinda dissapointed in Samsung! They are like Chinese broken goods from Craigslist! (No racism here)