I am from India, and I was using the Galaxy s2 with Jelly Bean 4.1.2(installed from KIES). The phone suddenly crashed and only download mode is accessible. I downloaded the stock firmware from sammobile and tried odin3 v3.07, but it isnt working and the 0:[com3] background is blue.
The firmware i tried booting it with is I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5
i uploaded this by clicking on the PDA button and this how far it got to:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSK_I9100ODDLSA_I9100DDLS9_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've run out of ideas and forums that I've gone through ! Some one please help!
Look for @Hopper8 thread. Great thread lots of info on Odin problems
No Luck!
andrewwright said:
Look for @Hopper8 thread. Great thread lots of info on Odin problems
Click to expand...
Click to collapse
Hi,
I read through and tried flashing with siyah v6 but even that failed.
Not really sure what the issue is!
mosesadarsh said:
I am from India, and I was using the Galaxy s2 with Jelly Bean 4.1.2(installed from KIES). The phone suddenly crashed and only download mode is accessible. I downloaded the stock firmware from sammobile and tried odin3 v3.07, but it isnt working and the 0:[com3] background is blue.
The firmware i tried booting it with is I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5
i uploaded this by clicking on the PDA button and this how far it got to:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSK_I9100ODDLSA_I9100DDLS9_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've run out of ideas and forums that I've gone through ! Some one please help!
Click to expand...
Click to collapse
Doesnt seem like the phone is charging either!!
Flash philz kernel and then you should be able to get to recovery then flash a custom Rom
Read this bro
http://forum.xda-developers.com/showthread.php?t=2101610&page=2
Hope it helps !!
I tried everything possible but nothing worked. . I got stuck at factoryffs every time then hit xmit data failure. . M sure I hard bricked it now! ! Must be the motherboard. .
can someone please post links to the philz kernel and a stable india version JB firmware !! Please please ... im desperate!!
Search!! Dont be lazy its not hidden or hard to find.
seriously bro?? I found the thread to that kernel but that list is never ending.. God knows which kernel is for my phone!!
Only comment if you have answers please !!!!
All the videos that i watched online show how to install philz kernel on a working phone.
My phone is kinda dead... so what needs to be done after flashing philz kernel? Tell me the next steps please..
Does it still go to download mode? Does odin still see it?
I tried flashing my phone with philz kernel but even that failed...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSK-ODD-4.92.8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<OSM> All threads completed. (succeed 0 / failed 1)
Make is easy on your self and flash lss firmwear and flash lss kernel "near the top of download list" chances are you dont have an os now odin has failed to flash. Hooper8 thread has good info on flashing problems! Read that before you try.
Pics clicked a minute back... does this help...
Pls read hooper8 thrsad
Any joy now op?
Nope.. No luck... nothing goes beyond the nand write start! message.. Im done trying stock rom from sammobile, siyah v6, philz kernel.. nothing succeeded
mosesadarsh said:
Nope.. No luck... nothing goes beyond the nand write start! message.. Im done trying stock rom from sammobile, siyah v6, philz kernel.. nothing succeeded
Click to expand...
Click to collapse
Same problem here, my phone was working fine then all of a sudden i noticed it was dead, tried rebooting it, nothing happened, boot loop, tried to access CWM, i got the lower section menu of CWM but nothing else, a black screen with the buttons.
So next i said, let me use odin to flash a new kernel. That failed and ever since that failed, i cannot do anything except enter download mode. If i power the phone on, i get a [phone-problem-computer] image in yellow with text that says somehting like problem loading software, please conntect to kies recovery mode. of course that never works.
And everytime i try to flash absolutely anything on this device, Odin DOES see the device, and the second i press flash/start, when it reacher nand write start, it hangs there, stuck doing nothing.
I took the phone to a friend who has an Riff jtag box, he soldered his jtag to the phone and said the memory chip is not dead, i can read its capacity normally. But when he tried to write to it, it did not work, kept giving him errors, he said he has never encountered such a behavior before. And then i had to leave.
Up to now, my phone is still dead and i have no idea what to do. It only enters download mode, but at the same time, this is useless since flashing anything simply does not work. Anyone knows what the reason could be?
FYI, i was on NeatROM 5.5, which comes with Philz Kernel.
NAND is stuffed/corrupted. How/why - who knows ? Motherboard replacement if you've already tried JTAG. Could be something hardware going on that caused the chip to become 'damaged'.
Related
Hi Guys
I was having some trouble connecting my Galaxy S2 to my comp this evening to transfer some photos. Downloaded and installed Kies and it said there was a software update. Went through with it, upgrading to Icecream Sandwich (or w/e its called) but during the installation process it failed (can't remember the exact error message).
My phone is now unable to switch on, just showing the error message:
"Firmware upgraded encountered an issue. Please select recovery mode in Kies and try again."
Unfortunately, Kies will not locate my device and will not go through with recovery.
After some searching I came accross this forum, and specifically http://forum.xda-developers.com/showthread.php?t=1449771]this thread.
I've worked my way through that. I can flash the kernel succesfully through Odin (says pass) but when I try and flash the firmware it fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_NEW_BOOTLOADER.tar.md5 is valid.
<OSM> I9100PBVKL2_I9100PORALB1_I9100PBVKL2_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Get the same trying to use Bootloader aswell.
Now I'm guessing my warranty is now voided, so is there anything I can do to save my phone or is it completely b0rked?
Help much appreciated.
Some details from under my battery
Model GT-I9100P
SSN: I9100PGSMH
Any other details you need?
Bare in mind i cannot get into the phone at all.
Is it possible that I need to use the ICS recovery package rather than the Gingerbread?
i think u need full rom with pit and ur phone will work
Hi, thanks for your reply.
Unfortunately I'm in work and don't have a comp with full access. Any chance you could possibly link the files I need or at least point me in the right direction.
Many thanks.
I had an i9300 that was running the 20130621-nightly CM-10.1-build, with either 6.0.3.2 CWM touch or 6.0.3.1. It suddenly started freezing and hanging randomly, and it would either reboot, FC the app or go to the home screen after 5-30 minutes.
- I tried wiping the data, cache and dalvik, but it didn't help.
- I flashed the 20130619-nightly, but that didn't help either.
- I also used the dummy file-method described here: http://forum.xda-developers.com/showthread.php?t=2133401&highlight=unusual+freezing
but it didnt trigger the freeze. However, I couldn't test it fully, as the app would constantly FC as I tried to open it after writing the first dummy file. I went into the app-settings to wipe it's data, but then the phone froze again, and I moved on.
- I then used http://forum.xda-developers.com/showthread.php?t=1671969&highlight=triangle
to flash a stock firmware, namely this one:
GT-I9300_NEE_I9300XXALE8_I9300NEEALE3_I9300XXLE8
It booted into the initial setup-walkthrough, but it froze again within minutes. As I tried to reboot it by pulling the battery, I got stuck at the Samsung Galaxy SIII logo, not the flashing Samsung logo. I realized there was also a kernel-file linked below the firmware I downloaded:
Kernel_I9300XXALE8
As I tried to flash it Odin reported this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Kernel_I9300XXALE8.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>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The same is reported when flashing the firmware again.
I then downloaded a .pit file I found in the same thread, and flashed the .pit file and the kernel file.
GT-I9300_mx_20120329
This was reported by Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Kernel_I9300XXALE8.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>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The same is reported when flashing pit & firmware.
Download mode reports the following:
Odin Mode
Product name:
Custom binary download: No
Current binary: Samsung Official
System status: Custom
Click to expand...
Click to collapse
It seems I can't boot into recovery, and right now I'm scared and afraid to break it even more..
Mate, you have sds (see my sticky thread in general).
The freezes were the sds fix kicking in. Then you flashed an ics component that had no sds fix and you actually allowed / caused your phone to die from sds.
Send for repair because you need new memory chip / motherboard
Sent from my GT-I9300 using Tapatalk 2
Awesome.
Just to be clear, is there really nothing else to do? Could I try flashing a JB-firmware?
In retrospect, could I have saved it by sticking to the DFG-method?
Should I do anything to change the info in Download-mode, for warranties sake?
Thanks for the quick answer though, it's just that I'm going on a month-long vacation on monday, so I was kinda hoping to bring a working phone!
There is literally nothing you can do. With anything. All you can do is send it for repair and hope for the best.
The phone only died when flashing ics. The dfg may or may not have prevented the freezing but either way it wouldn't have died
Sent from my GT-I9300 using Tapatalk 2
I still find it weird that it booted to ICS once, and then died, but I guess it had to actually boot as ICS to die or something..
Thanks for the help though!
Viftee said:
I still find it weird that it booted to ICS once, and then died, but I guess it had to actually boot as ICS to die or something..
Thanks for the help though!
Click to expand...
Click to collapse
Yeah, I don't find it weird. ICS opened the door as it were. The memory was ready to die but the fix prevented it (thats what the freezes were) so as soon as something without the fix was there, there was nothing to prevent the memory going.
Please help.
i tried to do a stock restore using the method here http://forum.xda-developers.com/show....php?t=2657828 and there was an error. i did this before and it worked now it failed.
<ID:0/003> 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/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> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
the phone doesn't want to start and it says " firmware upgrade encountered an issue. Please select recovery mode in kiess & try again." i tried that but i doens't work. if i start the odin one-click exe. it tries to instal and i get the same error.
what can i do to restore my android?
Edit: i think i fixed it. i tried the file i had 3~4 times and nothing so i downloaded the nab stock rom fromhttp://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20Note%203%20%28SM-N900P%29/Stock%20ROMs/ and it's installing now. i hope there are no more isues.
Valentin6282 said:
Please help.
Edit: i think i fixed it. i tried the file i had 3~4 times and nothing so i downloaded the nab stock rom fromhttp://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20Note%203%20%28SM-N900P%29/Stock%20ROMs/ and it's installing now. i hope there are no more isues.
Click to expand...
Click to collapse
The NAB file will fix your issues, but I'll address what happened so others can see this thread and learn.
On the Note 3, once you're on Kit Kat (NAB or NC5), you cannot downgrade to Jellybean (MJ4).
Trying to do so will cause the error in OPs post.
There are tons of repositories where you can get stock NAB or NC5 TW Roms (taking a stroll through the Developers Section will find them easily), so all you have to do is try one of those and all of your issues will be solved.
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> 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)
ALL HELP IS MUCH APPRECIATED!!:good:
Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.
Definitely need to flash newer firmware
degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_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> 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)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.
Hello guys. I just made a new account for this problem. I will really really appreciate if u guys help me out, because my parents are gonna kill me if they find out my phone has a fault. So here it is.
A few weeks back i rooted my phone but then snapchat stopped working because of its new policy or something and i decided to unroot the phone. In an act of stupidity i unrooted the phone through SuperSU complete unroot and ignored all the warnings. I know im an idiot (Please help me out folks) Then my phone got stuck on bootloop. I searched it up and found solutions through ODIN and all. So thats what i did. I dowloaded the drivers and downloaded odin. Ran my phone in the downloading mode. Btw i did delete the cache through recovery mode and have already reset it as well through their and nothing happened. So back to the ODIN. I downloaded the firmware, stock one. The problem is i dont know which on to download. Thus far i have downloaded two which are, G920TUVU5EPK5_G920TTMB5EPK5_G920TUVU5EPK5_HOME.tar.md5 and G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5. As seen in the tutorial, i put the phone in download mode and ran odin. There at first the <ID:0/008> Added!!
was shown as soon as i connected. But when i added the PDA file, it didnt detect it and remained the same at 008. So i went ahead with the start and this is what it says,
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU5EPK5_G920TTMB5EPK5_G920TUVU5EPK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This was the case for both the stock firmwares. PLEASE SOMEONE HELP ME OUT. I cant let my folks find out. Can any of u answer this as quickly as possible? PLEASE! IT'D be a huge help.