Stuck in download mode

[str8shot]

New i337 user here.

Had it rooted yesterday, using the ./pwn method.

I realize now - I was on AMF3.

Once rooted - I was trying to get TWRP installed via goomanager.

Now I'm stuck in download mode. When ever I try to flash via odin to MDL or MDB, I get a FAIL! (Auth) error.

Is there anyway to fix this? Is there an AMF3 tar out there that's flashable via Odin?

Or am I completely screwed?

 

[jd1639]

Sorry to say, you're screwed. There is no mf3 Odin file. And you can't put a custom recovery on mf3. That's what bricked you. You could try jtag. Talk to mobiletechvideos.com.

 

[str8shot]

Fail.

Other alternative is to wait for an Odin flashable file, I assume?

 

[jd1639]

Fail.

Other alternative is to wait for an Odin flashable file, I assume?

Yes, but it could be a real long wait. I'm not even sure jtag would work. From what I've seen on xda it seems the mf3 is really causing problems. If you go that route talk to mobiltech and explain what happened as see if they have a fix before you send your phone in. Warranty might also work.

 

[xBeerdroiDx]

has anyone tried kies emergency recovery yet with this issue? i'm curious.

 

[str8shot]

has anyone tried kies emergency recovery yet with this issue? i'm curious.

I tried that, but Kies doesn't even register the phone as connected.

I'm really bumming.

 

[str8shot]

Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...

 

[jd1639]

Huh

Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...

Man, I'm feeling your pain. I was thinking along the same lines. Some how you borked the recovery and if you could get that back on you might be ok. You might want to check with Aou or AdamOutler. They're wizzes at this type of stuff.

Edit, Just found this. http://forum.xda-developers.com/showthread.php?p=44431964

 

[maxshah912]

New i337 user here.

Had it rooted yesterday, using the ./pwn method.

I realize now - I was on AMF3.

Once rooted - I was trying to get TWRP installed via goomanager.

Now I'm stuck in download mode. When ever I try to flash via odin to MDL or MDB, I get a FAIL! (Auth) error.

Is there anyway to fix this? Is there an AMF3 tar out there that's flashable via Odin?

Or am I completely screwed?

Call Samsung tell them your phone not working it is not turning on and send for repair [ PS free warranty for yr ] best they can do is tell you no after looking phone. Shipping is free as well.
I have bricked my s3 by flashing different Rom and they fixed it for me.
Also bricked my s4 AT&T same way as u did they fixed it for me lol

Most of time they be nice and fix it for you.

 

[Aou]

Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...

Man, I'm feeling your pain. I was thinking along the same lines. Some how you borked the recovery and if you could get that back on you might be ok. You might want to check with Aou or AdamOutler. They're wizzes at this type of stuff.

The closest we got was this:
http://forum.xda-developers.com/showthread.php?t=2374221 (see end of post #6 for tarball)

We managed to build an odin-flashable tarball with the MF3 recovery. If it worked, it would save your device.

Problem is, the only copies of recovery.img that we can get right now are refused by the phone because they are not signed. If we got a signed version, we'd be golden. Unfortunately we probably won't see this until Kies has MF3.

 

[str8shot]

The closest we got was this:
http://forum.xda-developers.com/showthread.php?t=2374221 (see end of post #6 for tarball)

We managed to build an odin-flashable tarball with the MF3 recovery. If it worked, it would save your device.

Problem is, the only copies of recovery.img that we can get right now are refused by the phone because they are not signed. If we got a signed version, we'd be golden. Unfortunately we probably won't see this until Kies has MF3.

It's a miracle!

I read through your thread; and for giggle - instead of letting it fail to boot and fall back to dl mode, I manually entered dl mode, then hit vol down to cancel and reboot.

It booted normally and all appears well...guess I have to delete goo for now. I'm missing CM10.1, though.

Thanks! And PHWEW! Thought I was screwed!

 

[Aou]

It's a miracle!

I read through your thread; and for giggle - instead of letting it fail to boot and fall back to dl mode, I manually entered dl mode, then hit vol down to cancel and reboot.

It booted normally and all appears well...guess I have to delete goo for now. I'm missing CM10.1, though.

Thanks! And PHWEW! Thought I was screwed!

Congrats! Yes, you'll be without custom ROMs until we find a new exploit similar to Loki, or fully unlocked bootloaders.

I'm assuming you don't have a recovery at all now, right? Might want to check that out while you have everyone's attention here.

If it's borked, you might be able to manually use "dd" to flash the stock MF3 recovery back onto your device... You would use something like:

su
dd if=/sdcard/mf3-recovery.bin of=/dev/block/mmcblk0p21

For the love of God, don't get that partition number wrong (p21) - check your spelling before pressing Enter. There is some risk in this method, so check out any available options you might have in goo manager to restore a backup or something first.

 

[str8shot]

Congrats! Yes, you'll be without custom ROMs until we find a new exploit similar to Loki, or fully unlocked bootloaders.

I'm assuming you don't have a recovery at all now, right? Might want to check that out while you have everyone's attention here.

If it's borked, you might be able to manually use "dd" to flash the stock MF3 recovery back onto your device... You would use something like:

su
dd if=/sdcard/mf3-recovery.bin of=/dev/block/mmcblk0p21

For the love of God, don't get that partition number wrong (p21) - check your spelling before pressing Enter. There is some risk in this method, so check out any available options you might have in goo manager to restore a backup or something first.

Using the unsigned recovery from the other post?

 

[Aou]

Using the unsigned recovery from the other post?

As a last resort, yes. It came from @joeybear23 who dumped it using my instructions in post #2 of that same thread, or you could extract it out of the tarball if you wish. The image itself can be downloaded in the first part of post #6. Might need to rename it or otherwise change the filename referenced in the "dd" command.

Again, this is only if your recovery is currently borked and unusable.

 

[NMonster69]

I fixed mine using a dif file.

I found a file called MF3_BTL_FIX.tar.md5. Flashed it in odin and it fixed my bootloader issues. Everything back to normal. Found it used for a dif issue elsewhere on XDA. I thought I was screwed for the foreseeable future.

 

[jpaytoncfd]

It's a miracle!

I read through your thread; and for giggle - instead of letting it fail to boot and fall back to dl mode, I manually entered dl mode, then hit vol down to cancel and reboot.

It booted normally and all appears well...guess I have to delete goo for now. I'm missing CM10.1, though.

Thanks! And PHWEW! Thought I was screwed!

Just wanted to give this a second thumbs up. Seems soooo stupid but it works, lol. Thanks!

 

[ardonie]

lol

after hours of trying every thing else thanx. it worked