Hi,
Yesterday my GT-I9100 stopped working. I was just charging it when it turned off and after that it wouldn't boot normally and got into a bootloop just displaying the Siyah boot screen.
I was using stock JB 4.1.2 with a Siyah 6.0b5 kernel and it's been running for several months now, which is why I don't really understand how I could brick the device without changing anything.
I can't get into the Recovery Mode, but the Download Mode does work.
I tried to flash the stock kernel first and then some other custom kernels (e.g. PhilZ), but Odin gets stuck at the same place every time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSZ-OJC-5.15.9.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> zImage
<ID:0/008> NAND Write Start!!
After that I tried to flash the whole stock firmware (1 part as well as 3-part versions and different ROMs), but it still got stuck every time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100VIALS6_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> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> cache.img
I tried following many of the guides for soft bricked phones in the forum and as recommended in several threads, I tried using different Odin versions, rebooting my PC and so on, but nothing helped.
Instead of the Siyah bootscreen that I had at the beginning, I now have the standard screen saying 'Firmware upgrade encountered an issue....'
Has anyone experienced something like that before and is there something I can do to revive my S2?
Find Hopper8's 'Odin troubleshooting' thread. Try all the stuff in that thread over & over. That's the only way you're fixing it. Otherwise it's a service centre job. Tho I'd be surprised if you don't manage to fix it eventually, these cases are often fixed with persistence - the first 8 flashes you try fail, but for whatever reason the 9th works (as an example).
MistahBungle said:
Find Hopper8's 'Odin troubleshooting' thread. Try all the stuff in that thread over & over. That's the only way you're fixing it. Otherwise it's a service centre job. Tho I'd be surprised if you don't manage to fix it eventually, these cases are often fixed with persistence - the first 8 flashes you try fail, but for whatever reason the 9th works (as an example).
Click to expand...
Click to collapse
I've been trying that for over 6 hours now and I'm slowly starting to doubt if I can win the Odin jackpot. Since it always gets stuck when writing NAND, could there be an issue with it?
Possibly, but given the alternative (I.E you paying a not insignificant amount of money to have it fixed), if I were in your situation I'd be trying for a lot longer before declaring a stuffed NAND, unless forking out a lot of money to have it fixed isn't an issue for you.
There is no simple fix in this situation.
MistahBungle said:
Possibly, but given the alternative (I.E you paying a not insignificant amount of money to have it fixed), if I were in your situation I'd be trying for a lot longer before declaring a stuffed NAND, unless forking out a lot of money to have it fixed isn't an issue for you.
There is no simple fix in this situation.
Click to expand...
Click to collapse
Ok, I'll continue trying. Thanks for your advice. Do you think it makes sense to try flashing the same file with the same Odin version over and over or should I rather change something each time I try?
I'd be trying different stock roms (doesn't really matter which, but stay away from 4.0.4) & with different versions of Odin. Find Hopper's thread, try everything in the thread if you need to.
Related
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.
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'.
Hey Guys,
i guess i need your help. I've flashed diffrent ROM's with Odin before so i got an rough idea how it works.
Story so far:
GT-I9100 4.1.2 Official ROM (I9100XWLSD_I9100DBTLS7_DBT) with PhilZ Kernel (PhilZ-cwm6-XWLSD-OXX-4.87).
Phone swithed itself off for any reason and i tried to reboot it. Phone started up and was stuck at the screen with "Samsung Galaxy S II". Nothing happened for like an hour. After waitin i decided to flash the ROM again. And here it just got worse.
Using Odin3 v1.85 (Kies tasks killed, original samsung usb cable) i selected the ROM mentioned above and tryed to flash it. At first everything was running good, but the i got stuck at:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
i left it for half an hour or even more... nothing happened. I tried to flash Philz Kernel again, but i got stuck too.
Same for ICS ROM and GB.
I can't get into recovery mode (which i should have done before thinking of flashing stuff )
Download mode is all i can choose now. I'm not getting any further right now.
Can anyone help me with this? I'm quite bummed out. I need my phone
Thanks in advance.
Daniel.
i.am.dirt said:
Using Odin3 v1.85 (Kies tasks killed, original samsung usb cable) i selected the ROM mentioned above and tryed to flash it. At first everything was running good, but the i got stuck at:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
i left it for half an hour or even more... nothing happened. I tried to flash Philz Kernel again, but i got stuck too.
Same for ICS ROM and GB.
I can't get into recovery mode (which i should have done before thinking of flashing stuff )
Download mode is all i can choose now. I'm not getting any further right now.
Click to expand...
Click to collapse
Odin flash fails? Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
immortalneo said:
Odin flash fails? Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Click to expand...
Click to collapse
Thanks for that fast reply. I've skimmed over that guide and i have to say i've already tryed nearly all of it... that's a bad sign, huh?
I'll try diffrent Odin versions but i've been reading nearly everywhere that v1.85 is the correct version for my GT-I9100...
i.am.dirt said:
Thanks for that fast reply. I've skimmed over that guide and i have to say i've already tryed nearly all of it... that's a bad sign, huh?
I'll try diffrent Odin versions but i've been reading nearly everywhere that v1.85 is the correct version for my GT-I9100...
Click to expand...
Click to collapse
It wouldn't hurt to try then, would it?
Believe me when I say this, but a lot of members have reported this issue before, which led to the creation of the above guide. And its instructions are based to an extent on the successes reported by some members. So try all you can and see what happens! :good:
I've tried to figure it out to what extend different ODIN versions will give different results. Here's what i've been encountered with:
v1.3:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> cache.img
got stuck at cache.img
v1.83:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> cache.img
got stuck at cache.img
v1.85:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
same sh!t here
v3.04:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
what a surprise!
v3.06:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
failed for any reason
v3.07:
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
it doesn't get any better
Seriously what is going on with that device?
Seems like it doesn't matter which ODIN version i use... the results are poor.
Any suggestions?
i.am.dirt said:
Seriously what is going on with that device?
Seems like it doesn't matter which ODIN version i use... the results are poor.
Any suggestions?
Click to expand...
Click to collapse
Keep trying out everything in that guide and in every possible combinations you can, until you're absolutely sure that your phone's NAND is borked. Then take it to a Service Centre.
Flash a packaged ROM (modem, code & csc) with the 3.06 version.
Sent from...this is not even my S2
i91000 brick at cache
Any ideas for this thread ? I have a simmilar problem, my i9100 can't flash any software any kernel ?
milo_sc said:
Any ideas for this thread ? I have a simmilar problem, my i9100 can't flash any software any kernel ?
Click to expand...
Click to collapse
i have same problem with my s2. did you fix it ? please reply fast
Same issue. Was this ever resolved? I can't even get the tablet to stay powered off now!
NickSaul said:
Same issue. Was this ever resolved? I can't even get the tablet to stay powered off now!
Click to expand...
Click to collapse
Has anyone tried gastonw's advice yet?
I was having the exact problem described in the original post on my Galaxy Note Pro 12.2 (SM-P900 wifi). I was able to fix my device by flashing TWRP through Odin. This allowed me to reboot my device as normal.
After I was able to boot back into my device, I went into developer options and realized that USB Debugging was NOT enabled. I ticked the box and reset back into Download mode. This time, the Odin flash went smoothly and quickly and I now have a rooted Note Pro 12.2.
So for those of you who are having Odin fail at flashing cache.img, try my solution and let me know if it works.
#1. Download TWRP (I got mind from the official TWRP website)
#2. Flash TWRP through Odin in the same method that you flashed CF Auto Root
#3. Boot into your device normally and open Developer Options in the Settings Menu
#4. Enable USB Debugging
#5. Connect your tablet to your PC
#6. A pop-up window will arise on your tablet asking to Allow the connected computer to debug your tablet; tap OK to Allow it
#7. Reboot into download mode
#8. Reflash CF Auto Root using Odin
These steps worked for me so hopefully they can help someone else out as well
justb2 said:
I was having the exact problem described in the original post on my Galaxy Note Pro 12.2 (SM-P900 wifi). I was able to fix my device by flashing TWRP through Odin. This allowed me to reboot my device as normal.
After I was able to boot back into my device, I went into developer options and realized that USB Debugging was NOT enabled. I ticked the box and reset back into Download mode. This time, the Odin flash went smoothly and quickly and I now have a rooted Note Pro 12.2.
So for those of you who are having Odin fail at flashing cache.img, try my solution and let me know if it works.
#1. Download TWRP (I got mind from the official TWRP website)
#2. Flash TWRP through Odin in the same method that you flashed CF Auto Root
#3. Boot into your device normally and open Developer Options in the Settings Menu
#4. Enable USB Debugging
#5. Connect your tablet to your PC
#6. A pop-up window will arise on your tablet asking to Allow the connected computer to debug your tablet; tap OK to Allow it
#7. Reboot into download mode
#8. Reflash CF Auto Root using Odin
These steps worked for me so hopefully they can help someone else out as well
Click to expand...
Click to collapse
Thx! good answer for unbricking my phone but... still get the same error with enabled debugging mode
CryserCore said:
Thx! good answer for unbricking my phone but... still get the same error with enabled debugging mode
Click to expand...
Click to collapse
I have the same problem with my s3 neo! I tried to root my phone with Odin , and phone now is bricked. Firat i have installed TWRP , und everything was fine. Than , i tried to flasch superuser to get my phone rooted. Now i can´t reach TWRP (??) , and only thing that i can do ist download mode.
I am tryin to flasch stock firmware through Odin, but ever the same - cache.img error! Help please!
Hi
Please anyone help me
I am also having the same error. It stucks at cache.img. I am trying I9100XWLPT_I9100XXLQ6_I9100XEULPA_HOME.tar.md5 downloaded from sammobile.com
My model is GT-I9100 .
Can anyone help please ?
Earlier , i was having cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100.zip and one day, it all gone bad. I can only use Odin mode.
I cannot even go to Recovery mode.
I tried boot.bin alone and that runs fine and it shows me Samsung logo screen.
I then tried renaming cache.img to cache.img.tar and that also runs fine .
But overall, it does not run when i think it tries to write to Nand or whatever.
I have tried all version of odin and various cables as well.
Any help will be hugely appreciated.
best regards
I had the same problem.....resolved it by extracting the tar.md5 file to the c:/ directly instead of the desktop...
Yo.
Had the same issue on the GT-I9506.
The issue occurred for me after I had accidentally attempted to flash an auto-root file to bootloader in ODIN, can confirm that flashing CWMR as through PDA solved my issue, as I was then able to flash the same auto-root file direct through PDA.
Hope this helps somebody, as I wasted an hour ****ing around trying to figure out how to fix. ^^
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.
Apologies if this has already been dealt with but Ive looked and cant find solution anywhere, 2 weeks looking through forums so far or I'm looking at wrong solutions or Im stupid and and keep following bread trails that take me into the nether regions of cyberspace never to be heard of again. I am trying to restore this phone for my son.
SGS2 will only go into download mode, (No Recovery mode no matter what - it freezes at Device name and model number) maintains a freeze at normal boot onto logo screen.
Bought new battery and new data sync cable.
Kies wont even install, moved to another PC. Kies installed but wont recognise Device, updated all drivers, removed driver reinstalled drivers dozens of times no luck. Please don't make me go back to Kies……
I have tried flashing stock rom with ODIN details below.
Odin v 3.07, have tried all other versions no luck this one advanced furtherest.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100TDVOF1_I9100TTELOF1_I9100TDVOE1_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> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
This is the most successful attempt of 20 attempts to reflash.
Tried Heimdall got stuck at Heindall frontend trying to locate firmware packages?? Gave up.
Is it Bricked or can it be saved? Any help from compassionate experts would result in a significant reduction in hair loss for me. I really don't want to go back to iPhone.
Update
SGS2Nutter said:
Apologies if this has already been dealt with but Ive looked and cant find solution anywhere, 2 weeks looking through forums so far or I'm looking at wrong solutions or Im stupid and and keep following bread trails that take me into the nether regions of cyberspace never to be heard of again. I am trying to restore this phone for my son.
SGS2 will only go into download mode, (No Recovery mode no matter what - it freezes at Device name and model number) maintains a freeze at normal boot onto logo screen.
Bought new battery and new data sync cable.
Kies wont even install, moved to another PC. Kies installed but wont recognise Device, updated all drivers, removed driver reinstalled drivers dozens of times no luck. Please don't make me go back to Kies……
I have tried flashing stock rom with ODIN details below.
Odin v 3.07, have tried all other versions no luck this one advanced furtherest.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100TDVOF1_I9100TTELOF1_I9100TDVOE1_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> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
This is the most successful attempt of 20 attempts to reflash.
Tried Heimdall got stuck at Heindall frontend trying to locate firmware packages?? Gave up.
Is it Bricked or can it be saved? Any help from compassionate experts would result in a significant reduction in hair loss for me. I really don't want to go back to iPhone.
Click to expand...
Click to collapse
Have attempted to Pit with stock image ..also failed..