ODIN is unable to flash stock firmware for Galaxy S4 SC-04E - Galaxy S 4 Q&A, Help & Troubleshooting

Hi,
I need some assistance. I have an S4 (SC-04E) and it has TWRP custom recovery loaded in it. My colleague accidentally clicked wipe system from TWRP and it wasn't able to boot at all. So I thought I'd flash the stock firmware in order to resolve the problem. However, when I flash stock firmware on ODIN, it fails and gives me an error:
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I resolve this? The original firmware was 5.0.1 and I tried flashing both 4.4.4 as well as 5.0.1, but both have failed. I googled the error and I was unable to get relevant results. I downloaded the stock firmware from sammobile. Any idea what I can do for this issue?

Your phone doesn't boot because your friend wiped the Operating System from it. The recovery should boot and flashing any custom ROM through it should make it work again.
Regarding your Odin problem, make sure you have done the following:
Used a different USB cable
Used a different USB port
Used a different Odin version
Tried another Windows
Tried a completely different PC.
All of the above can affect the outcome of flashing with Odin.

Related

Accidentally deleted my System folder SGH-M919

Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!
titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.

[Q] Got myself into a bit of a mess with custom roms

I'm pretty new to this, and managed to root my AT&T galaxy s4 i337 recently, using a guide I found here (it won't let me post the link).
From what I can tell, it didn't give me a custom recovery. Booting into recovery mode gives me the stock recovery. Now, I'd like to try paranoid android or cyanogenmod, but so far I've tried several guides and apps/tools and none has worked.
I've tried installing the clockwork mod app, and although it told me it's successfully installed, when I reboot into the clockwork recovery, it instead takes me to the stock recovery.
I've tried flashing the new AP with Philz touch using Odin3, but each time it fails on auth:
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried copying the paranoid android rom to my SD card, and installing it via the stock recovery but all it seems to have done is reset my phone to stock. All the samsung bloatware is back.
If anyone could tell me what I'm doing wrong, or how to get around this I'd really appreciate it. Ideally I'd like to end up with a custom recovery, and either PA or CM on there. I believe the phone is still rooted.
thanks very much for any help.
http://forum.xda-developers.com/galaxy-s4-att is where you want to go, as there are far more people on that forum that can help you with your issue than we can. This is the international S4 forum. Your device has a locked bootloader, meaning you cannot install a custom recovery or a custom ROM to the device's system areas. To get a custom ROM on your device requires a different process, which the link provided can assist you with.
Ah, thank you very much for pointing me in the right direction.

Phone won't boot, even into recovery mode

Hi all, im desperate for help here!!
I flashed Dr Ketans Rom to my Note 4 a couple of days ago but decided to try to go back to stock today due to a bug with my email. Anyway, a long story short, my phone failed the flashing process with odin whilst trying to flas the latest stock firmware from sammobile and then my phone refused to start up again.
I now get a screen telling me the firmware up grade process went wrong but I cant even reboot into recovery to install anything else.
I have tried flashing both TWRP and Philz recovery but both just flash the title screen on and off but never load up.
I have tried 2 firmware versions from sammobile and both end in fail, it seems like I cant flash any firmwares with odin which is a right pain because I cant get to recovery to install a zip file....
Please help, Im sooooo stuck!
Edit - this is the log from Odin if it helps anyone... Ive now tried software 4.4.4 also but nothing works.
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
0-0-0 said:
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
Click to expand...
Click to collapse
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
sudburys said:
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
Click to expand...
Click to collapse
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
0-0-0 said:
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
Click to expand...
Click to collapse
No probs...
Thanks for the try anyway

Bypass FRP? Can't get passed activation Setup Wizard

I recently re-installed a custom ROM and after installing a couple of the necessities apps and downloading Xposed (not installed) I would get random lost of wi-fi, lost phone's data, and couldn't send texts. I rebooted and lost root. Therefore was unable to perform a backup or re-flash ROM. I tried clearing system cache, rebooting, anything else i could think of and finally did a factory reset so i could flash stock firmware. Oh and my external SD card all of a sudden was corrupted. Once in the activation Setup Wizard was unable to activate the phone because the data wasn't working. I also tried removing the sim card and trying through wi-fi but again couldn't connect.
I've been searching for hrs and trying every method of bypassing the Set Up Wizard. Non have worked because most of them involve accessing the internet.
I've also tried booting in maintenance mode and enabling USB debugging to flash firmware but have been unsuccessful. I've tried different versions of Odin and all failed.
Does anyone have any suggestions? I could really use the help!
Forgive me if I'm missing something incredibly obvious or a previous post mentioned this issue as I did my best to search for one. I'm new to rooting as this is my first rooted phone which I only accomplished a couple weeks ago. And i realize now that a factory reset, (which I believe doesn't wipe the ROM, correct?), wasn't very smart while i was having network problems.
Firmware
G935VVRU2APE1
Custom ROM is one I've been using all week with minor issues and have been able to re-flash the ROM to solve issues in the past.
Odin PrinceComsy v3.12 (this one has always worked in the past, have switched USB ports including one that's not 3.0)
Odin v3.11
v3.10.7
Fails in Download mode:
sw rev check fail : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot
Odin Fails:
<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> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> lksecapp.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update: Currently running Verizon Software Repair Assistant
Update: Looks like the Verizon Software Repair Assistant worked. Of course I would find the solution right after asking for help. Now if I could just find out why this how happened in the first place.

Unable to flash anything on Samsung Galaxy S4 GT-I9515

Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?

Categories

Resources