Database Users

ATT S4 Yellow Triangle Recovery and Rom

Hello,
After successfully rooting my S4 and installing 4.3.3 I wound up screwing things up and now have the yellow triangle of death when I try to get back into recovery or boot the rom.
The only thing I seem to be able to do successfully now is get back to download mode.
Trying to flash a new recovery via odin results in a nand write failure. I've tried philz, clockwork and twrp, all do the same thing.
Since I can't boot the rom there's no way to use an adb based utility like casual, which is what I had used to originally root.
From what I can find it doesn't appear there are any odin flashable versions of the loki utility.
Any help with ideas on what to try next appreciated.
Thanks for any help

tr2ride said:
Hello,
After successfully rooting my S4 and installing 4.3.3 I wound up screwing things up and now have the yellow triangle of death when I try to get back into recovery or boot the rom.
The only thing I seem to be able to do successfully now is get back to download mode.
Trying to flash a new recovery via odin results in a nand write failure. I've tried philz, clockwork and twrp, all do the same thing.
Since I can't boot the rom there's no way to use an adb based utility like casual, which is what I had used to originally root.
From what I can find it doesn't appear there are any odin flashable versions of the loki utility.
Any help with ideas on what to try next appreciated.
Thanks for any help
Click to expand...
Click to collapse
Tried flashing a stock rom with Odin, data factory reset and reroot?

No Command, Error when trying to get into Custom Recovery

Hey all, not sure what's going on but I've flashed both the CWM and the latest TWRP tar files through Odin and upon trying to get into recovery, Vol-Up+Pwr+Home I get the blue recovery booting line which hangs on it's own for about 5 seconds then goes to No Command, a little android with a red exclamation stating error and then it goes to the stock recovery.
This is the CDN SM-N900W8 with the latest MJ4, I have not yet rooted although that was the plan once I get into recovery.
Any help would be appreciated.
Goo.Manager and Rom Manager aren't locating recovery's for me to install via the app method.

opensourcefan said:
Hey all, not sure what's going on but I've flashed both the CWM and the latest TWRP tar files through Odin and upon trying to get into recovery, Vol-Up+Pwr+Home I get the blue recovery booting line which hangs on it's own for about 5 seconds then goes to No Command, a little android with a red exclamation stating error and then it goes to the stock recovery.
This is the CDN SM-N900W8 with the latest MJ4, I have not yet rooted although that was the plan once I get into recovery.
Any help would be appreciated.
Goo.Manager and Rom Manager aren't locating recovery's for me to install via the app method.
Click to expand...
Click to collapse
you have to root 1st

The plan was root via the SU zip from recovery but I guess I just do CF-Auto-Root then from Odin...? I thought I would at least be able to get into recovery rooted or not.

opensourcefan said:
The plan was root via the SU zip from recovery but I guess I just do CF-Auto-Root then from Odin...? I thought I would at least be able to get into recovery rooted or not.
Click to expand...
Click to collapse
yeah i CF-Auto-Root with odin then flashed cwm with odin

Okay doing it in that order worked nicely. I found a tutorial that described the opposite which was bad I guess.

Bootloader/Flash Problem

I have an ATT i337 S4 (mdl baseband) running on T-mobile. Current setup was wicked 7.0 ROM with ATT kernel.
I was trying to change to cyanogenmod ROM and tried using my TWRP 2.5.0.2 to load the rom but it would flash it and gave me an md5 error. Supposedly this is a known issue with TWRP so most people recommend using clockworkmod recovery and I tried to load that using recovery tools. Recovery tools couldn't find the CWM image file but did find the 2.6.3.0 updated TWRP image file so I tried to update TWRP and when I did, I can't boot to recovery anymore and instead get the yellow triangle saying unauthorized software.
At the same time (ugh) I flashed wicked 8 ROM update and think I loki'd it (I am running wicked 8.0 now) but I forgot to run the att kernel afterward. The current kernel is 3.4.5 ... dirty ptmr3 ... N5110 #1. I think this is the standard t-mobile kernel which will obviously not work on my ATT phone.
The problem is, now I can't reboot into recovery mode. When I try, I get the yellow triangle "system software not authorized by ATT...". I don't know if the problem is with the bad kernel or with the updated 2.6.3 TWRP. The only way I can get around the bootloader problem is the hold down the down vol and home button, then the power button and that gets me into a "Warning a custom OS can cause critical problems ..." page. From there if I continue, I get the yellow triangle. If I hit the volume down button to cancel, it boots normally but not into the bootloader and I have partial functionality of my phone.
Where do I go from here? Odin to stock? Replace the bootloader somehow? Anything else?
I did do a nandroid of my system before all of this but for some reason I can't access my SD card. I can hit mount but nothing shows up on file manager. Will that backup replace the bootloader with the known good one? I could copy the backup to the phone memory and do it from there using titanium backup I think.
Thanks,

