Dear Friends
I tried to upload new Rom to my Samsung Galaxy S2 but it field and now even I can't get download mode only what I get is picture of (device---Attention---PC),
could you help me to get download mode again?
...
MistahBungle said:
That is download mode. Forced download mode. It's forcing you to flash something to get it going again. Flash a stock rom in Odin.
Click to expand...
Click to collapse
Thanks Man to reply, could you help me to official Rom to download it please?
...
The link below is a thread containing instructions on how to flash a stock firmware and also a list of the stock firmwares that are available.
http://forum.xda-developers.com/showthread.php?t=1075278
Sent from my GT-I9100 using Tapatalk 2
MistahBungle said:
Here or Samfirmware. Or even the PC version of Checkfus. I'd try the first two places initially.
Click to expand...
Click to collapse
Thanks Man,
I will do my best...
...
MistahBungle said:
No probs. Follow the flashing instructions in the thread that Nicholas1520 linked to. Any issues, post here. But have a go at it yourself first. You'll learn plenty going thru this
Click to expand...
Click to collapse
OK thanks boys,
I'm going throw it carefully and I will post anything later
MistahBungle said:
No probs. Follow the flashing instructions in the thread that Nicholas1520 linked to. Any issues, post here. But have a go at it yourself first. You'll learn plenty going thru this
Click to expand...
Click to collapse
Dear Friends,
I downloaded two of these Roms, and I can see the device downloadable in Odin3 and I selected in PDA then I pressed start, the software (Odin3) start to upload till I got Fail...
see this codes:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_ITV_I9100XWLPF_I9100OXILP6_I9100XXLPX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try using Odin 1.85:
http://db.tt/XSY1G5Ye
You should try another firmware and see of that's the case because your doing everything good so far.
Sent from my GT-I9100 using Tapatalk 2
nicholas1520 said:
Try using Odin 1.85:
http://db.tt/XSY1G5Ye
You should try another firmware and see of that's the case because your doing everything good so far.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Ok I will do my best with it,,, I will inform you later,,,
...
MistahBungle said:
Also, after you open Odin & before you start flashing, make sure you check Windoze Task Manager & close Kies/any associated processes if they're running.
And...Do you definitely have an I9100 or I9100T ? Check the sticker on the phone chassis under the battery to be doubly sure if you need to.
Click to expand...
Click to collapse
Ok, I'm already Using v.1.85 and I tried again by using different USB cable, my Device is I9100G, I did start again and its freezing now see this :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_ITV_I9100XWLPF_I9100OXILP6_I9100XXLPX.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..
...
MistahBungle said:
OK. There's your problem right there. You have an I9100G. I think you'll find you tried to flash a rom for the I9100/T which caused it to get into a state where it won't boot/forced download mode.
You need to download & flash an I9100G stock rom. I don't have any experience with the I9100G (apart from seeing posts on here from people who have them), but look in this thread (I don't know which one you should use tho).
Edit - And be careful in future, only flash roms/kernels specifically for the I9100G
Click to expand...
Click to collapse
OK, I will check it carefully.... Thanks for your support...
alisaher2000 said:
OK, I will check it carefully.... Thanks for your support...
Click to expand...
Click to collapse
Dear Friends,
I solved it by applying uploading Rom for I9100G via Odin3 v.1.85... Thanks for all supports....
:good:
...
Related
I installed CWM touch, and superuser zip folder on my Galaxy note (att)
So I read a tut that said to wipe everything so I did on recovery mode, booted it up, worked good, went back because superuser didnt work right. I installed 3-4 times before it said success, now its goes to a crisp samsung logo, then goes blurry and stops.....
Stupid noob mistake I didnt backup anything. Figured it was simple as jailbreaking an iphone (which you cant mess up on, plug in, hit button, done)
I been trying it all but just cant get it to work.
If your phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
jayRokk said:
If youre phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
Click to expand...
Click to collapse
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
It boots to the samsung logo, but not lock screen. And I'm phoneless now Lol.
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
welchertc said:
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I been reading alot but seems like there is a hundred different explanations or ways to do it, and hard to find the right way?
liftedzuki said:
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
Click to expand...
Click to collapse
Yes its a .tar file
And search for it buddy there is a whole thread on official ICS and with it the CWM file and SU file to get you going
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
liftedzuki said:
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
jayRokk said:
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
:silly: I got it from a link in this note section, I should have seen that though.
So if I flash it, does it flash over the other flash? or does it add to it.
I'll continue readin.
Not all Samsung's are the same. You should only be getting tar files from your specific section. Keep in mind you need to match the model number
Sent from my SPH-L710 using Tapatalk 2
I would suggest going here and flashing one of these one clicks in Odin:
http://forum.xda-developers.com/showthread.php?t=1647756
Sent from my SPH-L710 using Tapatalk 2
And if I'm not mistaken you want the first link. I don't have a note so maybe someone here can chime in.
Sent from my SPH-L710 using Tapatalk 2
That link worked good. Thanks so much to everyone, I about had a heartache as I got my phone like 3 months ago, and just got ICS on it.
This time I'm gonna read alot more before I try it again.
Good idea. Glad it worked. If ya ever have any questions in the future , don't hesitate to ask BEFORE flashing.
Sent from my SPH-L710 using Tapatalk 2
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Haha it happens. Just be glad ya didn't end up with a huge note shaped paperweight
Sent from my SPH-L710 using Tapatalk 2
liftedzuki said:
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Click to expand...
Click to collapse
OP if your good to go, can you put Solved in your title....
thank you sir
Dear Friends
I HAVE MESS-UP WITH MY i9300!!!!
The incident is I was using custom rom, and installed some stupid app called "Adblock" or something,
and then, my phone just keep went-off for about 8-10 times a day. So then, I decided to reflash
custom rom by CWM, and after I pressed install in Aroma Installer, it just kick me out all of sudden, and
then, I couldn't get back to CWM anymore, so I decided to flash some stock rom by odin, but what
had happen was it starts until "Nand write start" and stacked for a while, and then just FAIL me.
On the net, I found that Checkrom Resurrection V4 could rescue softbrick i9300, I tried, but
no luck either. Finally, just now, I tried a 3 files stock rom with pit, and it came out as:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
What I have done:
1. reflash custom rom by CWM
2. 3 wipes - (but I am no longer to get back to CWM)
3. flash stock rom - hong kong combo firmware @ Samfirmware - by Odin
4. flash Checkrom Resurrection V4 by Odin
5. flash stock rom - 3 files firmware + pit - by Odin
6. changed usb port
7. changed PC
8. uninstall all applications relative to Kies
have you guys got any idea what can I do? I am thinking to mess-up the phone even badly (till it couldn't switch on), so that I can take it to Samsung Service Center for warranty replacement, but have you got ANY method I can do that to mess it up? Or anything I can over-come from the soft (or hard) brick. PLEASE Give me some help guys. I am very struggle.
Wrong thread.. Needs to be in Q&A
Try a fully stock rom with Odin 1.85
Sent from my GT-I9300 using xda app-developers app
Kingybear said:
Try a fully stock rom with Odin 1.85
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks Mate, but no luck
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
NatTheCat said:
Wrong thread.. Needs to be in Q&A[/QUOT
I put it on Q&A already, but just wanted to have more people can help, so I put it on here. sorry for any disturb.
Click to expand...
Click to collapse
The fact that you want more people helping you doesnt mean that you can do what you want, wrong section.
By the way, it seems that your s3 is bricked pal.
Sent from my GT-I9300 using Tapatalk
anyone can tell me how to delete the thread? Thanks
aguerito said:
The fact that you want more people helping you doesnt mean that you can do what you want, wrong section.
By the way, it seems that your s3 is bricked pal.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
show the poor guy some love dude, your comments are abrasive he only wants help for his expensive phone sheesh
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
I wouldnt panic yet they say its very hard to brick an S3?
check around and see what you can find out
kk12175 said:
Thanks Mate, but no luck
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
jothi2lingam said:
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
i was using Omega since v.9 until v33.2 at the last minute. and I found a video in youtube to resurrect my s3 by flashing Checkrom v4:
http://www.youtube.com/watch?v=ZNaQfdOi56E
tried it as well, but it seems doesn't work as it kept rebooting / hanging at the Galaxy S3 logo. And I tried to flashed some stock rom (combo file) from Samfirmware, no luck neither. Tried to flash some stock rom (3 files + pit) HK base rom. Same happened. Fail after Nand Write Start.:silly:
and now, couldn't get into CWM neither.
jothi2lingam said:
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Been using adblock for a while myself and never had a hiccup .. excellent app..
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
johnkhor123 said:
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I had flashed custom rom before, do you think I can still use the warranty? If yes, definitely going.
kk12175 said:
Dear Friends
I HAVE MESS-UP WITH MY i9300!!!!
The incident is I was using custom rom, and installed some stupid app called "Adblock" or something,
and then, my phone just keep went-off for about 8-10 times a day. So then, I decided to reflash
custom rom by CWM, and after I pressed install in Aroma Installer, it just kick me out all of sudden, and
then, I couldn't get back to CWM anymore, so I decided to flash some stock rom by odin, but what
had happen was it starts until "Nand write start" and stacked for a while, and then just FAIL me.
On the net, I found that Checkrom Resurrection V4 could rescue softbrick i9300, I tried, but
no luck either. Finally, just now, I tried a 3 files stock rom with pit, and it came out as:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
What I have done:
1. reflash custom rom by CWM
2. 3 wipes - (but I am no longer to get back to CWM)
3. flash stock rom - hong kong combo firmware @ Samfirmware - by Odin
4. flash Checkrom Resurrection V4 by Odin
5. flash stock rom - 3 files firmware + pit - by Odin
6. changed usb port
7. changed PC
8. uninstall all applications relative to Kies
have you guys got any idea what can I do? I am thinking to mess-up the phone even badly (till it couldn't switch on), so that I can take it to Samsung Service Center for warranty replacement, but have you got ANY method I can do that to mess it up? Or anything I can over-come from the soft (or hard) brick. PLEASE Give me some help guys. I am very struggle.
Click to expand...
Click to collapse
Try TURN OFF antivirus, update Kies, Try on other OS.
Because I had the same problem with own S3.
Windows 8, AVG IS 2013, Odin 3.07,3.04.
Everytime after few second Odin stop working and show FAIL "Complete(Write) operation failed."
But on Windows 7, updated Kies to 2.5, turned off AVG, Odin 3.07, fresh downloaded rom ELK4, Galaxy S3 slowly but finished NAND write
and now I am happy againg
johnkhor123 said:
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ya i think so,,Same incident for previously after flashed one of the rom from this thread i went to sleep..The phone was reboot itself (stuck in bootloop) till i found at morning, my phone fuc**ing hot stucked in Samsung Galaxy SIII. After tried flashed using odin & using cwm not worked because my phone keep on rebooting. Once send to sammy centre i said that i put in charge, once wakeup in morning my phone keep on rebooting & so hot. So after one week they replace me new board for my s3 even they can see my cwm. I tried to delete cwm but cant. Thank god atlast they replace my s3. so only way is send to samsung centre. I face exactly same issue previously as you facing now
KKTHX said:
Try TURN OFF antivirus, update Kies, Try on other OS.
Because I had the same problem with own S3.
Windows 8, AVG IS 2013, Odin 3.07,3.04.
Everytime after few second Odin stop working and show FAIL "Complete(Write) operation failed."
But on Windows 7, updated Kies to 2.5, turned off AVG, Odin 3.07, fresh downloaded rom ELK4, Galaxy S3 slowly but finished NAND write
and now I am happy againg
Click to expand...
Click to collapse
sounds good. give it a try .. thanks MATE
kk12175 said:
anyone can tell me how to delete the thread? Thanks
Click to expand...
Click to collapse
Thread closed.
** Thank you to JGeigerM, hexitnow, and joderme for the solution.
** Solver was paid.
** I leave a condensed version in case someone is frantically googling like I was.
[Background]
I downloaded VRUAME7 for my Galaxy S4.
I then tried to flash Blue Toggles apk.
I then began getting the message "Unfortunately, System UI has stopped".
I decided to use Odin to attempt to flash MDK firmware, which FAILED as you will see below:
**ODIN LOG**:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.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> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
**PHONE LOG**
START [224, 1448]
SW REV. CHECK FAIL : fused : 3, Binary : 1
**SOLUTION**:
(1) Verizon GS4 I545 VRUAME7 Stock Image = http://invisiblek.org/sch-i545/SCH-I...3crny1_fac.zip
(2) Unzip that file when downloaded
(3) Run Odin 3.07 (latest as of posting) as administrator
(4) Select .MD5 file that you unzipped as a PDA
(5) Hit Start once it loads
Here is the link to the stock ME7 image... http://forum.xda-developers.com/showthread.php?t=2357235
Try this one and see if it works.
You were trying to flash the mdk firmware which you cant flash back to once on me7. the stock me7 file is at this link
http://forum.xda-developers.com/showthread.php?p=43420116
The mods for me7 need to be made for it most of the time I believe framework is quite a bit different from mdk which is why you got yourself a soft brick. Im gonna put this out there just in case yoh were looking into it but youre unable to flash a custom recovery on me7 or else youll get another soft brick of sorts. There are people working on it tho.
Sent from my SCH-I545 using Tapatalk 2
EDIT: Solved
I'm glad I could help. XDA forum stalking has become my new habit so I saw it when you posted :good:
EDIT: Solved
Yeah that was a bad download. Another user posted the same thing. After he redownloaded it he was good to go.
Sent from my SCH-I545 using Tapatalk 2
It lives!
Thank you all so much again.
A mod can switch this to solved.
I'm trying to contact JGeigerM for payment.
Sorry, hexitnow, you were 2 minutes later than his original link.
m0bstr said:
It lives!
Thank you all so much again.
A mod can switch this to solved.
I'm trying to contact JGeigerM for payment.
Sorry, hexitnow, you were 2 minutes later than his original link.
Click to expand...
Click to collapse
I wouldnt of accepted anything for payment so im not worried bout it. You can edit your post and add solved to the title. Glad you got it going though.
Sent from my SCH-I545 using Tapatalk 2
It wasn't much help to send you just a link to an image.
Sent from my SCH-I535 using Tapatalk 4
Hey everyone!! I just need some help with Odin. I have Odin v 3.09 installed. I tried installing a custom ROM on my Galaxy S4 SCH-I545 and screwed it up. I now need to use Odin to flash a stock ROM back on to my phone. I am really confused because Odin keeps saying:
<ID:0/004> Added!!
<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/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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't say try a different port or try another computer because I have done both. Just please help ASAP because I really want my phone back.
:good:Thanks Guys!!!:good:
EDIT:
I fixed this thanks to k1mu. He gave me this. and it worked great. Use the no-wipe ROM.
spence1322 said:
Hey everyone!! I just need some help with Odin. I have Odin v 3.09 installed. I tried installing a custom ROM on my Galaxy S4 SCH-I545 and screwed it up. I now need to use Odin to flash a stock ROM back on to my phone. I am really confused because Odin keeps saying:
<ID:0/004> Added!!
<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/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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't say try a different port or try another computer because I have done both. Just please help ASAP because I really want my phone back.
:good:Thanks Guys!!!:good:
Click to expand...
Click to collapse
Using big fonts doesn't help. :laugh:
You tried to flash ME7. Why? What build were you running prior to your failed flash? What did you try to flash that failed?
Probably CM, AOSP, or some other build that's never going to work..
At this point, I'd suggest installing Samsung Kies and using the emergency firmware recovery.
Then, before flashing ANYTHING ELSE. reading at least the stickies in this and the general forum.
What you did was completely avoidable.
k1mu said:
Using big fonts doesn't help. :laugh:
You tried to flash ME7. Why? What build were you running prior to your failed flash? What did you try to flash that failed?
Probably CM, AOSP, or some other build that's never going to work..
At this point, I'd suggest installing Samsung Kies and using the emergency firmware recovery.
Then, before flashing ANYTHING ELSE. reading at least the stickies in this and the general forum.
What you did was completely avoidable.
Click to expand...
Click to collapse
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
spence1322 said:
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
Click to expand...
Click to collapse
First idea would be stop flashing random builds. You need to find out what build you are on, and flash that through Odin. Once you update to a newer build, you cannot revert back to an older build.
spence1322 said:
Sorry for the big font!!! First post testing out the features.
I don't know why i was trying to flash ME7. I found it on another thread on here and a lot of people said it worked for them, not for me. I was running 4.3. I tried flashing SCH-I545_MDK_562219_Stock_Restore.tar.md5 two other unknown recoveries I found here and there.
I tried installing Kies. I got it installed and everything but my phone will not connect to Kies. I have tried multiple different downloads for drivers and the troubleshooting in Kies. It just won't work.
Any ideas??
Click to expand...
Click to collapse
couldn't help yourself?? This is a $600 phone and you have to be sure what you are doing before you proceed. Not sure how to direct you from here.
decaturbob said:
couldn't help yourself?? This is a $600 phone and you have to be sure what you are doing before you proceed. Not sure how to direct you from here.
Click to expand...
Click to collapse
Apparently, based on another thread, he's running MJ7. Hopefully flashing that will get it working.
k1mu said:
Apparently, based on another thread, he's running MJ7. Hopefully flashing that will get it working.
Click to expand...
Click to collapse
with all the information available in these forums and people still proceed with little knowledge on their phones.....blows my mind away.
decaturbob said:
with all the information available in these forums and people still proceed with little knowledge on their phones.....blows my mind away.
Click to expand...
Click to collapse
Look... I'm sorry I don't know everything like you... I'm 15
spence1322 said:
Look... I'm sorry I don't know everything like you... I'm 15
Click to expand...
Click to collapse
I'm 15 as well, but I also make sure to read up on what I'm doing before I destroy my phone.
spence1322 said:
Look... I'm sorry I don't know everything like you... I'm 15
Click to expand...
Click to collapse
Don't want to lecture but being your age makes it doubly important to research....that's how you get to have knowledge.
Sent from my SCH-I545 using XDA Premium 4 mobile app
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!