Database Users

How to Unbrick SGS4

I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!

Did you try and reflash recovery ? Does the phone boot up once you restore via Odin ?

Have you tried flashing twrp via Odin?

I have not tried flashing TWRP with Odin... is there a Odin version of TWRP?
It did not boot after flashing stock. I'd like to Odin TWRP if it's available.
I found an Odin TWRP.tar for SGS3, but nothing for S4, yet. Need a little more help.

Did you try rooting and flashing twrp via goomanager? I had something similar happen to me on my skyrocket and that's how I fixed it.

Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium

TheAxman said:
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This version of CWM claims to work with Aroma on the S4...
http://forum.xda-developers.com/showthread.php?t=2322682

scott14719 said:
This version of CWM claims to work with Aroma on the S4...
well lets take a look see...shall we. thanks
Click to expand...
Click to collapse

came across this thread: http://forum.xda-developers.com/showthread.php?t=2281287
it converts an img to an odin-flashable tar.
i went ahead and converted the latest twrp img for the at&t S4 and have attached it. i have not tested it as i am not near my device at the moment. if you decide to try it, unzip the tar.md5 and flash at your own risk as i have not tested this method by @cabloomi.

False aroma works fine with twrp on a gs4.
Sent from my SGH-I337 using Tapatalk 4 Beta

This happened to me. Use odin to put TWRP back on. You'll be fine.
Sent from my SGH-I337 using Tapatalk 2

Yeah I had this a couple different times trying to get rid of the custom/lock icon boot up. Flash fresh stock rom, root it and install recovery with "Root and Recovery for ATT-TMO GS4-CASUAL-R527b" --> http://forum.xda-developers.com/showthread.php?t=2297900 then flash the recovery you want etc, and restore Nandroid of backed up rom. Worked for me!

Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you

JJ5150 said:
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Click to expand...
Click to collapse
I had a similar issue. When you hold the key combination to boot into recovery, do it for more than one cycle. Sometime for some reason it doesn't take the first time so keep holding the buttons. After getting into android recovery, clear cache and reset the phone.

JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
Click to expand...
Click to collapse
When I had the problem is sounds like your having I Odined the Stock image back to the phone and then cleared the dalvik and cache with the stock recovery menu, then I was able to boot, I then rooted and used the debloater program found here on the forums and then just downloaded goomanager and installed TWRP, the one it pushes is LOKIed for you.
This is also the only .img file I can find for the our version of TWRP. IIRC you can use Odin to flash it
EDIT: Like trublu said, you may have to do it several times (clearing the caches in the stock recovery after ODIN)

JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing.
Click to expand...
Click to collapse
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
JJ5150 said:
I have yet to find a Odin version of TWRP that's loki'd for the S4.
Click to expand...
Click to collapse
i believe that all s4 recoveries are "loki'd", if you will.

xBeerdroiDx said:
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
i believe that all s4 recoveries are "loki'd", if you will.
Click to expand...
Click to collapse
The Tmo and Sprint variants do not require Loki'd recoveries, as their bootloaders are not locked.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands

JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
They do great work..used them 2 years ago. With a mytouch..ouch..
Sent from my SAMSUNG-SGH-I337 using xda premium

JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
It's called Jtag repair. And the guys you mentioned have saved many a ass with it. I've seen several good results. Unless something else is found, it is the only way I know of to fix a truly bricked phone. Some people (those who flash a lot and Dev a lot) have their own Jtag boxes.
BTW, which tool / method did you use to convert the .img to a TAR? I've seen a couple of methods and a tool or two but I was wondering if you used something I don't know about? TIA.

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

[HELP] Unable to Reset to Stock

I updated CM10.2 this morning to the latest nightly and since have not been able to access the recovery or boot to android. I have tried flashing a new recovery and stock image using Odin3 v1.85 but have not had any results. Any recommendations as to what I can do to fix this?

ferrerj said:
I updated CM10.2 this morning to the latest nightly and since have not been able to access the recovery or boot to android. I have tried flashing a new recovery and stock image using Odin3 v1.85 but have not had any results. Any recommendations as to what I can do to fix this?
Click to expand...
Click to collapse
First of all we need more information than this. For example, what files you downloaded and trying to use in odin and such and pics of odin error would mostly help us out more. Since you basically saying you cant boot to recovery nor you can odin back to stock. We get stumped and theres no way to help and just randomly telling you things to do. So the more info you can provide the better and faster solution we can provide you. Thanks
Sent from my SPH-L720 using xda app-developers app

