Database Users

SGS4 won't boot....

Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx

vivelafrance said:
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
Click to expand...
Click to collapse
where odin failed exactly?
did you try changing usb port? kies totally disabled? original usb cable?

thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.

vivelafrance said:
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
Click to expand...
Click to collapse
one more thing, remove battery for a couple of minutes, then try with odin 1.85

All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.

vivelafrance said:
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
Click to expand...
Click to collapse
i dont know if flashing pit file along with the firmware will work

yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?

vivelafrance said:
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
Click to expand...
Click to collapse
pit file is flashed with the firmware. choose the right pit for your device! re-partition will be checked automatically when you select the pit file.

still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...

vivelafrance said:
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
Click to expand...
Click to collapse
did you flash firmware with the pit file at same time and didnt work?
almost you did everything.
try to change computer if available.

no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help

vivelafrance said:
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
Click to expand...
Click to collapse
If you haw acess t dawnload mod you are nhot bricked pleas go and try other pc
Sent from my GT-I9505 using xda premium

First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx

this is surely NOT a mobile issue if you can enter into download mode.
i had the exact issue a month ago when i had note2.
if you can't try it on another pc, try :
1) uninstall skies completely
2) unisnstall usb drivers
3) reboot the pc
4) connect your s4 in download mode to your pc.
5) let your pc install freah usb drivers
6) start odin and flash
7) if still you get the same error download a different verison of the official rom and try flashing.
i followed the above procedure couple of times and was finally able to install the rom. the issue is either with the drivers or the rom.
Sent from my GT-I9500 using xda app-developers app

bricked for sure
vivelafrance said:
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
Click to expand...
Click to collapse
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.

Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app

Bluetoth10 said:
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Click to expand...
Click to collapse
thnx. yeah, flashing the PIT actually always worked but it was the only thing that worked! lol

DenmarkRootN00b said:
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.

vivelafrance said:
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
Click to expand...
Click to collapse
good luck at least i just thought it would work by doing it in recovery but yeah... warranty is better.. if not.. then keep trying if they wont replace it

ok I FINALLY could access the stock recovery, did a full wipe and everything is back in order now, works perfectly.
THANKS to all!

[Q] Odin fails, soft bricked phone.

Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> 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)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.

chendoyen said:
Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> 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)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.
Click to expand...
Click to collapse
I thought the only way to fix a bricked phone is to have it repaired or something. But I dont understand why you would switch back to samsung ui, but thats not my business. I believe is risky to go back to the phones normal UI after installing a rom because of the update problem. Basically I would never go back to the normal phones UI even if I wanted to after installing a rom, because I feel like there will be a problem. I dont really know a solution but maybe you can give it into someone to repair it, but I believe it costs A LOT. Sorry I don't really have a good solution for you. These are the risks with installing roms and switching back.

Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app

imlgl said:
Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Yes, also tried another cable.
Also tried: Another Odin version, another PC and different USB ports.

Anyone?

Nobody an idea?

You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable

bAk3ry said:
You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable
Click to expand...
Click to collapse
Tried again another PC and it worked a bit, I now have stock samsung firmware 4.3 installed but still no wifi and no sound. Is there a solution for that? Already tried to install CWM and TWRP but still doesn't work. When I try to play music it says audio file not supported (.MP3 file, before problems always worked) S Voice keeps crashing... And when I try to turn Wifi on I get a security message that says:
The device detected an application attempts to perform action that are not allowed. These actions are blocked.

You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.

MistahBungle said:
You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.
Click to expand...
Click to collapse
Tried that but it still won't work.

[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

I bricked my Note because i didnt flash the kernel :(

Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!

If you can access download mode, your phone is not bricked.
Simply download last firmware for your model from sammobile, and flash it with odin...

ok thanks, will do.
But how do I safely root the note 4 5.1.1? CF-Autoroot isnt compatible

Ok, I just finished download a stock rom for my phone (.tar.zip) but when I click start in Odin it always fails for some reason...<ID:0/003> Can't open the serial(COM) port.
Edit: tried a different port now it fails at:
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
What can I do?
Does upgrading via Kies will result in losing all data?

I'm working on this issue for hours now but I'm stuck
Using Odin it will fail at sboot.bin
And kies doesnt recognize my note 4

Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone: SW REV. CHECK FAIL, DEVICE 2, BINARY 1

Nixdax said:
Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!
Click to expand...
Click to collapse
Restore your backup in recovery

What is your exact model, G or F, what? You download the ROM from sammobile with your exact model no., and then flash.

It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........

Never heard about the H version before! Anyway, make sure you are flashing the correct Xposed, that is Wanam's, but Arter's, and read the installation instructions closely.

Nixdax said:
It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........
Click to expand...
Click to collapse
Please, search before flash.

H model is with Exynos processor.
http://www.sammobile.com/firmwares/database/SM-N910H/

[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)