Database Users

[Q] SGS4 sick recovery needed

I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys

Correct me if I'm wrong someone buy I'm pretty sure If you're boot loader is locked you are NOT to flash any custom recoveries or kernels. Safestrap is the only recovery you can use. I'm on mf3 myself, you may have to odin back to stock, root, and install safestrap again. Can't flash any kernels on mf3.. it will cause your phone not to boot.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

You are going to have to odin the stock tar files. I assume you are on mf3 firmware. Look for the mf3 tar files, there on one of the threads. Google "mf3 tar xda"

I looked for a link to firmware mf3 to flag in Odin but nothing
Already the bricking the phone deal is taken care of.

I don't know why its so hard for people to find stuff I googled it with results just fine.
http://forum.xda-developers.com/showthread.php?t=2502003
Sent from my SAMSUNG-SGH-I337 using xda premium

jd1639 said:
You are going to have to odin the stock tar files. I assume you are on mf3 firmware. Look for the mf3 tar files, there on one of the threads. Google "mf3 tar xda"
Click to expand...
Click to collapse
So do u have a link AT&T I337 MF3 firmware?

Lewis_Koseck said:
So do u have a link AT&T I337 MF3 firmware?
Click to expand...
Click to collapse
Google "mf3 tar xda"

WOW!

scott14719 said:
WOW!
Click to expand...
Click to collapse
That Google stuff is complicated, lol

Obviously I did and nothing. It's great when people ask for help all we get is snobbed nosed attitudes
And here I Google the brick problem Every one on xda saying only solution is Odin. And real no I was able to pull out of the brick without it so obviously not everyone is as smart as you guys but if it's even possible to keep your attitudes in check would be great!

jd1639 said:
That Google stuff is complicated, lol
Click to expand...
Click to collapse
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.

Lewis_Koseck said:
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Click to expand...
Click to collapse
Glad you got it fixed. But you probably have no clue how you got in the situation you were in nor how you got out of it. I'd suggest you do a lot of reading of the pinned threads in the general forum. Sorry, you'll have to get your own links.

Lewis_Koseck said:
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Click to expand...
Click to collapse
Post #5 in THIS thread GAVE you a link to the MF3 firmware 2 HOURS before you posting again asking for it. How much more help would have liked to receive? I suggest you evaluate your own mental state of being before you respond to others with childish name calling. At the very least, read the thread you are in before making yourself look ignorant. You will definitely not be a loss to the community with an attitude like yours.

scott14719 said:
Post #5 in THIS thread GAVE you a link to the MF3 firmware 2 HOURS before you posting again asking for it. How much more help would have liked to receive? I suggest you evaluate your own mental state of being before you respond to others with childish name calling. At the very least, read the thread you are in before making yourself look ignorant. You will definitely not be a loss to the community with an attitude like yours.
Click to expand...
Click to collapse
I swear I even gave him the link to what he needed all he had to do was read it. Does he need arrows pointing to it or pilot navigation or something? Smh... Calling people names when all we're trying to tell him is look first than read.
Sent from my SAMSUNG-SGH-I337 using xda premium

Lewis_Koseck said:
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Click to expand...
Click to collapse
Lewis_Koseck said:
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Click to expand...
Click to collapse
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.

@JohnMonsour I doubt he will read this he didn't even try to read the link I posted to try to help him. But great guide
Sent from my SAMSUNG-SGH-I337 using xda premium

Yeah. Unfortunately. I should re-post this guide for MF'd people though. What do you think? I think the the OP died..... LOL.
---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------
[email protected] said:
Does he need arrows pointing to it or pilot navigation or something?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This I lol'd at....... HAHAHAHAHA.

[Q] Accidently closed TWRP

Hi guys, I will try and explain this as simple as possible.
I as trying to install cyanogenmod 11 on my phone, and everything seemed to go alright until I made a mistake. I used TWRP to first backup my stock rom on the phone, and then when I was supposed to reboot into the app, I accidently rebooted the phone.
Now the problem is that the phone does not have any OS installed, so what is happening is that it's trying to boot into an OS that's not there, and instead ends up being stuck on the Samsung logo. I can enter Odin mode just fine, but for the love of god I cannot seem to figure how to get back into the TWRP application, or if it is even possible.
I do have the backup of the ROM stored on my SD card, and I've now moved it over to my PC, but it still does not seem to help me in any way. I've trid to launch the Odin3 program on my pc, in an attempt to to try and launch in TWRP through that, but it has all been without any success, so now I come to this board of guinesses, asking for help!
As an added bit of information, this was my first time trying to install a custom rom, so yeah.. Puff..
- The lost Dane.
- Edit -
I tried to "flash" by doing what this link said, in the hopes that my phone would boot into the program, but alas, it only booted back to the logan saying "samsung Galaxy Note 3 SM-N9005" :/
http://forum.xda-developers.com/showthread.php?p=30694404
-- Edit Edit --
To make it super clear ... If I could get back into TWRP, I would be able to run my backup. I know how that app works, I just simply cannot get back into, and I do not know if it is even possible. I've searched and tried various guides to "flash TWRP through Odin" but it has all been without any success... :/