ROMANTiC KiD said:
First of all we need more information than this. For example, what files you downloaded and trying to use in odin and such and pics of odin error would mostly help us out more. Since you basically saying you cant boot to recovery nor you can odin back to stock. We get stumped and theres no way to help and just randomly telling you things to do. So the more info you can provide the better and faster solution we can provide you. Thanks
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I am actually not getting any errors from Odin. Its just the fact that my phone will boot loop continuously. I've tried letting it sit for ~20 min but it just says Samsung. I have tried booting to the recovery but the phone will then just reboot and try loading the system which does not load past the Samsung boot animation. I have been trying to flash the following stock tar file:
L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5
as found in this thread:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
I have also tried flashing the TWRP version 2.6.1.0 and 2.6.0.0 tar files using Odin also without any luck.
Does this help?

ferrerj said:
I am actually not getting any errors from Odin. Its just the fact that my phone will boot loop continuously. I've tried letting it sit for ~20 min but it just says Samsung. I have tried booting to the recovery but the phone will then just reboot and try loading the system which does not load past the Samsung boot animation. I have been trying to flash the following stock tar file:
L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5
as found in this thread:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
I have also tried flashing the TWRP version 2.6.1.0 and 2.6.0.0 tar files using Odin also without any luck.
Does this help?
Click to expand...
Click to collapse
Yes it does. Now what happens when you odin mdc file?
Sent from my SPH-L720 using xda app-developers app

ROMANTiC KiD said:
Yes it does. Now what happens when you odin mdc file?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
That did the trick. Thanks.

[Solved] Phone Borked: no system on MK2

Was testing kn0x0ut on our device when I ended up flashing an empty system image. I was on MK2 and attempted to use the MJ6-MJ9 method of flashing just enough files to pass the OTA checks. They didn't flash, and now it says my PIT is broken. I have recovery, and the data partition is in place as on a normal boot it loads to black screen with a blue LED. I can use adb, but there is no root so I can't restore my system. Any suggestions? I'm busy today so I won't be able to reply much, but I can gladly give more information.
EDIT: The system apparently isn't empty. The partition got flashed at some point and appears to have MF3 files.
However, there is still no root and it boots up to nothing but a black screen with blue LED still. I can't get the small update from cache that the MJ6-MJ9 thread mentions. Also, attempting a recovery boot results in the Secure Fail: Kernel screen. Recovery is fixed with the MJ6 recovery file.
FIXED: I was able to get it working following the instructions again. Not sure what the exact issue was with the first time i tried, but flashing the MJ6 recovery makes recovery boot again. I had to flash the two emergency tars, flash the recovery tar again, and then boot into recovery. It then applied the update from cache and on next reboot i went back in and used the sideload.

Have you tried ADB sideloading the update through the recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Supreme Dynamite said:
Have you tried ADB sideloading the update through the recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It doesn't go through since it fails the file check.

Possible help
Hey there, I Gorked my i337 at&t version on Thanksgiving day! I was able to go to this thread and just used Odin to flash the two .tar files and then was able to sideload the mk2 update. Boom phone was back to 4.3
http://forum.xda-developers.com/showthread.php?t=2526964&page=19

joshzdad2013 said:
Hey there, I Gorked my i337 at&t version on Thanksgiving day! I was able to go to this thread and just used Odin to flash the two .tar files and then was able to sideload the mk2 update. Boom phone was back to 4.3
http://forum.xda-developers.com/showthread.php?t=2526964&page=19
Click to expand...
Click to collapse
That's what i've been trying to no avail. The first small update from cache never happened and now it's broken even more.
EDIT: Recovery is booting after flashing the MJ6 recovery, surprisingly. Will attempt instructions one more time and report back.

I beleive i just said screw it since I knew I was boned! I then just flashed recovery-mj6.tar.md5 not even sure if it worked. Then flashed the mf3-emergency-part-1.tar.md5 then the mf3-emergency-part-2.tar.md5 and finally I beleive I tried the side load of my mk2 full update file and it worked.

joshzdad2013 said:
I beleive i just said screw it since I knew I was boned! I then just flashed recovery-mj6.tar.md5 not even sure if it worked. Then flashed the mf3-emergency-part-1.tar.md5 then the mf3-emergency-part-2.tar.md5 and finally I beleive I tried the side load of my mk2 full update file and it worked.
Click to expand...
Click to collapse
Good job man you had me on the seat of my pants reading this.
ROOTED ATT MK2 using Tapatalk

