I need advice(can boot into recovery and download mode only)

[mclld]

I got an Att GS4 from a friend and it won't do anything but I can get into stock Android recovery and download mode. Should I try to flash a factory image first?

 

[jamezr]

I got an Att GS4 from a friend and it won't do anything but I can get into stock Android recovery and download mode. Should I try to flash a factory image first?

Is it rooted? If so then yes...just flash a stock rom and you are good to go......

 

[mclld]

It isn't rooted that I know of

 

[jamezr]

It isn't rooted that I know of

I would go ahead and flash the stock image that it comes with in odin.
Here is a link and video......makes you wait 17 seconds to view it but.....

http://phonerebel.com/how-to-unroot-unbrick-samsung-galaxy-s4-return-to-stock-att-sprint-t-mobile-verizon-more/#

 

[Stooby Mcdoobie]

Is it rooted? If so then yes...just flash a stock rom and you are good to go......

It can be rooted if there is no OS.

 

[jamezr]

It can be rooted if there is no OS.

almost...it still has remnants of what image was on it last. Not all images can be rooted now. It it had one of the updated images like KitKat....it might not be rootable.

 

[mclld]

I am familiar with odin and have flashed several roms, I just wanted to make sure my best option in this situation

 

[Stooby Mcdoobie]

almost...it still has remnants of what image was on it last. Not all images can be rooted now. It it had one of the updated images like KitKat....it might not be rootable.

Not following you here. Root only affects system.img -- which appears to be missing if the OP can't boot into the OS. All that should be needed to flash a custom ROM is an unlocked bootloader (though usually not required when flashing a factory ROM).

Admittedly, I've not much experience with Samsung devices; but I don't see why it would differ fundamentally from other manufacturers.

I am familiar with odin and have flashed several roms, I just wanted to make sure my best option in this situation

Looks like you will need to flash a ROM, whether it be via Odin or Kies.

 

[jamezr]

Not following you here. Root only affects system.img -- which appears to be missing if the OP can't boot into the OS. All that should be needed to flash a custom ROM is an unlocked bootloader (though usually not required when flashing a factory ROM).

Admittedly, I've not much experience with Samsung devices; but I don't see why it would differ fundamentally from other manufacturers.

I see what your saying now....I think your right. But I have never had an phone without a OS.
My assumption was there was something wrong with the phone and it would not boot.....so it already has an image or OS on it but was having trouble booting.

 

[Stooby Mcdoobie]

I see what your saying now....I think your right. But I have never had an phone without a OS.
My assumption was there was something wrong with the phone and it would not boot.....so it already has an image or OS on it but was having trouble booting.

And that could be the case as well. I've run into issues with the system image corrupting or me accidentally deleting it while trying to clear cache/dalvik inside TWRP or CWM, so that's where my mind went first. Either way, flashing a factory image should reveal whether it actually is a hardware issue or not.

 

[mclld]

I would go ahead and flash the stock image that it comes with in odin.
Here is a link and video......makes you wait 17 seconds to view it but.....

http://phonerebel.com/how-to-unroot-unbrick-samsung-galaxy-s4-return-to-stock-att-sprint-t-mobile-verizon-more/#

I am downloading that stock image now

 

[jamezr]

I am downloading that stock image now

Let us know how it goes

 

[mclld]

It acts like it will do it in odin then it will fail

 

[Switchback666]

It acts like it will do it in odin then it will fail

If you are using the latest Odin try with older version, different USB port won't hurt also.

 

[Stooby Mcdoobie]

It acts like it will do it in odin then it will fail

I would try flashing a custom ROM next. Unlock the bootloader and flash a custom recovery, then push customrom.zip to /sdcard via ADB (TWRP and CWM both allow you to do this).

 

[mclld]

I am not familiar with unlocking the boot loader, can you give me a good link?

 

[Stooby Mcdoobie]

I am not familiar with unlocking the boot loader, can you give me a good link?

Looks like the AT&T GS4 bootloader can't actually be unlocked, but there is an exploit to safestrap around it and flash a custom recovery. Search for Loki exploit on Google/XDA.