Database Users

Stuck in download mode

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?

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.

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

str8shot said:
Fail.
Other alternative is to wait for an Odin flashable file, I assume?
Click to expand...
Click to collapse
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.

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

xBeerdroiDx said:
has anyone tried kies emergency recovery yet with this issue? i'm curious.
Click to expand...
Click to collapse
I tried that, but Kies doesn't even register the phone as connected.
I'm really bumming.

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

Huh
str8shot said:
Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...
Click to expand...
Click to collapse
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

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?
Click to expand...
Click to collapse
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.

str8shot said:
Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...
Click to expand...
Click to collapse
jd1639 said:
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.
Click to expand...
Click to collapse
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.

Aou said:
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.
Click to expand...
Click to collapse
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!

str8shot said:
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!
Click to expand...
Click to collapse
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:
Code:
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.

Aou said:
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:
Code:
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.
Click to expand...
Click to collapse
Using the unsigned recovery from the other post?

str8shot said:
Using the unsigned recovery from the other post?
Click to expand...
Click to collapse
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.

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.

str8shot said:
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!
Click to expand...
Click to collapse
Just wanted to give this a second thumbs up. Seems soooo stupid but it works, lol. Thanks!

lol
after hours of trying every thing else thanx. it worked

[Solved]Need help after formatting internal storage! Soft Brick

I truly need the community's help on this one. Trying to fix a rom that I was using, I decided to wipe everything to reflash it. However, some how I read the thread wrong. Using TWRP, I formatted the "internal storage" thinking that was going to fix my Rom problems.
Now, I can't boot into the Rom or any rom, unless I wipe everything and restore one of my back ups. I restored a back up and it booted, but my data is jacked and phone service is not operable. I thought maybe a reboot will fix it, and now my phone is stuck at "Samsung Galaxy S 4". It doesn't move from there.
What should I do? How do I get it it continue the boot into the rom after a regular reboot? How do I get my radio back?
It's funny to me because I usually never get this careless with my phone. So I can laugh about it but damn I have to figure this one out!
Please help!!!!!!!!!!!!!!!!!

I am by know means an expert but I think you may have to start here with the firmware files then try and flash your backup http://forum.xda-developers.com/showthread.php?t=2338919
Sent from my SPH-L720 using Tapatalk 4

Thanks Chief, let me try that!

Thanks Chief. Unfortunately, that didn't work. I used Odin to flash the Firmware files and let it reboot. I'm still stuck at the Samsung Gal...boot screen. Let me try manually going into recovery and restoring.
Any other ideas? Anyone?

Kenjari said:
Thanks Chief. Unfortunately, that didn't work. I used Odin to flash the Firmware files and let it reboot. I'm still stuck at the Samsung Gal...boot screen. Let me try manually going into recovery and restoring.
Any other ideas? Anyone?
Click to expand...
Click to collapse
Have you tried flashing the complete odin ROM? You can find the all in one somewhere on the dev thread, it has rom, kernel, firmware and the rom all in one as it came from samsung. That should take care of your problem. It will wipe everything, or I think there was also a thread somewhere with odin flashables that didn't wipe data or internal sd but I can't seem to find it right now.

ifly4vamerica said:
Have you tried flashing the complete odin ROM? You can find the all in one somewhere on the dev thread, it has rom, kernel, firmware and the rom all in one as it came from samsung. That should take care of your problem. It will wipe everything, or I think there was also a thread somewhere with odin flashables that didn't wipe data or internal sd but I can't seem to find it right now.
Click to expand...
Click to collapse
Exactly. I'm on the target. I'm currently waiting for this tar that will unroot the phone. It is MDL but I will update and reroot. I hope this does the ticket. I'm going to use Odin to flash it or unroot.

Well strike two. That didn't work either. I downloaded a unrooted MDL tar and connected to Odin. When through the entire process and it rebooted. It still is stuck at "Samsung Galaxy S4".
I read on the Nexus 7 that I might have to reflash a system.img and boot.img? Someone else had a similar experience on the N7 and had to download it via flashdrive and then install via recovery. I'm not saying that's the case but I wonder if I need to reflash a boot.img or something.
Please help. Not sure where to go at this point. Unrooting didn't help.

Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's