Thaelern said:
Hi guys, I will try and explain this as simple as possible.
I as trying to install cyanogenmod 11 on my phone, and everything seemed to go alright until I made a mistake. I used TWRP to first backup my stock rom on the phone, and then when I was supposed to reboot into the app, I accidently rebooted the phone.
Now the problem is that the phone does not have any OS installed, so what is happening is that it's trying to boot into an OS that's not there, and instead ends up being stuck on the Samsung logo. I can enter Odin mode just fine, but for the love of god I cannot seem to figure how to get back into the TWRP application, or if it is even possible.
I do have the backup of the ROM stored on my SD card, and I've now moved it over to my PC, but it still does not seem to help me in any way. I've trid to launch the Odin3 program on my pc, in an attempt to to try and launch in TWRP through that, but it has all been without any success, so now I come to this board of guinesses, asking for help!
As an added bit of information, this was my first time trying to install a custom rom, so yeah.. Puff..
- The lost Dane.
- Edit -
I tried to "flash" by doing what this link said, in the hopes that my phone would boot into the program, but alas, it only booted back to the logan saying "samsung Galaxy Note 3 SM-N9005" :/
http://forum.xda-developers.com/showthread.php?p=30694404
-- Edit Edit --
To make it super clear ... If I could get back into TWRP, I would be able to run my backup. I know how that app works, I just simply cannot get back into, and I do not know if it is even possible. I've searched and tried various guides to "flash TWRP through Odin" but it has all been without any success... :/
Click to expand...
Click to collapse
Did you hold volume up+home+power button to get into recovery mode?
In case your twrp get corrupted due to flashing failure previously
1. Download twrp from the following. 2.6.3.7 if you were running 4.3 or 2.6.3.8 if you were running 4.4.2(not sure if 2
6.3.8 is 4.3 compatible). For odin flashable use the one with .tar
http://www.techerrata.com/browse/twrp2/hlte
2. Get into download mode(vol down+home+power)
3. Link the downloaded .tar to pda in odin. Odin log should show 'added' once you connect phone to pc
4. Start the process. Once finish phone should boot into recovery automatically but it'll try to boot back into OS. Just hold vol up+home+power button to get back into recovery

Rosli59564 said:
Did you hold volume up+home+power button to get into recovery mode?
Click to expand...
Click to collapse
When I do that, I get an ultra short blue text appearing on the screen, before it goes into downloading mode, with a red text saying "Could not do normal boot." So it basically goes right into odin mode.

Thaelern said:
When I do that, I get an ultra short blue text appearing on the screen, before it goes into downloading mode, with a red text saying "Could not do normal boot." So it basically goes right into odin mode.
Click to expand...
Click to collapse
I edited my post. You need to reflash twrp

You are an absolute god. I wish I could show my appreciation, but I fear words isn't even enough to even begin.. I managed to get into TWRP now, though my backup rom doesn't show up anymore, but I suppose that's because I run a different version of TWRP than I did first? Idk, but really appreciate that you were able to get me back into TWRP.

Thaelern said:
You are an absolute god. I wish I could show my appreciation, but I fear words isn't even enough to even begin.. I managed to get into TWRP now, though my backup rom doesn't show up anymore, but I suppose that's because I run a different version of TWRP than I did first? Idk, but really appreciate that you were able to get me back into TWRP.
Click to expand...
Click to collapse
Yes if you know your previous twrp version than you can restore your old rom backup
---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------
Thaelern said:
You are an absolute god. I wish I could show my appreciation, but I fear words isn't even enough to even begin.. I managed to get into TWRP now, though my backup rom doesn't show up anymore, but I suppose that's because I run a different version of TWRP than I did first? Idk, but really appreciate that you were able to get me back into TWRP.
Click to expand...
Click to collapse
Right you need your previous twrp version to use the backup
Hehe you can actually press the thanks button

Rosli59564 said:
Yes if you know your previous twrp version than you can restore your old rom backup
---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------
Right you need your previous twrp version to use the backup
Hehe you can actually press the thanks button
Click to expand...
Click to collapse
I really do appreciate the help you've given, but I have one final request, and I really do hope it isn't too much to ask. Say I am unable to find the same version of TWRP, I will have to actually flash cyanogenmod onto my device. I don't think it should be too tough now that I've managed to launch into TWRP, because now I should be able to just put the rom on my SD card, and then install the files, no?
if it helps you, my device is SM-N9005, and I had 4.3 when I started this whole thing. Cheers!
- Edit.
I tried to download the Nighty build from CyanogenMod's own homepage, but when I try and install it, it says failed, giving me an erro that says "This package is for "hlexx" devices: This is a." That's all it says ... Hmfh. Sooooooooo... Yes! I'm in recovery mode now, but without any rom. :/

