Database Users

[50€ reward]!!! - SGS2 NOT flashable anymore

Hi guys.
After my first flash (with success) I had root and all was all right.
But now, I wanted to try litening ROM 2.0, I have to see, that I am not able to flash my device anymore. I tried with odin with 1- and 3-part firmwares,.. only Kernel,..tried with Heimdall, made factory resets thousand times.... after EVERY reboot my SGS2 is in the SAME state since before.
It is a state like I made a special recovery. Installed Apps (after first flash) were gone after every reboot. Token images, ... left....
What can I do now? There has to be a solution I hope ...!?

humphrey74 said:
Hi guys.
After my first flash (with success) I had root and all was all right.
But now, I wanted to try litening ROM 2.0, I have to see, that I am not able to flash my device anymore. I tried with odin with 1- and 3-part firmwares,.. only Kernel,..tried with Heimdall, made factory resets thousand times.... after EVERY reboot my SGS2 is in the SAME state since before.
It is a state like I made a special recovery. Installed Apps (after first flash) were gone after every reboot. Token images, ... left....
What can I do now? There has to be a solution I hope ...!?
Click to expand...
Click to collapse
Hi,
what do u have on Odin display?
because, if you don't kill ALL Kies processes, it's impossible for Odin to connect to your device. (it was the case for me)
Try to kill it with your Windows task manager.
good luck.

keke7442 said:
Hi,
what do u have on Odin display?
because, if you don't kill ALL Kies processes, it's impossible for Odin to connect to your device. (it was the case for me)
Try to kill it with your Windows task manager.
good luck.
Click to expand...
Click to collapse
I forgot to say that here in detail
Odin said PASS (in green) and before klicking start, the correct connection was signed with the yellow COM field.
There is no KIES problem, I killed all KIES processes in TaskManager before.
I discussed this in a lot of forms and nobody could help me yet.
There must be something in my configuration, that makes my SGS2 load a special recovery. (have NO titanium backup installed!!)
..hm ...

humphrey74 said:
I forgot to say that here in detail
Odin said PASS (in green) and before klicking start, the correct connection was signed with the yellow COM field.
There is no KIES problem, I killed all KIES processes in TaskManager before.
I discussed this in a lot of forms and nobody could help me yet.
There must be something in my configuration, that makes my SGS2 load a special recovery. (have NO titanium backup installed!!)
..hm ...
Click to expand...
Click to collapse
Does it boot? and which kernel/recovery do you have installed? which software were you running before you tried to flash to litening?

I had this problem going from villian to litening. I had to install official genertic samsung firmware to sort it out. After I did that I have had no problems with flashing roms.
Sent from my GT-I9100 using XDA Premium App

Yes, it boots. But always into one same state.
I flashed it with XWKDD_insecure.tar (without repart and without PIT file) and then rooted it with "SuperOneKlick".
My Phoneinfo says:
Kernel_version: 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Buildnr: GINGERBREAD.XWKE2
After it, cause I was very happy to have a rooted device, I installed AndroidWall, AdFree, AutoKillerMemory, NoLED and AutorunManager
that´s all I did. additionaly I tried to set up the UAString for the stock browser with commands like about:debug, about:config and about:useragent.
That´s all I can remember.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from .... .

humphrey74 said:
Yes, it boots. But always into one same state.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from ....
No it loads what you have flashed last .
Use Odin and an stock rom KF3 with single part file flash without repartition or pit .
Then start again as your posts just show that you have flashed nothing at all .
That kernel is very very old .
Post where Odin fails and post phone details if it boots .
Follow lightning rom instructions fully .
jje
Click to expand...
Click to collapse

I had the same issue, but solved after flashing the GT-I9100_KE7_insecure.tar.md5 kernel.
I believe there's a link to the kernel in this thread