Progress made.
leaderbuilder said:
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Click to expand...
Click to collapse
leader, chief, ifly4,...I'm making progress.
leader, actually I flashed a previous version, the MDL via Odin. At first it didn't boot as stated in my previous post. I decided to wipe and factory reset. """"Bingo"""" it booted. Now I'm on MDL and unrooted. However, I transferred my phone over to a previous device so I can't update profile and prl. I'm going to activate the phone and see if it works. For some reason I can't can't seem to get a radio signal on it. It shows the be O with the slash in the middle. This is what it looked like before I deactivated it and lost everything before.
I post back with results. Not quite solved yet.
Thanks leader and everyone else.

Sound like your on the wrong firmware/baseband. what does your modem/baseband say?

Yeeessssss
leaderbuilder said:
Sound like your on the wrong firmware/baseband. what does your modem/baseband say?
Click to expand...
Click to collapse
It says L720VPUAMDL. I actually got it going. I had to change it from WCDMA to CDMA and reset. Now I'm unrooted. and going. However, leader, is there away to update the modem/baseband before I root? Or should I root then flash the MF9 Modem?

if you got MDL to activate you can jst take the OTA update to MF9. It will update it all.
Then use CF-Autoroot to gain root. After that same - install goomanager from Playstore and use it to install TWRP.

leaderbuilder said:
if you got MDL to activate you can jst take the OTA update to MF9. It will update it all.
Then use CF-Autoroot to gain root. After that same - install goomanager from Playstore and use it to install TWRP.
Click to expand...
Click to collapse
Awesome. Hey thanks again leader for helping me out. I'm usually never careless with these things. I use SACS rom but decided to try Miui. From some reason every time I flash Miui, I get the "Roaming Indicator Off" thing along with two signals. Reading the thread it suggest to format the internal. Why oh Why did I try that step. The rest is history....
Thanks again. Learned a lot with this process.

Glad you got it working.
There is a 'thanks' button too.

leaderbuilder said:
Glad you got it working.
There is a 'thanks' button too.
Click to expand...
Click to collapse
No doubt. I got to remember that!
Sent from my SPH-L720 using Tapatalk 4

Glad to hear you got it going.
Sent from my SPH-L720 using Tapatalk 4

leaderbuilder said:
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Click to expand...
Click to collapse
Thank you!

[RESOLVED]Recovery help

RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse

As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium

jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.

So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium

when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck

Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?

xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?

Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.

jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!

Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.

jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:

Good deal
Sent from my GT-I9505 using xda premium

Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:

[Q] Need stock Settings.apk

I accidentally overwritten the SecSettings.apk- so now every time I try to open the settings app it crashes..
Does anyone have a copy of the settings apk?
Any info is much appreciated!

Boot329 said:
I accidentally overwritten the SecSettings.apk- so now every time I try to open the settings app it crashes..
Does anyone have a copy of the settings apk?
Any info is much appreciated!
Click to expand...
Click to collapse
What firmware are you running? Stock odexed?
Sent from my SM-N9005

celderic said:
What firmware are you running? Stock odexed?
Sent from my SM-N9005
Click to expand...
Click to collapse
I am running stock and its rooted.
I have no clue on how to check the firmware without the settings application...feels sort of hopeless haha.
Do you think if I flash a new rom everything will work?
I don't have a recovery installed and everytime I try installing one I get the "seandroid enforcing" bit with it boot looping.

Boot329 said:
I am running stock and its rooted.
I have no clue on how to check the firmware without the settings application...feels sort of hopeless haha.
Do you think if I flash a new rom everything will work?
I don't have a recovery installed and everytime I try installing one I get the "seandroid enforcing" bit with it boot looping.
Click to expand...
Click to collapse
You can dirty flash the rom you are on without wiping and all should be restored, just reflash the custom recovery and reroot afterwards.