Thaelern said:
I really do appreciate the help you've given, but I have one final request, and I really do hope it isn't too much to ask. Say I am unable to find the same version of TWRP, I will have to actually flash cyanogenmod onto my device. I don't think it should be too tough now that I've managed to launch into TWRP, because now I should be able to just put the rom on my SD card, and then install the files, no?
if it helps you, my device is SM-N9005, and I had 4.3 when I started this whole thing. Cheers!
- Edit.
I tried to download the Nighty build from CyanogenMod's own homepage, but when I try and install it, it says failed, giving me an erro that says "This package is for "hlexx" devices: This is a." That's all it says ... Hmfh. Sooooooooo... Yes! I'm in recovery mode now, but without any rom. :/
Click to expand...
Click to collapse
Yes you can flash any cm based rom.
You can also flash any stock rom such as SweetRom/X-Note/BobCat as most developers still keeping 4.3 rom in their thread.

Thaelern said:
I really do appreciate the help you've given, but I have one final request, and I really do hope it isn't too much to ask. Say I am unable to find the same version of TWRP, I will have to actually flash cyanogenmod onto my device. I don't think it should be too tough now that I've managed to launch into TWRP, because now I should be able to just put the rom on my SD card, and then install the files, no?
if it helps you, my device is SM-N9005, and I had 4.3 when I started this whole thing. Cheers!
- Edit.
I tried to download the Nighty build from CyanogenMod's own homepage, but when I try and install it, it says failed, giving me an erro that says "This package is for "hlexx" devices: This is a." That's all it says ... Hmfh. Sooooooooo... Yes! I'm in recovery mode now, but without any rom. :/
Click to expand...
Click to collapse
Try this link: http://download.cyanogenmod.org/?device=hlte
Sent from my toaster