JJEgan said:
humphrey74 said:
Yes, it boots. But always into one same state.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from ....
No it loads what you have flashed last .
Use Odin and an stock rom KF3 with single part file flash without repartition or pit .
Then start again as your posts just show that you have flashed nothing at all .
That kernel is very very old .
Post where Odin fails and post phone details if it boots .
Follow lightning rom instructions fully .
jje
Click to expand...
Click to collapse
I downloaded the old stock kernel 'I9100XWKF3_Kernel.tar' and flashed it with odin.
Result:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> zImage
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
I did it several times. Odin says nothing failed.
After reboot, ..same state!
Phone Details after this:
Kernel_version: 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Buildnr: GINGERBREAD.XWKE2
Click to expand...
Click to collapse

You need to flash a full firmware not a kernel .
jje

humphrey74 said:
JJEgan said:
I downloaded the old stock kernel 'I9100XWKF3_Kernel.tar' and flashed it with odin.
I did it several times. Odin says nothing failed.
After reboot, ..same state!
Click to expand...
Click to collapse
Download the full KF3 ROM and flash that using ODIN. Then re-do your root. I recommend using CF-Root instead of Superoneclick. It takes the guesswork out.
Click to expand...
Click to collapse

OK, I downloaded the full KF3 ROM and flashed it with Odin.
Finished with PASS.
No change anfter reboot.
As I said in my first post, I can flash what I want .... device boots up into the same state, as I did flash nothing!
I flashed FULL firmwares, rooted kernels ... etc..
Nothing happens

Download XXKG2 from here
http://forum.xda-developers.com/showthread.php?t=1174161
and flash the 3 file version (wipe version)

OK i did flash the 3-parted KG2 exactly like the instructions say.
Odin says:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKG2_CL375027_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG2_REV_02_CL1037208.tar.md5 is valid.
<OSM> GT-I9100-CSC-HOME-MULTI-OXAKG2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> Sbl.bin
<ID:0/011> param.lfs
<ID:0/011> zImage
<ID:0/011> factoryfs.img
<ID:0/011> data.img
<ID:0/011> hidden.img
<ID:0/011> cache.img
<ID:0/011> modem.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response form LOKE
<ID:0/011> cache.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/003> Added!!
As I said .... after reboot thy phone is in same state!!
And now you professionals it´s your turn...

Does it boot straight to OS after flash?
or does it load up recovery (formatting /cache updating media and other stuff)?

omrij said:
Does it boot straight to OS after flash?
or does it load up recovery (formatting /cache updating media and other stuff)?
Click to expand...
Click to collapse
It boots straight to OS after flash. EVERYTIME

hi there
Im not a developer, just a simple user, if were u, these r the tricks that I will play
1- change the usb port
2- restart the computer
3- change the computer
4- uninstall kies and install the independant drivers
5- finally, if all failed, ill wait from kies to do the system update for me, this will give u a fresh start over
hope this would help

drreality said:
hi there
Im not a developer, just a simple user, if were u, these r the tricks that I will play
1- change the usb port
2- restart the computer
3- change the computer
4- uninstall kies and install the independant drivers
5- finally, if all failed, ill wait from kies to do the system update for me, this will give u a fresh start over
hope this would help
Click to expand...
Click to collapse
hey
- I changed the USB port
- I restarted the computer very often
- I tried with other computer
- I tried update with KIES
No other result than it boots into same state

Factory reset after flash?

Yes, I did this too. And not only once ...
No change happens

[Q] Please help me unbrick my s4 TB bricked CWM can't help.