gee2012 said:
You can dirty flash the rom you are on without wiping and all should be restored, just reflash the recovery and reroot afterwards.
Click to expand...
Click to collapse
I would if I could! For some reason everytime I try flashing a recovery through Rom Manager or GooManager or others has trouble booting into the recovery

Boot329 said:
I would if I could! For some reason everytime I try flashing a recovery through Rom Manager or GooManager or others has trouble booting into the recovery
Click to expand...
Click to collapse
Uninstall rom manager ad never use it again mate, it used to be bad but lately its awfull. Just flash the CWM .tar file with Odin and you`re set. Link CWM recovery by Chenglu http://forum.xda-developers.com/showthread.php?t=2454079. Pick the right .tar file and its done in a jiffy.

gee2012 said:
Uninstall rom manager ad never use it again mate, it used to be bad but lately its awfull. Just flash the CWM .tar file with Odin and you`re set. Link CWM recovery by Chenglu http://forum.xda-developers.com/showthread.php?t=2454079. Pick the right .tar file and its done in a jiffy.
Click to expand...
Click to collapse
Yeah I just realized its pretty awful. I never personally used Odin before- do you know a step by step post that could get me familiar with flashing the tar file with Odin?
Thank you for you information thus far!

Boot329 said:
Yeah I just realized its pretty awful. I never personally used Odin before- do you know a step by step post that could get me familiar with flashing the tar file with Odin?
Thank you for you information thus far!
Click to expand...
Click to collapse
Here is a YouTube tut. http://www.google.nl/url?sa=t&rct=j...HIzgrj-ZklmZ5SiAoPD1u4w&bvm=bv.65058239,d.ZWU and here a written one http://forums.androidcentral.com/sp...08-guide-how-flash-tar-files-odin-3-07-a.html.

For some reason Odin isn't recognizing my phone. I think I installed the necessary drivers so it should recognize it

Boot329 said:
For some reason Odin isn't recognizing my phone. I think I installed the necessary drivers so it should recognize it
Click to expand...
Click to collapse
I tried a different usb and that seemed to do the trick.
Hopefully I can fix this:laugh:
Thanks!!

[SOLVED] bricked my phone using twrp app...

tried to install twrp from app.. got the "software not authorized..." message.. tried to boot from download mode as others have suggested but still recieve "software not authorized..." message..
phone was loki`ed from begining and never took at&t updates. in odin 3.09 phone shows as a com..
is there anything i can do to bring this phone back to life??

If the bootloader isn't locked, flash a stock rom from sammobile.com.

audit13 said:
If the bootloader isn't locked, flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
thanks for your response... holding the up-volume and power only results with the same "not authorized" screen.. also adb does not list it as a device but odin does add it..

Download mode is power and volume down.

audit13 said:
Download mode is power and volume down.
Click to expand...
Click to collapse
sorry confused it with recovery.. the file from sammobile will leave 100% stock?? also whch of the 2 files mdl is the newest of the two
will i need to start over like in http://forum.xda-developers.com/showthread.php?t=2297900 ??

Just flash the stock rom in Odin and perform a factory wipe before booting the stock rom for the first time.

audit13 said:
Just flash the stock rom in Odin and perform a factory wipe before booting the stock rom for the first time.
Click to expand...
Click to collapse
well that worked brilliantly. what should i use to get twrp and root back?

You can use Odin to flash twrp and root with an unlocked bootloader.
Twrp: https://dl.twrp.me/jflteatt/
Flash SuperSU from twrp: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

dook13 said:
well that worked brilliantly. what should i use to get twrp and root back?
Click to expand...
Click to collapse
Towel root works with the MDL bootloader for rooting. Can't tell you how to get TWRP, I use CWM on my at&t S4.

StoneyJSG said:
Towel root works with the MDL bootloader for rooting. Can't tell you how to get TWRP, I use CWM on my at&t S4.
Click to expand...
Click to collapse
i just used the CASUAL app i linked earlier.. it worked to get root and installed twrp..
now i'm looking for a decent rom to install.. all the ones i used to use aren't supported any longer..

I hear Thor ROM and Golden eye ROM are nice and fast TW roms. For non touch wiz there is probably an CM or AOSP rom out there somewhere.