Sprint s4 sph-l720 help!!!!

Ok so I was running CM 11 while i was on MK2 firmware....i flashed a wrong file now i am stuck, I can get into download mode.
My device is Sprint Galaxy S4 running the MK2 firmware, but i have no idea where to go because it will not boot up anymore and only goes into download mode, any ideas on how to fix?
Thanks

i flashed a wrong file now i am stuck
Click to expand...
Click to collapse
Boy that could be bad...
BUT if you get to Download mode you may be able to grab the full MK2 Odin-able .tar you should be Okay.
Please note that the sph-L720 is NOT the L720T. If you have that version and you flash this .tar you'll be hosed.

leaderbuilder said:
Boy that could be bad...
BUT if you get to Download mode you may be able to grab the full MK2 Odin-able .tar you should be Okay.
Please note that the sph-L720 is NOT the L720T. If you have that version and you flash this .tar you'll be hosed.
Click to expand...
Click to collapse
Ok thanks, i will try this and let you know later after its all downloaded and what happens!

RogSeve said:
Ok thanks, i will try this and let you know later after its all downloaded and what happens!
Click to expand...
Click to collapse
Make sure to Run Odin 'as administrator'.
From the zip just extract the .tar.md5 and place that into the PDA slot. Odin 3.09 seems to be working the best for most on this device.

leaderbuilder said:
Make sure to Run Odin 'as administrator'.
From the zip just extract the .tar.md5 and place that into the PDA slot. Odin 3.09 seems to be working the best for most on this device.
Click to expand...
Click to collapse
Yup just downloaded that odin actually, but i have to wait about an hour for that mk2 file to download. And thanks i know I've actually done this before but on mf9 so it was a little easier. Will this bring me back to stock?
Thanks

RogSeve said:
Yup just downloaded that odin actually, but i have to wait about an hour for that mk2 file to download. And thanks i know I've actually done this before but on mf9 so it was a little easier. Will this bring me back to stock?
Thanks
Click to expand...
Click to collapse
You'll be stock everything - baseband(modem), kernel, recovery and ROM.
You will have the knox bootloader, so when you flash a custom recovery you'll 'trip' that. But not really a big deal. You can remove the 'Knox software(s) if you want - there are some removal scripts here in the forums. Only thing is you can't Odin back before MJA/MK2.
To root you can use CF-Autoroot or Saferoot, then use Goomanager or find a recovery zip here and install custom recovery of your choice.

leaderbuilder said:
You'll be stock everything - baseband(modem), kernel, recovery and ROM.
You will have the knox bootloader, so when you flash a custom recovery you'll 'trip' that. But not really a big deal. You can remove the 'Knox software(s) if you want - there are some removal scripts here in the forums. Only thing is you can't Odin back before MJA/MK2.
To root you can use CF-Autoroot or Saferoot, then use Goomanager or find a recovery zip here and install custom recovery of your choice.
Click to expand...
Click to collapse
Ill try that later if it works, i might just stay on stock mk2 don't wanna mess anything else up....lol

RogSeve said:
Ill try that later if it works, i might just stay on stock mk2 don't wanna mess anything else up....lol
Click to expand...
Click to collapse
Ok so now when i try to open it up in odin it says hash value is invalid....any ideas on what to do for that?

leaderbuilder said:
You'll be stock everything - baseband(modem), kernel, recovery and ROM.
You will have the knox bootloader, so when you flash a custom recovery you'll 'trip' that. But not really a big deal. You can remove the 'Knox software(s) if you want - there are some removal scripts here in the forums. Only thing is you can't Odin back before MJA/MK2.
To root you can use CF-Autoroot or Saferoot, then use Goomanager or find a recovery zip here and install custom recovery of your choice.
Click to expand...
Click to collapse
Ok when i try to open the mk2 file it keeps saying the md5 hash is invalid. Ive tried 3 different odins to open it and i get the same result..

You don't open the .tar.md5 file.
You place this file - L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 in the PDA slot.

RogSeve said:
Ok so I was running CM 11 while i was on MK2 firmware....i flashed a wrong file now i am stuck, I can get into download mode.
My device is Sprint Galaxy S4 running the MK2 firmware, but i have no idea where to go because it will not boot up anymore and only goes into download mode, any ideas on how to fix?
Thanks
Click to expand...
Click to collapse
have you tried heimdall? its unbricked me a few times, and its way easier to use too. i think you can use ob both windows and mac, i used on mac. if you are familiar with how to use a command line tool or terminal, this is the way to go. just my humble opinion.