[Q] From 4.4.2 to 4.2 ?? - Galaxy S 4 Active Q&A, Help & Troubleshooting

Hallo, i am running "I9295XXUCNE5_I9295DBTCNE1_DBT" Rooted (official 4.4.2 for Germany) but i want to go back to "I9295XXUAMF5_I9295OXXAMF4_EUR" (official 4.2 for Greece, my country).I have download everything form "http://www.sammobile.com/firmwares/". I am trying to do it with odin but nothing (Fail)...Please help
Thank you.
P.S. now i am running Carbon's Rom, but i really have to go back to 4.2 official...

Just flash 4.2 via odin
Sent from my GT-I9295 using XDA Premium 4 mobile app

6783 said:
Just flash 4.2 via odin
Sent from my GT-I9295 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried to install "I9295XXUAMF5_I9295OXXAMF4_I9295XXUAMF5_HOME.tar.md5" but sais FAIL and the phone stuck on downloaer.
I select PDA from Odin and then "I9295XXUAMF5_I9295OXXAMF4_I9295XXUAMF5_HOME.tar.md5" i press start and then Fail...

<ID:0/009> Added!!
<ID:0/009> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9295XXUBMK3_I9295OXXBMK5_I9295XXUBMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl2.mbn
<ID:0/009> sbl3.mbn
<ID:0/009> rpm.mbn
<ID:0/009> aboot.mbn
<ID:0/009> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Malous said:
<ID:0/009> Added!!
<ID:0/009> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9295XXUBMK3_I9295OXXBMK5_I9295XXUBMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl2.mbn
<ID:0/009> sbl3.mbn
<ID:0/009> rpm.mbn
<ID:0/009> aboot.mbn
<ID:0/009> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is failing to flash the bootloader. Flash everything EXCEPT the bootloader and it should go through.

May i ask how?
Sent from my GT-I9295 using XDA Free mobile app

Malous said:
May i ask how?
Sent from my GT-I9295 using XDA Free mobile app
Click to expand...
Click to collapse
I just realized that it is all packaged as 1 file. The first thing I would do is to check the MD5 to make sure the file you downloaded is not corrupted. Make sure you are using the cable that came with your phone, try different versions of Odin and different usb ports. If you have the i9295 it should have an unlocked bootloader, so as long as your download isn't corrupted it should flash just fine.

Related

[Q] Error while installing the Official firmware update in the Downloading mode

I have not kept the cell in the usb debuggin mode and have kept the phone in downloading mode and tried install using ODIN and while installing it showed as FAIL and was unable to start again.Volume up + home button +power on i have tried but it is not going to recovery mode.
I have not rooted the device yet.
The LOGS that i have got while using it.
Please help me..I would be so thank full if anyone could help me for GOD sake..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000ZSLM5_N7000OZSLM5_N7000XXLSO_HOME.tar.md5 is valid.
<OSM> N7000ZSLM5_N7000OZSLM5_N7000XXLSO_HOME.tar.md5 is valid.
<OSM> N7000ZSLM5_N7000OZSLM5_N7000XXLSO_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009> Sbl.bin
<ID:0/009> zImage
<ID:0/009> cache.img
<ID:0/009> Transmission Complete..
<ID:0/009> Now Writing.. Please wait about 2 minutes
<ID:0/009>
<ID:0/009> Receive Response form LOKE
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in Advance..
Install the drivers and try again
64 bit http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32 bit http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Sent from my GT-N7000 using Tapatalk 2
Help
I have tried this.
Please help before the battery runs out.
Thanks for reply.
Help me at least startup my phone
madhu163 said:
I have tried this.
Please help before the battery runs out.
Thanks for reply.
Click to expand...
Click to collapse
Atleast help me to startup my cell.
I am facing a lot of prblms without the cell rightnow.
Please and please help me.
updated to jelly bean..
thanks to this forum:good:
Congratulations
Sent from my GT-N7000 using Tapatalk 2

[Q] bootloop phone

I have been running PACMAN rom (with NX kernel), but due to it crashing repeatedly, I've tried to restore it to my stock ROM (Jellybean).
So I backed up everything on Titanium Backup,
downloaded the correct (most up to date ROM for me) N7000XXLSZ_N7000OXXLS4_VOD
and then flashed it using Odin,
It whizzes away, comes up with an "all clear"
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000OXXLS4_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> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> zImage
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000OXXLS4_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> zImage
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
then my phone restarts and is just hanging on the the Samsung boot screen.
I can't access recovery mode, but I can access download mode.
Having researched the other threads, it appears I am not alone, but I am unsure how to progress to get stock rom.
Can anyone please advise me what the next steps should be please?
I tell a lie, I can get into recovery mode, but it still loops
emyllis said:
I tell a lie, I can get into recovery mode, but it still loops
Click to expand...
Click to collapse
Did you perform wipes after or before flashing?
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
Did you perform wipes after or before flashing?
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No - I assumed using ODIN would wipe it clean as it were...
Would the correct course of action be to go into CWM, wipe everything then try ODIN again?
In my head the issue is with the kernel (NX), but I think that;'s just paranoia!
anyway, I've got into CWM and am about to go and wipe everything to try again... My worry is that the kernel is wrong though and it'll generate an error message further on down the line? any thoughts please?
If you have flash a rom, then there will not be any cwm.it will be stock recovery. You can flash Philz kernel using recovery and then use cwm recovery to wipe data. The phone should boot up then.
Sent from my GT-I9500 using xda premium

I have a problem with odin ?! help !

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070JVBMD1_I9070OJVBMD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> cache.img.md5
<ID:0/009> NAND Write Start!!
<ID:0/009> hidden.img.md5
<ID:0/009> __XmitData_Read ..
<ID:0/009> XmitData Fail..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that's what i got when i'm trying to flash stock jb 4.1.2 :/
it's not the first time that i flash stock jb
edit: solved by flashing custom recovery by odin then reflash stock GB

SM-G900A firmware corrupted

Hi, i recently got the SM-G900A from AT&T and the firmware corrupted. It was running stock lollipop with the build number G900AUCU4BOF3. At first i was on a screen where it said for me to "Connect to Kies and select Emergency Recover" or something, but my phone isn't supported nor does it show up on Kies. I have tried every stock version i could find to try and downgrade my build number if possible, but it would always fail in Odin.
Also, in Recovery Mode it shows a completely different build number: G900AUCU1ANCE
<ID:0/009> 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/009> Odin engine v(ID:3.1100)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The thing i don't really get is why it let me flash "system.img.tar" and it won't flash a full stock rom without the output above.. Any help would be greatly appreciated! If possible, can someone dump their stock rom?

Bricked from resurrectionmix, please help

I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.
But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> sbl1.mbn
<ID:0/015> rpm.mbn
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail : ABOOT
And the firmwares I tried are
NIH, NK4, COD
MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.
Can somebody help me out? Thanks
Stiria said:
I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.
But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> sbl1.mbn
<ID:0/015> rpm.mbn
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail : ABOOT
And the firmwares I tried are
NIH, NK4, COD
MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.
Can somebody help me out? Thanks
Click to expand...
Click to collapse
Did you contact the dev?

Categories

Resources