blackknightavalon said:
Try this link: [
Sent from my toaster
Click to expand...
Click to collapse
Will that work on the international version of the Note 3 ? I'm starting to believe that's the whole culprint of why I can't get it to work. :/

Thaelern said:
Will that work on the international version of the Note 3 ? I'm starting to believe that's the whole culprint of why I can't get it to work. :/
Click to expand...
Click to collapse
Believe so. It's because of updater script i guess as described in the link
http://forum.xda-developers.com/showthread.php?t=2600648&page=2
Try flashing chenglu's 6.0.4.5 recovery.
http://forum.xda-developers.com/showthread.php?t=2454079
Just the same as you did for twrp. I think i read somewhere that changing recovery helped some people.
The worst just download sweetrom/x-note/bobcatrom or any stock 4.3 based rom if you deperately need the phone to boot up

Rosli59564 said:
Believe so. It's because of updater script i guess as described in the link
Try flashing chenglu's 6.0.4.5 recovery.
Just the same as you did for twrp. I think i read somewhere that changing recovery helped some people.
The worst just download sweetrom/x-note/bobcatrom or any stock 4.3 based rom if you deperately need the phone to boot up
Click to expand...
Click to collapse
So after having spent the better half of the night, I actually managed to get my phone to boot into cyanogenmod 11 ! But that joy was shortlived when I came to realize that wi-fi wasn't working, and I couldn't get it to work. I tried to factory reset as I had read would help, but alas it did no good. I figured I should try and run back a stock 4.4.2 rom and just be done with it, but that was when I realized I had lost my root (?!) so that wasn't really a possibility either, next I set out to try and find a way to root my phone now running cyanogenmod 11. I found a file here on XDA called "CF-Auto-Root-hlte-hltexx-smn9005.tar" but whenever I try and flash that onto my phone, my phone just stays stuck saying "trying to enter into recovery mode" and does not really go anywhere from there. I can get back into recovery mode if I flash "n9005-cwm-recovery-6.0.4.5(1116)" onto the phone, like you said, but that still leaves me without root access, which I need to throw a rom onto my device?! Arrrgh, this is getting silly, I just wish I could go back to my backup/ default rom on the device, but I can't.

Thaelern said:
So after having spent the better half of the night, I actually managed to get my phone to boot into cyanogenmod 11 ! But that joy was shortlived when I came to realize that wi-fi wasn't working, and I couldn't get it to work. I tried to factory reset as I had read would help, but alas it did no good. I figured I should try and run back a stock 4.4.2 rom and just be done with it, but that was when I realized I had lost my root (?!) so that wasn't really a possibility either, next I set out to try and find a way to root my phone now running cyanogenmod 11. I found a file here on XDA called "CF-Auto-Root-hlte-hltexx-smn9005.tar" but whenever I try and flash that onto my phone, my phone just stays stuck saying "trying to enter into recovery mode" and does not really go anywhere from there. I can get back into recovery mode if I flash "n9005-cwm-recovery-6.0.4.5(1116)" onto the phone, like you said, but that still leaves me without root access, which I need to throw a rom onto my device?! Arrrgh, this is getting silly, I just wish I could go back to my backup/ default rom on the device, but I can't.
Click to expand...
Click to collapse
About the cf auto root make sure you flash the one for 4.3. I believe you flashed the one for 4.4.2.
Doesn't really matter whether you have root access or not as long as you can boot into custom recovery. Just flash any custom rom. It'll give you root anyway.
Still if you need root just make sure you flash cf auto root then flash twrp or chenglu recovery. Flash the one for 4.3 that's the most important

Rosli59564 said:
About the cf auto root make sure you flash the one for 4.3. I believe you flashed the one for 4.4.2.
Doesn't really matter whether you have root access or not as long as you can boot into custom recovery. Just flash any custom rom. It'll give you root anyway.
Still if you need root just make sure you flash cf auto root then flash twrp or chenglu recovery. Flash the one for 4.3 that's the most important
Click to expand...
Click to collapse
But when I have cyanogenmod 11 installed, is that then not 4.4.2 ? I suppose that's what's giving me trouble... I'll try and see if I can find the cf auto root for 4.3 and return back if I was successful or not. Again, thank you for being so patient..
-Edit
This seems to be the only one I can find; http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
And I've already tried that one 3 times, but every time I flash it, the phone reboots and keeps trying to enter into recovery mode, and is unable to do so before I've flashed n9005-cwm-recovery-6.0.4.5(1116) again
this is what it says;
"recovery booting...
Recovery is not seandroid enforcing
Set warranty bit : Recovery "

Thaelern said:
But when I have cyanogenmod 11 installed, is that then not 4.4.2 ? I suppose that's what's giving me trouble... I'll try and see if I can find the cf auto root for 4.3 and return back if I was successful or not. Again, thank you for being so patient..
-Edit
This seems to be the only one I can find; http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
And I've already tried that one 3 times, but every time I flash it, the phone reboots and keeps trying to enter into recovery mode, and is unable to do so before I've flashed n9005-cwm-recovery-6.0.4.5(1116) again
this is what it says;
"recovery booting...
Recovery is not seandroid enforcing
Set warranty bit : Recovery "
Click to expand...
Click to collapse
You flashed 4.4.2 cm rom but you're on 4.3 booloader. So you need to use cf auto root for 4.3 which is available here
http://forum.xda-developers.com/showthread.php?t=2466423
read third post(download section)
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Rosli59564 said:
You flashed 4.4.2 cm rom but you're on 4.3 booloader. So you need to use cf auto root for 4.3 which is available here
http://forum.xda-developers.com/showthread.php?t=2466423
read third post(download section)
Click to expand...
Click to collapse
Just enter download mode and reflash twtp. I saw there are 4 different versions for 4.3(2.6.3.0/2 6.3.5/2.6.3.6/2.3.6.7). Flash 1 by 1 and see if it can restore your backup

Rosli59564 said:
You flashed 4.4.2 cm rom but you're on 4.3 booloader. So you need to use cf auto root for 4.3 which is available here
http://forum.xda-developers.com/showthread.php?t=2466423
read third post(download section)
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Just enter download mode and reflash twtp. I saw there are 4 different versions for 4.3(2.6.3.0/2 6.3.5/2.6.3.6/2.3.6.7). Flash 1 by 1 and see if it can restore your backup
Click to expand...
Click to collapse
You really are a boss with a heart of gold! I used the file you linked me, ran it, and sure enough it installed and gave me root access. Believe it or not, but I am learning from this! The whole thing about bootloader being different from the rom version was new to me. But I am up and running with root access now, so now I hope it shouldn't be too hard to get a stock rom thrown in. I've kinda given up on my backup. I no longer care for the files I had before, now I just want the phone up and running with wifi.. X_ X
- Edit
Or do you have any clue as to what is causing wifi to not work? I really don't mind the rom at all, I quite like it, but where I live wifi is mandatory as it's a lowered area with mountains around me, meaning LTE really isn't viable while at home.

Thaelern said:
You really are a boss with a heart of gold! I used the file you linked me, ran it, and sure enough it installed and gave me root access. Believe it or not, but I am learning from this! The whole thing about bootloader being different from the rom version was new to me. But I am up and running with root access now, so now I hope it shouldn't be too hard to get a stock rom thrown in. I've kinda given up on my backup. I no longer care for the files I had before, now I just want the phone up and running with wifi.. X_ X
- Edit
Or do you have any clue as to what is causing wifi to not work? I really don't mind the rom at all, I quite like it, but where I live wifi is mandatory as it's a lowered area with mountains around me, meaning LTE really isn't viable while at home.
Click to expand...
Click to collapse
Not sure about the wifi problem but yes you're good to go with a new rom. Make sure to choose only for 4.3 bootloader else you will run into problem later

Rosli59564 said:
Not sure about the wifi problem but yes you're good to go with a new rom. Make sure to choose only for 4.3 bootloader else you will run into problem later
Click to expand...
Click to collapse
Could you be so kind and to link me to a rom that works for 4.3 bootloader? I am so paranoid I'll end up picking something for 4.4.2, like I was about to do now. :S

Thaelern said:
Could you be so kind and to link me to a rom that works for 4.3 bootloader? I am so paranoid I'll end up picking something for 4.4.2, like I was about to do now. :S
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2495688
Post 1 choose V6
Or
http://forum.xda-developers.com/showthread.php?t=2472301
Post 3
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 1 v3.0
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 2 V5
There's a lot more in developement section. Just take a look there. Most developers still providing link for 4.3

Rosli59564 said:
http://forum.xda-developers.com/showthread.php?t=2495688
Post 1 choose V6
Or
http://forum.xda-developers.com/showthread.php?t=2472301
Post 3
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 1 v3.0
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 2 V5
There's a lot more in developement section. Just take a look there. Most developers still providing link for 4.3
Click to expand...
Click to collapse
Alright.. Time to get things done right! So just being sure I do it alright. I pick this one; http://forum.xda-developers.com/show....php?t=2498687
Download the one for 4.3 bootloader, once download I place the zip folder on my SD card
- Then boot into Recovery mode, wipe phone clean, and then install the rom directly from inside of Recovery mode?

Video Guide for Installing and Using Safestrap

There are a lot of questions popping up regarding how to install and use Safestrap on the recently rooted NC2 firmware for the SM-N900A. If you are a visual person like me, videos and pictorials are more helpful than trying to follow written guides. This was done on my AT&T Galaxy Note 3 running Skizzy034's S5 port, but it will also work if you are using plain rooted MI9, MJ5, NB4, MLG, or NC2 and want to flash a custom ROM. Safestrap can be found here.
A few important things note before you try flashing ROMs:
1. Before trying this you need to be rooted (use Kingo for Jellybean or Towelroot for NC2)
2. Safestrap v3.71 is for Jellybean and Jellybean ONLY
3. Safestrap v3.72 is for KitKat and KitKat ONLY
4. If you are running NC2 or MLG with the A3 bootloader you can ONLY flash KitKat ROMs such as FireKat, Dynamic Kat, the S5 port I mentioned earlier, Alliance ROM (KitKat version), or UrDroid. If I missed any please forgive me!
5. If you brick your phone (as mentioned in the video) you will have to use this guide by carl1961 to recover. If I brick my phone again I'll try to make a video guide for that.
Sorry for the somewhat low video quality. I was trying to film with one hand with my ancient Galaxy Nexus. If you have any other questions or comments feel free to post them here or send me a PM :good:
Here is the video:
https://www.youtube.com/watch?v=FMzV8bzEeJU&feature=youtu.be
DISCLAIMER
I am not responsible if you brick your phone. I did not force you to do this. By following this guide you are accepting the risks involved with modifying your expensive phone.
Not sure if I need to give credits since I posted links to other people's work, but I'll do it anyway:
All credit for Safestrap goes to @Hashcode
All credit for Towelroot goes to @geohot
All credit for Firekat goes to @megalomanic14
All credit for Dynamic Kat goes to @bri315317
All credit for the S5 port goes to @Skizzy034
All credit for Alliance ROM goes to @RErick
All credit for UrDroid and the MLG fix goes to @carl1961

Face_Plant said:
There are a lot of questions popping up regarding how to install and use Safestrap on the recently rooted NC2 firmware for the SM-N900A. If you are a visual person like me, videos and pictorials are more helpful than trying to follow written guides. This was done on my AT&T Galaxy Note 3 running Skizzy034's S5 port, but it will also work if you are using plain rooted MI9, MJ5, NB4, MLG, or NC2 and want to flash a custom ROM. Safestrap can be found here.
A few important things note before you try flashing ROMs:
1. Before trying this you need to be rooted (use Kingo for Jellybean or Towelroot for NC2)
2. Safestrap v3.71 is for Jellybean and Jellybean ONLY
3. Safestrap v3.72 is for KitKat and KitKat ONLY
4. If you are running NC2 or MLG with the A3 bootloader you can ONLY flash KitKat ROMs such as FireKat, Dynamic Kat, the S5 port I mentioned earlier, Alliance ROM (KitKat version), or UrDroid. If I missed any please forgive me!
5. If you brick your phone (as mentioned in the video) you will have to use this guide by carl1961 to recover. If I brick my phone again I'll try to make a video guide for that.
Sorry for the somewhat low video quality. I was trying to film with one hand with my ancient Galaxy Nexus. If you have any other questions or comments feel free to post them here or send me a PM :good:
Here is the video:
https://www.youtube.com/watch?v=FMzV8bzEeJU&feature=youtu.be
DISCLAIMER
I am not responsible if you brick your phone. I did not force you to do this. By following this guide you are accepting the risks involved with modifying your expensive phone.
Not sure if I need to give credits since I posted links to other people's work, but I'll do it anyway:
All credit for Safestrap goes to @Hashcode
All credit for Towelroot goes to @geohot
All credit for Firekat goes to @megalomanic14
All credit for Dynamic Kat goes to @bri315317
All credit for the S5 port goes to @Skizzy034
All credit for Alliance ROM goes to @RErick
All credit for UrDroid and the MLG fix goes to @carl1961
Click to expand...
Click to collapse
Woohooo my question got answered right away, and even got it's own thread..!! Thanks brother..!

page acbssd
Face_Plant said:
There are a lot of questions popping up regarding how to install and use Safestrap on the recently rooted NC2 firmware for the SM-N900A. If you are a visual person like me, videos and pictorials are more helpful than trying to follow written guides. This was done on my AT&T Galaxy Note 3 running Skizzy034's S5 port, but it will also work if you are using plain rooted MI9, MJ5, NB4, MLG, or NC2 and want to flash a custom ROM. Safestrap can be found here.
A few important things note before you try flashing ROMs:
1. Before trying this you need to be rooted (use Kingo for Jellybean or Towelroot for NC2)
2. Safestrap v3.71 is for Jellybean and Jellybean ONLY
3. Safestrap v3.72 is for KitKat and KitKat ONLY
4. If you are running NC2 or MLG with the A3 bootloader you can ONLY flash KitKat ROMs such as FireKat, Dynamic Kat, the S5 port I mentioned earlier, Alliance ROM (KitKat version), or UrDroid. If I missed any please forgive me!
5. If you brick your phone (as mentioned in the video) you will have to use this guide by carl1961 to recover. If I brick my phone again I'll try to make a video guide for that.
Sorry for the somewhat low video quality. I was trying to film with one hand with my ancient Galaxy Nexus. If you have any other questions or comments feel free to post them here or send me a PM :good:
Here is the video:
https://www.youtube.com/watch?v=FMzV8bzEeJU&feature=youtu.be
DISCLAIMER
I am not responsible if you brick your phone. I did not force you to do this. By following this guide you are accepting the risks involved with modifying your expensive phone.
Not sure if I need to give credits since I posted links to other people's work, but I'll do it anyway:
All credit for Safestrap goes to @Hashcode
All credit for Towelroot goes to @geohot
All credit for Firekat goes to @megalomanic14
All credit for Dynamic Kat goes to @bri315317
All credit for the S5 port goes to @Skizzy034
All credit for Alliance ROM goes to @RErick
All credit for UrDroid and the MLG fix goes to @carl1961
Click to expand...
Click to collapse
Omg. Safestrap still not work omg kill me plz..

jdmsohc22 said:
Woohooo my question got answered right away, and even got it's own thread..!! Thanks brother..!
Click to expand...
Click to collapse
Glad you liked it :good:
Johnliu12 said:
Omg. Safestrap still not work omg kill me plz..
Click to expand...
Click to collapse
What exactly is the problem? Is Safestrap not installing or you can't boot into Safestrap? Which firmware version are you running? Did you install the correct version of Safestrap for your firmware version? Did Busybox successfully install? Sometimes the Busybox installation will fail and you have to keep trying until it is successful.

face_plant said:
glad you liked it :good:
What exactly is the problem? Is safestrap not installing or you can't boot into safestrap? Which firmware version are you running? Did you install the correct version of safestrap for your firmware version? Did busybox successfully install? Sometimes the busybox installation will fail and you have to keep trying until it is successful.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Johnliu12 said:
View attachment 2809247View attachment 2809248View attachment 2809249
Click to expand...
Click to collapse
Which version of Safestrap are you using? Did you try rebooting after installing Busybox? Maybe you got a bad Safestrap download. Try downloading it again and see if it's any better.

institu aga
Face_Plant said:
Which version of Safestrap are you using? Did you try rebooting after installing Busybox? Maybe you got a bad Safestrap download. Try downloading it again and see if it's any better.
Click to expand...
Click to collapse
Thank you very much..for help me...now is work im so happy ..
I try to busybox installed and reboot installing safestrap again is work.. thank you again u will be my God...

so in order to flash a rom after completing all these steps, we still have to do all those other steps that you listed on that other thread? we can't just wipe/flash like the HTC days..? thanks!

jdmsohc22 said:
so in order to flash a rom after completing all these steps, we still have to do all those other steps that you listed on that other thread? we can't just wipe/flash like the HTC days..? thanks!
Click to expand...
Click to collapse
Which other thread? After installing Busybox and Safestrap you're free to wipe and flash all you want.
Edit- if you're taking about the stuck download mode fix thread created by carl1961, those other steps listed are only for recovering from a soft brick.

Face_Plant said:
Face_Plant ROM Install Procedure
1. Download NC2_Bootloader_N900AUCECMGL_VER_2.zip from the OP (should be ~1.5 gigs)
2. Once the file finishes downloading, right click and select "extract all".
3. Open the extracted folder and click on Odin3 v3.09.
4. Boot into Odin/download mode (volume down/home/power button all at the same time) and plug your phone into your PC (I used the USB 3.0 cable, but any USB cable should work).
5. Load AP_NC2_Bootloader_N900AUCECMLG.tar.md5 into the AP slot in Odin, click start, and wait for it to finish.
6. Odin should say "pass" and your phone will boot up. Skip or complete the set up stuff. It's up to you.
7. Download N900AATTCNC2_KERNEL.tar.md5 Kernel (3.4.0-722276) from the OP and extract the file just like you did before.
8. Boot into Odin/download mode
9. Open Odin and load N900AATTCNC2_KERNEL.tar.md5 into the AP slot and click start.
10. If Odin says "pass", go to settings-> about device-> and scroll all the way down and make sure your phone has the 3.4.0-722276 kernel
11. If it does, you're good to root with Towelroot, install Safestrap, and get back to flashing!
Not sure if it's necessary, but I flashed the NC2 modem too. Do this by:
1. Download it from the OP (I used the first link. It uses Odin).
2. Extract the files like you did earlier.
3. Click on Odin3 v3.09 and load SM-N900A_NC2_Modem.tar.md5 into the CP slot.
4. Boot your phone into Odin/download mode and hook it up to your PC.
5. Click start and wait for Odin to finish.
Click to expand...
Click to collapse
Ok cool, so just to be clear these instructions above are only for bricked devices and not necessary after doing the safestrap thing..?? I'm just wondering because I read somewhere that I need to flash a bootloader " NC2_Bootloader_N900AUCECMGL_VER_2.zip" and I googled it and it came back to that thread with your instructions..?
Thanks man, you're a great help!
EDIT: I downloaded that AllianceROM for KitKat and when it was done downloading it was just a folder, not a zip.. I'm on a MacBook pro so I just right clicked it and selected "compress" to turn the folder in to a zip, but is it safe to flash the zip now or does it have to be made "flashable" somehow..?? Thanks again!

jdmsohc22 said:
Ok cool, so just to be clear these instructions above are only for bricked devices and not necessary after doing the safestrap thing..?? I'm just wondering because I read somewhere that I need to flash a bootloader " NC2_Bootloader_N900AUCECMGL_VER_2.zip" and I googled it and it came back to that thread with your instructions..?
Thanks man, you're a great help!
EDIT: I downloaded that AllianceROM for KitKat and when it was done downloading it was just a folder, not a zip.. I'm on a MacBook pro so I just right clicked it and selected "compress" to turn the folder in to a zip, but is it safe to flash the zip now or does it have to be made "flashable" somehow..?? Thanks again!
Click to expand...
Click to collapse
Correct, those instructions are only for bricked phones. What you saw in the video is all you need to do if your phone is working, rooted, and have Safestrap working.
If it's a zipped file then it should be good to flash. Before you go ahead and flash it I have a few questions: How big is the zipped file? Most ROMs for this phone should be somewhere around 1.5 gigs. Is there anything inside the zipped file when you open it? If the file you downloaded is an empty folder then I wouldn't flash it.
I've never come across a situation like yours and I don't know squat about Macs, so I'm afraid that I can't be of much help. To be safe I recommend redownloading it straight from the phone. It'll take longer, but I think it'll be much less risky than flashing what could be an empty file.

I have yet to get safestrap to work. I'm rooted via towelroot, I installed busy box, rebooted, installed safestrap 3.71 since I'm still on JB, but so just force closes every time. The screen stays black and crashes

wburch84 said:
I have yet to get safestrap to work. I'm rooted via towelroot, I installed busy box, rebooted, installed safestrap 3.71 since I'm still on JB, but so just force closes every time. The screen stays black and crashes
Click to expand...
Click to collapse
Just curious, why did you use Towelroot to root while still on JB? were you originally rooted and just re-rooted with TR? Because I know that there is more than one method to root JB and they all work with no problems and SS works with them as well. Saying that because TR maybe your problem (I could be wrong, though).

K-Alzwayed said:
Just curious, why did you use Towelroot to root while still on JB? were you originally rooted and just re-rooted with TR? Because I know that there is more than one method to root JB and they all work with no problems and SS works with them as well. Saying that because TR maybe your problem (I could be wrong, though).
Click to expand...
Click to collapse
I originally used king root and though that maybe that was the issue so I unrooted and rooted again with towelroot

wburch84 said:
I originally used king root and though that maybe that was the issue so I unrooted and rooted again with towelroot
Click to expand...
Click to collapse
Try unrooting, reroot with Kingo (if you're on NB4 you'll need Kingo v1.1.8), install Safestrap v3.71 WITHOUT Busybox, and give that a shot. I don't think the Jellybean version of Safestrap requires Busybox, so that may be the problem. The Safestrap apk might be corrupted too, so redownload it.

Face_Plant said:
Which version of Jellybean are you on? If you're on NB4 root with Kingo v1.1.8 and install Safestrap v3.71. I don't think the Jellybean version of Safestrap requires Busybox.
Click to expand...
Click to collapse

wburch84 said:
Click to expand...
Click to collapse
I was editing my post when you replied. Checkout what I added. Since you're on MJ5 any version of Kingo will work.

Face_Plant said:
I was editing my post when you replied. Checkout what I added. Since you're on MJ5 any version of Kingo will work.
Click to expand...
Click to collapse
I'll give that a try. Thanks for your help

@Face_Plant all of you stock NC2 users should check out my thread. It has some goodies ya'll might like [emoji6][emoji16]
Apks share

Im a complete noob/moron when it comes to this stuff, the only device ive ever flashed was the Motorola Atrix 4g. I only did that once.
So, once Safestrap is installed and ive made a backup, its a complete backup of the stock rom etc, right? so if i dont like one of the new ones, i just restart in safestrap again and wipe and reinstall the back up?
I would really like to give Firekat a try since heat issues have been my biggest concern with the phone. Im just really afraid of bricking my phone since ive never really tried this stuff before with the exception of the 4g which was pretty simple once i wrapped my head around it. Not to mention, i messed with the 4g after i got my Note 3 and really didnt care if it got messed up at that point.
Also, when installing any of the other Roms, the install process from safestrap just brings up the roms default install procedures and options right? If im off base, sorry.. I really want to try FireKat but im so leery of giving this a shot.

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.

Nice....it helped me :good:
Thanks :highfive:

neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband

nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.

neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.

IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that

Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app

Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD

Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.

neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.

I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?

neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.

not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?

jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.

Start Up Fail while installing rom

Ok guys I just recently rooted my first phone. All was well until I tried to install my first ROM. It seemed to be going fine until I got a Screen that said "start up fail" and in small red text at the top it said "Custom Binary Blocked By Secure Boot (Boot. img)" Here is a picture of the screen: http://imgur.com/a/DQ62P
Here is the link to the ROM: http://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
Any Ideas on what I can do to fix this?

Dizzy.Dylan said:
Ok guys I just recently rooted my first phone. All was well until I tried to install my first ROM. It seemed to be going fine until I got a Screen that said "start up fail" and in small red text at the top it said "Custom Binary Blocked By Secure Boot (Boot. img)" Here is a picture of the screen: http://imgur.com/a/DQ62P
Here is the link to the ROM: http://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
Any Ideas on what I can do to fix this?
Click to expand...
Click to collapse
Anyone got any ideas on what to do?

Dizzy.Dylan said:
Anyone got any ideas on what to do?
Click to expand...
Click to collapse
I had a similar occurrence while using FlashFire when I accidentally hit the EverRoot option. You'll have to put it into download mode and ODIN a stock ROM onto it. Then ROOT and upgrade as usual being careful not to hit the EverRoot. Hope it helps.

otterdad said:
I had a similar occurrence while using FlashFire when I accidentally hit the EverRoot option. You'll have to put it into download mode and ODIN a stock ROM onto it. Then ROOT and upgrade as usual being careful not to hit the EverRoot. Hope it helps.
Click to expand...
Click to collapse
I never hit EverRoot and I've tried it twice now and still havent gotten it to work Could it be something to do with the firmware?

Hey man, sorry to hear about this, I'm not exactly sure your problem, but I guess I would start by re-flashing the ENG Boot for your device (via Odin) - assuming that's the root method you used (you can find it here if you haven't got it elsewhere) Otherwise you could flash your device's stock firmware via Odin and then you could try following this guide here for rooting, and retry everything, which is what I would recommend.
I used that guide for my brother's SM-G935V and it has worked "flawlessly", I haven't tried installing a ROM on it yet but it should work as long as the ROM itself works, - I say "flawlessly" because there are a few issues with rooting this phone, but you can easily work around all of them.
I would recommend explaining and detailing your problem as much as you possibly can, in this post and in future posts, so that you can get as much help as possible.. if you need any clarification on anything, let me know, and be careful, for your first phone experimenting ,there's a lot of sh** that can go wrong! Keep in mind that you can fix most problems by flashing your stock firmware with Odin if all else fails.
Best of luck to you, let me know how it goes.