Hello everyone,
I have installed Resurrection Remix (Resurrection_Remix_KK_v5.1.5-20140609-i9100) and suddenly my phone turned off and stucked at the boot logo.
I can't start the recovery mode only the download mode is possible.
I have tried to reflash the recovery but it doesn't work. I have tried different cables and PCs without any success. I also tried different odin versions.
I think I have a NAND rw issue.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSD-OXX-4.93.6.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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
I have read different threads about stucked phones, but I am unsure which recovery package would be the right one, f.e. http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571
I just want to save as much as possible.
Every help is appreciated.
h3llghost said:
Hello everyone,
I have installed Resurrection Remix (Resurrection_Remix_KK_v5.1.5-20140609-i9100) and suddenly my phone turned off and stucked at the boot logo.
I can't start the recovery mode only the download mode is possible.
I have tried to reflash the recovery but it doesn't work. I have tried different cables and PCs without any success. I also tried different odin versions.
I think I have a NAND rw issue.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSD-OXX-4.93.6.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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
I have read different threads about stucked phones, but I am unsure which recovery package would be the right one, f.e. http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571
I just want to save as much as possible.
Every help is appreciated.
Click to expand...
Click to collapse
Do you installed Samsung drivers firstly? If no, download this and install. Restart PC.
If yes,
Download this kernel (Apollo kernel with TWRP) and flash it! after, you can install what ROM do you want! If you want KK install CM11-M12.
Hit Thanks button if I helped you!
IonutGherman said:
Do you installed Samsung drivers firstly? If no, download this and install. Restart PC.
If yes,
Download this kernel (Apollo kernel with TWRP) and flash it! after, you can install what ROM do you want! If you want KK install CM11-M12.
Hit Thanks button if I helped you!
Click to expand...
Click to collapse
Same odin output as before.
h3llghost said:
Same odin output as before.
Click to expand...
Click to collapse
What version of ODIN do you use?
I have tried 1.8.3, 3.1.6 and the latest one.
try this: http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
IonutGherman said:
try this: http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
Click to expand...
Click to collapse
I have two issues with that, which package should I choose and the downloads are not available for Germany. Is there another mirror?
Related
ive gotta major problem with my device. after trying to flash a stock rom (it crashed while flashing) i m unable to flash any rom. everytime i try to flash another one it says
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXEMB5_I9300OXAEMB5_996085_REV00_user_low_ship.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.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
"
i almost tried everything... i only can access the download mode on my phone... even the recovery is gone .
please help me fellas
thanks in advance !
Try flashing only a recovery (CF, Perseus, TWRP, etc) through ODIN and check if it is successful. The log seems to error out when flashing the recovery.
If successful, try flashing the stock ROM again.
If not, download another stock ROM and check if you can install it.
Just speculations. Dunno if it will actually work. The last resort is, of course, the service centre. Good luck! :thumbup:
Sent from my GT-I9300 using xda app-developers app
I had the same problem mate. You just need to flash the stock recovery using PC ODIN. Once you've flashed the stock recovery, you'll be able to flash any ROM properly. Im 99% sure this will work.
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. ^^
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
xMopx said:
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
Click to expand...
Click to collapse
You can't flash backwards. Flash me7.
gnubian said:
You can't flash backwards. Flash me7.
Click to expand...
Click to collapse
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
xMopx said:
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
Click to expand...
Click to collapse
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
xMopx said:
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
Click to expand...
Click to collapse
Just go to the safestrap app in app drawer on stock slot and uninstall it.
gnubian said:
Just go to the safestrap app in app drawer on stock slot and uninstall it.
Click to expand...
Click to collapse
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
xMopx said:
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
Click to expand...
Click to collapse
What happens when you start the phone?
gnubian said:
What happens when you start the phone?
Click to expand...
Click to collapse
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
xMopx said:
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
Click to expand...
Click to collapse
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
gnubian said:
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
Click to expand...
Click to collapse
Positive. I had installed the rom/recovery before anything newer than me7 was released. And I remember when I upgraded from whatever it shipped with to ME7 because the upgrade window popped up and I tapped Install by accident. I had this installed: http://forum.xda-developers.com/showthread.php?t=2351840.
Edit: to confirm, I found my old post asking about the modules to get that rom to work on ME7: http://forum.xda-developers.com/showthread.php?p=46944438
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
gnubian said:
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
Click to expand...
Click to collapse
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
xMopx said:
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
Click to expand...
Click to collapse
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
gnubian said:
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
Click to expand...
Click to collapse
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
xMopx said:
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
Click to expand...
Click to collapse
Try finding a stock recovery tar for your build and just flashing that in odin.
gnubian said:
Try finding a stock recovery tar for your build and just flashing that in odin.
Click to expand...
Click to collapse
I had the thought of doing this, but wasn't able to find one.
xMopx said:
I had the thought of doing this, but wasn't able to find one.
Click to expand...
Click to collapse
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
gnubian said:
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
Click to expand...
Click to collapse
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
xMopx said:
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
Click to expand...
Click to collapse
I believe it has to be a tar. If you can get it on there and wipe data/factory reset it may get rid of safestrap and allow you to odin the full stock tar.
Hi there,
it's matteios1984 first of all i'd like to say hello to the comunity and thank you all for interesting post about Android!
I'm here to asking help about a tricky case. I've a Samsung Galaxy S3 (i9300) bricked. In other words the phone behaves as follow:
- If i try to turn on the device it remains stuck on Samsung S3 logo
- No possible to boot in recovery mode
- When I connect it to the charger it's stucked showing the battery image and not showing any progress about charging status
- The device is still able to boot in download mode both with buttons combo and with resistor trick, but Odin is not able to flash anything on the device (my idea is to flash a Customer Recovery, perform a full wipe of the device and after restore original italian firmware)
Here following a log taken from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If i try to flash a file containing PIT informations here following the log from Odin:
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've heard about the possibility to boot the device by a MicroSD card that allows me to flash the device... Do you think this will fix my issue? Or do I need a box? If so, any suggestion about the model is appreciated.
Thanks in advance for your support
Try downgrading the bootloader to BLFB before flashing firmware or pit.
i have galaxy s3 the international model
right now it stucks on the logo. i can get into download mod, but not into recovery.
i've tried to flash stock version. i used first the one file method . didn't work, then i tried the 4 files method
with bootloader etc... but it failed again.
i changed cables, usb ports, nothing!
here's the odin log.
___________________
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMG4_I9300ITVEML2_I9300XXEMG4_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.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
could it be an hardware issue. or theres still chance
thanks..
Check if it says "Custom" on "Current Binary"
This is probably a cause of half SDS(Sudden Death Syndrome),basically your device is dead
Dinkec27 said:
Check if it says "Custom" on "Current Binary"
This is probably a cause of half SDS(Sudden Death Syndrome),basically your device is dead[/Q
in download mode it says:
custom binary download: no
currnet binary: samsung official
system status: official
so maybe its not??
Click to expand...
Click to collapse
I think your device is dead
tyler6389 said:
I think your device is dead
Click to expand...
Click to collapse
i think too, but is there any last options i could try.. like flash it with pit files???