[Q] Flashing ROM with Odin - stuck at cache.img - Galaxy S II Q&A, Help & Troubleshooting

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. ^^

Related

[Q] Rooting"stuck at boot.img

This is my first time rooting any android device.
I have done the following already
1. Installed Drivers with Kies
2. Installed Odin3
3. Downloaded the .md5.tar pre-rooted file 1.1 gb
4. Went into Odin, And selected PDA and choose the .tar file
5. Unchecked the Re-Partion
But! for some reason, it will stop at boot.img
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> prerooted.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
And it will stop. Im using the Samsung USB, and ive changed ports. Nothing seems to work! Help! D:
xxtoxicriotxx said:
This is my first time rooting any android device.
I have done the following already
1. Installed Drivers with Kies
2. Installed Odin3
3. Downloaded the .md5.tar pre-rooted file 1.1 gb
4. Went into Odin, And selected PDA and choose the .tar file
5. Unchecked the Re-Partion
But! for some reason, it will stop at boot.img
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> prerooted.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
And it will stop. Im using the Samsung USB, and ive changed ports. Nothing seems to work! Help! D:
Click to expand...
Click to collapse
would be best if you download stock firmware from sammobile for your sgs3 and flash it again and than download cf auto root for rooting sgs3. u should read guides properly on how to root sgs3 here at xda. i ts available in general sgs3 forum.. if any problem presist or if u need help u can pm me..
Odin won't work with kies installed, you only needed the drivers which come separately.
xxtoxicriotxx said:
This is my first time rooting any android device.
Nothing seems to work! Help! D:
Click to expand...
Click to collapse
Make sure Kies is not running at the same time as Odin and use CF auto root as suggested by suyash1629 the link is in my signature

[Q] Samsung galaxy s3 i9300 rebooting ( bricked? )

hi all,
i have a samsung galaxy s3.
when i boot the phone it's flashing at the text samsung galaxy i9300 for 1 sec and reboot again in a loop
i had cyanogenmod 11 installed on it, but wanted to go back to stock firmware.
what i dit was this:
i download the original firmware for my phone and region. ( Netherlands ) PHN-I9300XXEMH1-20130828150847
1: start odin3 (v1.85 )
2 load the md5 into the PDA section
3 put my phone in download mode
4 connect it to pc.
5 start odin.
the only thing i get is this:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMH1_I9300PHNEMG2_I9300CEEMG2_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.img
<ID:0/007> NAND Write Start!!
And is stays on that for 1-2 hours.
can someone please help me out?
Not good, try a later version of odin first.
Sent from my GT-I9300 using Tapatalk

[Q] Soft bricked SCH-I545!! HELP PLEASE!!!

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.

Help to recover a S2 stucked on boot logo

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?

Please, please help me. Bricked samsung galaxy j7

I attempted to root my phone through Odin pushing superuser and twrp onto it as tutorials told me to do, and my phone literally goes to the boot logo and then stops. I have tried a million times to flash a stock rom back onto it but it won't push through either Odin or TWRP without error messages. It lets me flash a cyanogenmod rom through TWRP but the screen just goes back when I boot it up. Is my phone done for? Can I fix this somehow?
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
es0tericcha0s said:
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
Click to expand...
Click to collapse
I have tried using both Odin3_v3.10.6 and Odin3 v3.12.3. The files I have attempted to flash are XSG-J700HXXU2BPF9-20160629164434, CAU-J700HXXU1APA3-20160106083224, SM-J700H_J700HXXU1AOK5_J700HOLB1AOK1_5.1.1-MYM, and J700FXXU1AOL2_J700FODD1AOL1_INS_(by_firmwarefile.com).
My phone's model number is J700H/DS. The error I am receiving is <ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J700HXXU1APA3_J700HOXY1AOL1_J700HXXU1AOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cm.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
from Odin and
"sw. rev. check fail. device:2, binary:1" on my phone's screen
Thank you for your reply, I am actually incredibly stupid and left the DS out of my model number and was therefore getting the wrong firmwear. I fixed it.

Categories

Resources