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.
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.
Please help.
i tried to do a stock restore using the method here http://forum.xda-developers.com/showthread.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?
Valentin6282 said:
Please help.
i tried to do a stock restore using the method here http://forum.xda-developers.com/showthread.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?
Click to expand...
Click to collapse
You should ask your question in : Sprint Galaxy Note 3 Q&A, Help & Troubleshooting
http://forum.xda-developers.com/note-3-sprint/help
They will answer and help you, this section belongs to "Android development only".
Good luck.
ok thank you
I'm that's mj4 from a quick look. If you were on 4.4.2 nab or even nc5 and tried flashing that mj4 in Odin. You more then likely bricked your phone. It's posted all over that you can't downgrade. If download is still accessible. I suggest downloading nc5 flash that via Odin.
Sent From My 0x1 Note 3.i love tep....
kaos420 said:
I'm that's mj4 from a quick look. If you were on 4.4.2 nab or even nc5 and tried flashing that mj4 in Odin. You more then likely bricked your phone. It's posted all over that you can't downgrade. If download is still accessible. I suggest downloading nc5 flash that via Odin.
Sent From My 0x1 Note 3.i love tep....
Click to expand...
Click to collapse
yap i was on nab and i tried to flash mj4. didn't know about the downgrade problem. i got nab and flashed it and it works, and now i decided to flash nc5 so i'm doing that and it seams to work.
thank you for your reply!
Valentin6282 said:
yap i was on nab and i tried to flash mj4. didn't know about the downgrade problem. i got nab and flashed it and it works, and now i decided to flash nc5 so i'm doing that and it seams to work.
thank you for your reply!
Click to expand...
Click to collapse
You got super lucky. Be very happy it didn't install. Lol
Sent From My 0x1 Note 3.i love tep....
As stated above questions and request for assistance belong in the Q&A section not in the Development section. Thread moved. Thank you for your future cooperation with this and all other XDA rules.
EFM
Have a great day!
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.