odin back to stock and then wipe/clear then retry should fix this problem

lilg754367 said:
odin back to stock and then wipe/clear then retry should fix this problem
Click to expand...
Click to collapse
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.

colorchange said:
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
Click to expand...
Click to collapse
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.

colorchange said:
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
Click to expand...
Click to collapse
I'm guessing I might be able to modify the open boot script and change to the old version but I don't know how to do this.

i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain

lilg754367 said:
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
Click to expand...
Click to collapse
Thanks lil, i know the kernel I want and have it downloaded. Right now I am downloading the tar file to get me back to stock. I was hoping to do something easier but crud...

yea no problem just hit the thanks button for me good luck

I can't get Odin to talk to my device. When it is not in download mode, Odin sees it but hangs and can't communicate. When I connect it in debug mode (very hard to get into download mode), Odin can't see it.
Help!

[Q] ***HELP i337 MK2 WON'T BOOT***

Hello all!
First off I would just like to say thank you, thank you, thank you. I have been a long time lurker on these forums (since the evo) and have gotten a lot of useful information from here. Now to my issue. I have had no phone for two weeks now, and have been doing search after search. I upgraded my phone to 4.3 (it was mk2) and rooted it via motochopper. So my dumbass tried to flash a custom rom with kn0x0ut and it failed. The phone rebooted and now will boot up to the samsung custom screen. You can hear the att boot up sound but no image. I can get into odin mode and stock recovery. When I am in odin it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMC BURST MODE enabled
I have tried sideloading the stock MJ9 and MK2 files to no avail. I really hope somebody can help me, I don't know how much longer i can go without a phone. Thanks guys and Merry Christmas!!!

yea sounds like bricked you cant flash roms on 4.3 yet take it to best buy that has a samsung center and just tell them samsung sent you here because my phone all of a sudden was acting up and they will flash it back to factory for you thats what i had to do

gtj0 said:
OK, If you're stuck with an incomplete flash, here are some steps you can try to get to MJ9...
These instructions assume you started with MJ6.
First, make sure you can boot into recovery. If not, download and apply the MJ6 recovery.
recovery-mj6.tar.md5
It should apply without error. If not, report the failure.
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z
mf3-emergency-part-2.tar.md5.7z
If you don't already have it, download the mf3-mj9 update file...
update-mf3-mj9.zip
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Reboot the phone back into Download mode and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
The phone should now reboot to recovery by itself and apply a small update. If it fails, stop and report.
The phone should now reboot to a black screen with the pulsing notification LED.
Reboot into recovery mode and flash update-mf3-mj9.zip. I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MJ9.
Click to expand...
Click to collapse
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925

dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
I was on MK2 using the 3.7 beta of SS when I couldn't get it to boot anymore. Tried the modified method outlined above, everything worked except after step 7, it never rebooted to recovery on it's own and installed a small update. Decided to try Kies, says it can do emergency firmware recovery but it hasn't worked yet. Any help would be appreciated as I'm not sure I can get the handset replaced since I got it at Walmart.

It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
sl1200md3 said:
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
Click to expand...
Click to collapse

dolph8886 said:
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
Click to expand...
Click to collapse
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!

FINALLY
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
FINALLY LONG SEARCH OVER FOR THIS FIX JUST ONE QUESTION WILL THE RECOVERY FAIL AS WELL?

tonyc0642 said:
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
Click to expand...
Click to collapse
hi i have the exact same problem....i dont know how to start adb on windows 7...arrgh...

Thanks to the everyone for this
It saved my ass..I put the zips on a sd and installed.Back on mk2 and rooted.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

I tried the above mentioned but after I flash the second file and reboot, it goes into kies , no recovery mode. Odin is still available. Also thanks for all the quick responses fellas yall are the best.
***UPDATE*** flashed the recovery but the sideload failed. Tried to turn it on and the Samsung lolgo came on, then went black. After a a few minutes the phone pops up on the computer and I can access the internal phone memory and the sd card.

I am really not sure, I believe that it will work if you do this process again.
No Idea if this makes any difference but, pay close attention to the process at least until the sideloading of the update.
Do not let the device attempt to boot with this firmware mismatch as this may cause issues. (This is the only conclusion I can come to as this process does work)
If the device automatically reboots then press and hold volume up to enter recovery or volume down to enter download mode.
If manual reboot or powering on then press and hold volume up or down respectively then press power until the device starts and release power button to avoid a reset.

SOLVED!!!
Thank you so much @dolph8886!!!1 You are the BEST!!! :good: :victory: :highfive:

This helped me, fixed my softbrick, hope this helps! Remember to thank the author if it works
http://forum.xda-developers.com/showthread.php?t=2621279

ok here it goes i tried to flash twrp using goo but now i have no stock recovery can someone help me please im on mk2 running 4.3 and rooted

Install Recovery and CM on Locked I9500

Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL

The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.

Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL

Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)

No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.

Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!

Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....

Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.

Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,