Hi everyone.
What happened to my phone is the weirdest thing and so far it seems nothing can work to fix it.
It's a GT-i9500 international model. Rooted and with KitKat 4.4.2.
How I messed things up:
- Was in Titanium Backup, tried to convert one game app I previously made "system app" back to "user app". The process was taking over 20 minutes... I figured must be some kind of a freeze. Then I held the power button to shut it off.
- I then powered on again, and realized that the device is not booting! There was no "Samsung" logo.
How I tried to fix it:
- I went to the CWM recovery and tried installing my latest backup (with a custom ROM). Did that after wiping all cache (with dalvik included) and data wipe system restore in CWM. After restoring the device that way -> It boots to "samsung" animation where it stays and gets warm when left for over an hour.
- I went back to CWM this time tried to flash the custom ROM again - so I picked the custom ROM zip file after wiping cache/system restore in CWM again and waited till it finishes. Rebooted the device -> It boots to "samsung" animation where it stays and gets warm when left for over an hour.
- Again in CWM tried to this time restore the stock rom which I have backed up with CWM after I have rooted the phone. -> The weirdest thing happened after restore. The phone booted into the carrier "boot animation", then it showed "Samsung gt-9500" (first time ever I've seen this screen on this device, it was never shown before), then it went once more to "samsung" letters being lit (but without the "samsung" boot animation with that purple thing and sound).
- I tried formatting the partitions within CWM except for the EFS and external SD partition and repeating each of the above all to no avail.
When I returned the stock firmware in third example (it was stock, but that backup made by CWM recovery ofc) CWM asked on reboot if I want to get back to stock recovery, I said no since I don't want to lose CWM esp now that the phone doesn't work as it should.
Currently I'm trying to:
- Flash stock firmware with ODIN through the download mode. Sadly so far I've seemed to have downloaded the Jelly Bean ROM instead of KitKat for it because ODIN gave me (nand write) error on flashing PDA and device showed:
check fail device:3 binary:2
So yeah, downloading firmware and will try ODIN with the KitKat one (the other I tried with ODIN didn't have version written in so that's why I assumed it must be KitKat too, took it from XDA guide, but seems it was JB after all).
I also want to stress that all previous steps in CWM were all done using KitKat builds so that couldn't be the problem.
So any of you have any idea what's going on with my phone?
I find it really weird that CWM which is supposed to restore phone in case of emergencies like this failed to do so. Perhaps nandroid backup would be a better choice next time? What do you think?
EDIT:
OMG this seem bad. Tried to flash through ODIN with another ROM and this is what I got:
<ID:0/007> Added!!
<OSM> Enter CS for MD5...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUFNC1_I9500YDDFNC2_I9500DDUFNA4
<OSM> Checking MD5 finished sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialization..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> param.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (Succeed 0 / failed 1)
---
Interestingly after this - now I don't have Chinese "download" mode anymore (the phone was bought through a friend and worked for over a year fine rooted btw) now it's in English... and, if I just try to boot it it says nicely:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
It would also seem recovery is gone too now... :/
hmm...
EDIT2:
Tried a different USB cable - same result.
Tried Odin 3.10 - same.
EDIT3:
WOW... the strangest thing!
So... after reading tons of threads I have found a suggestion to change the USB port. So I did (from USB 2.0 on my laptop to a USB 3.0 one if that matters). That's on org Samsung USB cable + reinstalled USB drivers to latest + ODIN 3.10. And then... it worked. Instead of "fail" on "system.img" this time it showed progress on the "system" stage. After a while it DID finish with a "PASS".
Next boot I was told that "Device memory damaged" and asked to factory reset it. Which I did. Next boot - Booted the first run settings and the system... next boot - booted the "Black Edition" (with different boot animation sound and then theme) and it's working now fine O_O will proceed to root it and then take care of everything again discarding the old backups and backing up stuff again.

[Q] -CM- What to update to

Hi guys, I have a Samsung Galaxy S4 from Canada, specifically Rogers. The phone is currently on the CM11 Nightly ROM. (I can check specifically which nightly, my phone is just backing up at the moment so I can't see!)
I have this problem, which is, when the phone automatically locks or I myself lock it, the radio signal completely drops. Sometimes the signal will come back, but to get it back for sure is to turn the phone on airplane mode then off again. It is annoying because when the phone is locked for a while, it will receive signal at some point. During that time I'll get a call and it'll ring but once the screen turns on the signal will drop, also dropping the call. I have a slight understanding that it could be a problem with the phone's radio firmware?
Now that you guys have an understanding about my problem, this is what I am hoping to accomplish. I want to update the phones ROM, as it is probably old, along with the proper fix to the phone's radio firmware. How do i go about doing this? The kind of ROM that I want is something in between stable version and nightly (not nightly as I think nightly was the one that caused my radio problem), I think that's SNAPSHOT M12? Please correct me if I am wrong. I would rather not lose any of my data but if I have to then I will but please do guide me because I am scared to lose any of my data.
Thank you guys for reading my long post, I hope my English and grammar is fine! I look forward to hearing from you guys!

The current version of Cyanogenmod is 12.1 (Android 5.1.1). The two release channels for 12.1 are nightlies and snapshots. As of yet there has been no CM12.1 snapshot I'm aware of, meaning all CM12.1 ROMs are nightlies.
You haven't said what version of the stock ROM you had before moving to CM11, but if the radio is too old, you'll want to update it. You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.

Thanks for the reply!
Strephon Alkhalikoi said:
You haven't said what version of the stock ROM you had before moving to CM11
Click to expand...
Click to collapse
I don't know how to answer this, It's been quite a long time since I moved to CM11. Basically what I did was, when I bought the phone I went home and installed CM11 on it, haha.
Strephon Alkhalikoi said:
You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
Click to expand...
Click to collapse
I am quite confused, sorry. What I'm doing right now is I'm downloading the newest radio firmware from the link you have given me. After that I'm going to follow the instructions of:
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
That will fix my radio problems?
Now to update my ROM. This is where I am mostly confused. In your opinion, should I stick with CM11 Nightly? Can I somehow go from nightly to a more stable version like cm11 snapshot m12? Should I update to CM12? Will my phone keep up with the CM12 ROM?
Strephon Alkhalikoi said:
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Click to expand...
Click to collapse
Sorry I will keep that in mind! Mind you, I carefully chose this and looked at all my other options. I didn't see the AT&T forum to fit because AT&T is in the United States and my carrier is in Canada, I just didn't want to have problems with anything else

Guys, I think i screwed up.... So when i downloaded that firmware from Sammobile. I flashed it with ODIN and made sure re-partition was not checked. Everything looked fine and when my phone rebooted (its still rebooting at the moment) the welcome screen was the default "samsung" splash screen, not the Cyanogen Mod . I thought this method was only going to flash the phone's modem, not the ROM too
EDIT:
No....my worst nightmare came true .........NO!!!!
So my phone finished rebooting and its just a black screen. All I can see is the status bar at the top right that displays the WiFi signal and the Phone's network signal and the battery. Okay so I figured something out. When the phone is locked and I press the Home button, Battery Doctor's charging wallscreen shows up, meaning my device wasn't wiped ? When I tried to unlock from Battery Doctor's charging screen, it would just show the black screen with just the status bar .... PLEASE HELP ME !!!

It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.

Strephon Alkhalikoi said:
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Click to expand...
Click to collapse
D'awww Well I guess a clean slate isn't so bad. I backed up my text messsages and my photo's should be backed up onto the google drive anyways. I don't know if you saw my edited post but the UI is not loading. Its just showing the status bar at the top right (signal, wifi signal, battery).
Thanks.

If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
EDIT: ROM installs don't wipe data when done through Odin unless you tell Odin to partition the device. Thus you'd need a factory reset to ensure Touchwiz works. But where you're going to put Cyanogenmod on, don't worry about Touchwiz.

Strephon Alkhalikoi said:
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
Click to expand...
Click to collapse
The problem is, I can't. There's nothing there on the phone. Its just a black screen. Unless, thats what you meant.
I tried searching for a CM 12.1 Canadian version and I found this thread. http://forum.cyanogenmod.org/topic/104233-jfltesgh-i337m/
apparently theres no canadian version of the CM 12.1
what should I do ?

Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.

Strephon Alkhalikoi said:
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Click to expand...
Click to collapse
Thanks for the replies! I'm sorry if im asking for too much but could you please confirm that this is the right one? link
So, I don't need to root? how can i verify that my phone is still rooted? If my phone is still rooted, I download Canadian Galaxy S4 SGH-i337M (Bell, Rogers, Telus) – CWM Recovery v6.0.4.4
Then flash that with Odin ?
edit: I think I know why this failed miserably....On Odin V3.10.6 I clicked "AP" for some reason, when I was flashing the firmware. Could that be the problem? If so, is there a fix ? i can't access my phones SD card .

Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.

i just installed cm-12.1-20150625-NIGHTLY-jfltexx on my s4 with cm-12.1-20150623-NIGHTLY-jfltexx but there is a problem with the phone functions. It can't make any call. .it do not find my sim card!! Same thing with cm-12.1-20150624-NIGHTLY . The last one that works is 20150623 . Is there anyone that can confirm my problem?

Strephon Alkhalikoi said:
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
Click to expand...
Click to collapse
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.

flipboi15 said:
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
Click to expand...
Click to collapse
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.

Lennyz1988 said:
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Click to expand...
Click to collapse
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!

Flashing CM is easy. It doesn't require root access because this phone has no bootloader lock. Download a custom recovery with TAR file format, install drivers, go to the download mode of your phone, connect your phone to your computer, and use Odin to flash the recovery. Then copy CM zip file to a SD card and flash it in recovery. That's all!?
For recovery I recommend TWRP: teamw.in
If you've installed Kies you should have drivers on your computer. Otherwise install Kies or only drivers if you can find them on Samsung official website.

flipboi15 said:
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Use a different usb port / different usb cable.

Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.

flipboi15 said:
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
Click to expand...
Click to collapse
Try redownloading the .zip file. Maybe it's corrupt.

So after trying to install the ROM in TWRP and failing. I couldn't load up the phone anymore, it got stuck at the Samsung Logo screen. I am now re-flashing I337MVLUGOC4 - 5.0.1 Lollipop.
edit:
So at the moment, my phone is working fine on stock rom. I redownloaded the CM-12.1 optimized. I moved it into my SD card. I need to know if there are certain steps I need to do to get this right. These are the steps I took the first time.
Rebooted into TWRP recovery mode, then clicked install then I navigated to the CM-12.1 ROM zip and swiped to install.
Was I supposed to wipe anything? The only time I wiped(the default wipe in twrp) was after I installed the 5.0.1 Lollipop firmware. By the way, i noticed that my phone's internal memory is almost full, it only has 2GB of 9.69GB left in the internal. I checked it out and all my old files were still there!

Galaxy S4 flash help

Hello,
I was wondering if anyone could possibly help me with my phone. The story is that yesterday it randomly shut off and then wouldn't turn back on. Then I eventually got it to turn on but it popped up with the message in the first image.
Then I downloaded my stock rom and downloaded it onto my phone using odin with no problems. But then it would just load with the boot image and nothing more. It wouldn't go into recovery mode either so I decided to redo it. However, when I did it, odin froze and left the progress like in the second image for hours. I decided to unplug and do it again, but it keeps on freezing at the same point. Now whenever I reboot it says the same thing as the first image....
Does anyone have any suggestions on what I could do?
EDIT: Now I actually installed stock rom, but it will not boot. It stays on the logo and when I try to go into recovery mode, it says it is going into recovery mode at the top left, but it just infinitely reboots after that. Any suggestions?

Flash the ROM in the Bootloader slot in Odin.

You could try different combinations of USB cables, USB ports and Odin version.

Pwnycorn said:
You could try different combinations of USB cables, USB ports and Odin version.
Click to expand...
Click to collapse
I've tried that already but to no avail... I am trying to flash the rom in the bootloader icon right now like Strephon Alkhalikoi mentioned

Strephon Alkhalikoi said:
Flash the ROM in the Bootloader slot in Odin.
Click to expand...
Click to collapse
it's still doing the same thing.... How long should it take?

Strephon Alkhalikoi said:
Flash the ROM in the Bootloader slot in Odin.
Click to expand...
Click to collapse
This is what it said when I did it on bootloader
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Pwnycorn said:
You could try different combinations of USB cables, USB ports and Odin version.
Click to expand...
Click to collapse
I got it to finally work, but now it won't boot correctly. I try to go into recovery mode and it just keeps infinitely rebooting after that.

Confirm that the phone model # in download mode is the agh-i337m.
If this is correct, try Odin 3.19, uncheck everything excep f reset time, flash the phone. When successfully flashed, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery, and factory reset.

audit13 said:
Confirm that the phone model # in download mode is the agh-i337m.
If this is correct, try Odin 3.19, uncheck everything excep f reset time, flash the phone. When successfully flashed, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery, and factory reset.
Click to expand...
Click to collapse
Yeah its SGH-I337M and there is no odin 3.19. Which version did you actually mean?

Sorry, I meant Odin 3.1.

audit13 said:
Sorry, I meant Odin 3.1.
Click to expand...
Click to collapse
Thanks. It worked....but only temporarily. I got into recovery halfway, but then it rebooted again. I got into it again somehow and tried to press factory reset, but it restarted again... What should I do?
EDIT: I got it to factory reset, but it just keeps on doing the same thing.... It keeps on restarting over and over

Strange, the memory chip could be defective.
You could try flashing twrp and use twrp to do a factory reset.

audit13 said:
Strange, the memory chip could be defective.
You could try flashing twrp and use twrp to do a factory reset.
Click to expand...
Click to collapse
Sorry how do I do that? What is twrp?

robs247 said:
Sorry how do I do that? What is twrp?
Click to expand...
Click to collapse
It's a custom recovery. TWRP stands for Team Win Recovery Project.
I don't think there's a version specifically for your device, so then make sure that whatever you get is for the Qualcomm S4.

Twrp for the i9505 can be flashed to the i337m and can be found here: https://dl.twrp.me/jfltexx/
Download the tar version, flash it in the pda slot of Odin 3.1. Do the same thing where you uncheck auto reboot, flash remove cable etc. and boot into twrp, choose wipe, advanced wipe, wipe cache and data.

audit13 said:
Twrp for the i9505 can be flashed to the i337m and can be found here: https://dl.twrp.me/jfltexx/
Download the tar version, flash it in the pda slot of Odin 3.1. Do the same thing where you uncheck auto reboot, flash remove cable etc. and boot into twrp, choose wipe, advanced wipe, wipe cache and data.
Click to expand...
Click to collapse
I did it, but when I try to boot into recovery, it says "Recovery is not SEANDROID ENFORCING." Then it just reboots after like 20 seconds... What should I do?
EDIT: I got in and I did what you told me to do, but it still randomly reboots and keeps going in a boot loop for a while, then works correctly, then stops working...

I wonder if it is a batter problem. Try using the phone while it is connected to a power source.

audit13 said:
I wonder if it is a batter problem. Try using the phone while it is connected to a power source.
Click to expand...
Click to collapse
It does the same thing

Same problem
same problem please help me how to fix it (
imgur.com/a/UwhUe

Reflashing stock rom

I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.

mrnice10033 said:
I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.
Click to expand...
Click to collapse
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.

#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.

#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
unfortunatly, I've tried this multiple times and still cannot get it out of the boot loop. I'm not booting back into recovery but rather to the Samsung logo now.

Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
I've done this as well with no success.

And if you are not waiting for the necessary time you need to load the system? .. since after installing the stock you have to leave this in the samsung logo about 10 to 20 minutes at least

One thing to note is that you should be flashing AP, BL, CP, and CSC, and not the HOME package only (not sure if your variant has it in the first place!). Also, ensure that the "NAND Erase All" option is ticked before performing the flash.

thank you, I have not tried ticking nand flash before but I will try it.

Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
This is what I'm seeing on Odin
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.

mrnice10033 said:
This is what I'm seeing on Odin
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.
Click to expand...
Click to collapse
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!

https://drive.google.com/drive/folders/0B8346PsUO8X8cUE1QkZMOGI2SmM?usp=sharing
Try this!

Rizzed said:
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!
Click to expand...
Click to collapse
Thank you so much. I appreciate it.