Video Guide for Installing and Using Safestrap - AT&T Galaxy Note 3 General

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.

Related

[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] Failed root with odin, cannot detect with Kies 3

I recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
"Secure check failed: cache"
Click to expand...
Click to collapse
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
CoryG89 said:
I recently got a Galaxy Note 3 from Verizon. I wanted to root the device, .........
......Any help will be very much appreciated.
Click to expand...
Click to collapse
Click the link in my sig and d/l the MJE tar, flash it in ODIN (instructions also provided)
Then, you can follow the root, safestrap and cust rom links...
All links, step by steps, everything you need to get you up and running are in the link in my sig
Start fresh with the OEM MJE tar, then go from there... Hit me up in that thread for additional help!
az_biker said:
Click the link in my sig and d/l the MJE tar, flash it in ODIN (instructions also provided)
Then, you can follow the root, safestrap and cust rom links...
Click to expand...
Click to collapse
Thank you very much! I wish I would have found your guide first. I flashed the MJE firmware, was able to successfully root using Kingo (after a few attempts). I also installed safestrap and the open source superuser app.
Now I just have to figure out what roms I want, looks like I can take advantage of the multiple rom slots and try a few before installing one into the stock rom slot.
Again, many thanks!
Odin to MJE Question
Hi, my phone is fully stock with MJE on it. To root my phone, would I need to install the MJE tar file and also use King or just the MJE file? So far, I have had no luck using Kingo to root my phone.
Thanks
tss01 said:
Hi, my phone is fully stock with MJE on it. To root my phone, would I need to install the MJE tar file and also use King or just the MJE file? So far, I have had no luck using Kingo to root my phone.
Thanks
Click to expand...
Click to collapse
Just Kingo should do it for you. I did this last week stock on mje. Make sure you have usb debugging enabled or it won't work. I also used Kingo 1.1.6 instead of 1.1.7 and I had no problem at all woth knox or anything. It worked like a charm.
Misterxtc said:
Just Kingo should do it for you. I did this last week stock on mje. Make sure you have usb debugging enabled or it won't work. I also used Kingo 1.1.6 instead of 1.1.7 and I had no problem at all woth knox or anything. It worked like a charm.
Click to expand...
Click to collapse
Why 1.1.6 instead of .7?
Notorious 3
---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------
tss01 said:
Hi, my phone is fully stock with MJE on it. To root my phone, would I need to install the MJE tar file and also use King or just the MJE file? So far, I have had no luck using Kingo to root my phone.
Thanks
Click to expand...
Click to collapse
Follow the 'Root with Kingo' instructions in link (see my sig)... no worries, you'll be rooted snd running in no time.
Notorious 3
az_biker said:
Why 1.1.6 instead of .7?
Notorious 3
Click to expand...
Click to collapse
I used 1.1.6 because I wasn't sure if their new version was going to automatically add a custom recovery and trip Knox. I was reading the comments on their facebook page (Kingoapp) and saw one that said it will trip knox but a few days later read that it was a option to install a custom recovery. Instead of taking a chance I downloaded the older one and used that. Also in the 1.1.7 comments there is a link to official Samsung drivers if you want to be sure to have the latest ones. There are links for all their versions on the fb page if anyone wants to try that route.
Rooting w/Kingo
Finally was able to get root! What I did was uninstall the Samsung drivers and re-install them. Thank goodness it's finished. I also just installed HyperDrive and Beans. It's kinda nice having a choice each time I turn the phone on.
Thanks for your help.
tss01 said:
Finally was able to get root! What I did was uninstall the Samsung drivers and re-install them. Thank goodness it's finished. I also just installed HyperDrive and Beans. It's kinda nice having a choice each time I turn the phone on.
Thanks for your help.
Click to expand...
Click to collapse
Way to go! Glad you worked through it...
Notorious 3

[HELP] Custom Recovery Flashing Failed + Few Other Questions [Noob-User]

Dear XDA Developer Community,
So before I get to the main problem I'd like to let you know that I've been reading a lot of Articles/Threads on Rooting, Flashing Custom Recovery and Custom ROM. Also this is my very first Android phone so please do excuse me, I'm a complete noob at Android, FOR NOW!
My Android Phone Detail ( In case it helps anyone out):
Model Number: SM-N9005 - International Qualcomm Version.
Android Version: 4.4.2 - It originally came with 4.3 Jelly Bean, however I updated it and now regret this decision. However I'm well aware that a downgrade is not possible.
Kernel Version: 3.4.0 - 636608. [email protected]#1
AP: N9005XXUENB7
CP: N9005XXUENB1
CSC: N90050XAENB1
{
"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"
}
Need Help With:
Do I have to be rooted in order to flash custom recovery? I've tried to search for an answer but didn't find anything specific. I do know that I need root access in order to use TWRP Manager. However what about if I wanted to flash TWRP recovery via Odin?
So here's the trouble. I do not have root access nor custom ROM. I tried to flash TWRP using this tutorial, http://true-android.blogspot.co.uk/2014/03/twrp-2700-touch-recovery-for-samsung_8952.html. Go down to the header that says "How To Install TWRP 2.7.0.2 Touch Recovery on Samsung Galaxy Note 3 SM-N9005 Via Odin".
Using that method I tried to flash TRWP. I started Odin, added the img.tar to AP and started the flashing sequence. Everything went well and the box went green meaning it was applied. Getting excited I enter recovery mode only to be disappointed. The recovery was still an stock recovery (or whatever you call it). However it was the first time I went into recovery and was paranoid. When I select "reboot system now" it says "error". Does that mean I messed something up? The images below show what I mean.
I boot into recovery mode:
However it says "No command" with exclamation mark! Is that a bad thing?:
When I select "reboot system now" it shows me this, however it still reboots:
So does this mean something is wrong with the recovery or is it fine? Because I'm completely scared right now and don't want to ruin my brand new Note 3.
Additional Q:
Q1) I think my boot-loader is locked. Since I read Chainfire say that the KK version has locked boot-loaders now. Meaning I cannot flash anything. Is that why the TWRP flash failed? Not really sure. Also you guys know my phone details, could anyone lead my to a thread or anything so I could unlock the boot-loader. I've also read somewhere on XDA that the KitKat bootloader has "install-recovery". Is this true? And is there a way around this currently? Since I really wanted to install TWRP recovery badly.
Q2) Do I need to have ROOT access in order to flash custom recovery and custom ROM? Or could I do it without ROOT access since I've heard some custom ROM's come pre-rooted. I'm thinking to flash BobCat ROM.
Q3) If you look at my device details what method should I use to ROOT my device? "Root de la Vega" seems a bit complicated for me. Since I've only used CMD but don't know about Terminal (though I've heard of it many times). I could use "CF-Auto-Root by Chainfire", however is this safe to use? I do know if I use Chainfire's method my knox counter will trip.
Lastly thanks a lot for the help. I know I'm complete beginner at this and may annoy some users with my questions, so sorry about that. But I had to, because I'm very cautious. I don't go ahead with anything until I know the details and reading a lot on the topic.​
I was also on NB7 a few weeks ago, turn the device off, do the button combo for download mode, and flash this with odin - http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
then wait for it to reboot the phone after flashing, and try to go to recovery it should be fine now.
and to root the device, copy this onto the phone http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash that in TWRP and this will add supersu to the system partition of the stock rom. no need for cf-auto-root after this.
I hope this helps!
EDIT:
The first picture shows that knox is 0x0, after flashing twrp like you just did that will be 0x1 now, but this recovery i posted should be fine
also what version of odin are you using? i prefer 1.85 and have never had problems with it.
if you have kies installed or running on your pc kill the processes before starting odin.
celderic said:
I was also on NB7 a few weeks ago, turn the device off, do the button combo for download mode, and flash this with odin - http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
then wait for it to reboot the phone after flashing, and try to go to recovery it should be fine now.
and to root the device, copy this onto the phone http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash that in TWRP and this will add supersu to the system partition of the stock rom. no need for cf-auto-root after this.
I hope this helps!
EDIT:
The first picture shows that knox is 0x0, after flashing twrp like you just did that will be 0x1 now, but this recovery i posted should be fine
also what version of odin are you using? i prefer 1.85 and have never had problems with it.
if you have kies installed or running on your pc kill the processes before starting odin.
Click to expand...
Click to collapse
Hi, firstly could you please not quote the while OP because its massive and when you quote it, it ruins the thread. If you could edit that out it would be great, thanks.
Secondly, thanks a lot for the reply. I will try this method soon.
You see I tried to flash TWRP but it didn't work. But now my Current Binary & System Status is "Custom". So I'm shocked to see that, lol. But I'll try your method when I get time .
Also it says "Qualcomm Secureboot: Enable". And I've heard that I cannot flash anything if the bootloader is locked.
jaydeeph said:
Hi, firstly could you please not quote the while OP because its massive and when you quote it, it ruins the thread. If you could edit that out it would be great, thanks.
Secondly, thanks a lot for the reply. I will try this method soon.
You see I tried to flash TWRP but it didn't work. But now my Current Binary & System Status is "Custom". So I'm shocked to see that, lol. But I'll try your method when I get time .
Also it says "Qualcomm Secureboot: Enable". And I've heard that I cannot flash anything if the bootloader is locked.
Click to expand...
Click to collapse
mine also the same Qualcomm Secureboot: Enable , but still can flash recovery. no problem flashing other rom and rooting.
fadhil3536 said:
mine also the same Qualcomm Secureboot: Enable , but still can flash recovery. no problem flashing other rom and rooting.
Click to expand...
Click to collapse
Okay thanks for letting me know. Now I'll try the methods , wish me luck. Hehe.
If you want root flash cf-autoroot from original developement thread. Takes around 10 secs...
Also when flashing a recovery, untick reboot.
Its better to flash, wait for success then boot into recovery as KK has a little script that reverts back to Samsung recovery on 1st boot...
f you boot to recovery after a successful flash, when you then select reboot in the custom recovery it will ask if you wish to disable this little bugger... No more problems with stock recovery re-asserting itself over what you want then...
celderic said:
I was also on NB7 a few weeks ago, turn the device off, do the button combo for download mode, and flash this with odin - http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
then wait for it to reboot the phone after flashing, and try to go to recovery it should be fine now.
and to root the device, copy this onto the phone http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash that in TWRP and this will add supersu to the system partition of the stock rom. no need for cf-auto-root after this.
I hope this helps!
EDIT:
The first picture shows that knox is 0x0, after flashing twrp like you just did that will be 0x1 now, but this recovery i posted should be fine
also what version of odin are you using? i prefer 1.85 and have never had problems with it.
if you have kies installed or running on your pc kill the processes before starting odin.
Click to expand...
Click to collapse
fadhil3536 said:
mine also the same Qualcomm Secureboot: Enable , but still can flash recovery. no problem flashing other rom and rooting.
Click to expand...
Click to collapse
ultramag69 said:
If you want root flash cf-autoroot from original developement thread. Takes around 10 secs...
Also when flashing a recovery, untick reboot.
Its better to flash, wait for success then boot into recovery as KK has a little script that reverts back to Samsung recovery on 1st boot...
f you boot to recovery after a successful flash, when you then select reboot in the custom recovery it will ask if you wish to disable this little bugger... No more problems with stock recovery re-asserting itself over what you want then...
Click to expand...
Click to collapse
@celderic &@fadhil3536 thanks for those tips guys but it didn't work, however you're not wrong. Its the script in KitKat as ultramag mentioned. Really appreciate the help guys :good:.
Just as I suspected, what @ultramag said, seems to be the problem here. I did read that somewhere but no one mentioned a way around it.
Thanks a lot, I will try this and let you know of the outcome. In the meanwhile could you help me out here since you're a senior member.
Q1) Does unlocked or locked bootloader matter when ROOTING/Flashing Custom Recovery/Flashing ROM?
I forgot the other questions and some are already answered by me reading the forum threads. If I do remember any, is it okay if I PM you?
Thanks a lot, once again.
jaydeeph said:
@celderic &@fadhil3536 thanks for those tips guys but it didn't work, however you're not wrong. Its the script in KitKat as ultramag mentioned. Really appreciate the help guys :good:.
Just as I suspected, what @ultramag said, seems to be the problem here. I did read that somewhere but no one mentioned a way around it.
Thanks a lot, I will try this and let you know of the outcome. In the meanwhile could you help me out here since you're a senior member.
Q1) Does unlocked or locked bootloader matter when ROOTING/Flashing Custom Recovery/Flashing ROM?
I forgot the other questions and some are already answered by me reading the forum threads. If I do remember any, is it okay if I PM you?
Thanks a lot, once again.
Click to expand...
Click to collapse
You untick reboot in Odin. This will leave your phone in download mode after the flash. When it says "success" you then turn off phone and boot to recovery.
Depends what you mean wigh locked or unlocked bootloaders.
If youre talking about the n9005 bootloader that wont let you downgrade, I have that. Wont matter. If you mean like the US carriers that lock & do bad stuff you might need to check out that particular forum.
Im a shift worker so getting back can be spotty but I have no problem with you pming me.
ultramag69 said:
You untick reboot in Odin. This will leave your phone in download mode after the flash. When it says "success" you then turn off phone and boot to recovery.
Depends what you mean wigh locked or unlocked bootloaders.
If youre talking about the n9005 bootloader that wont let you downgrade, I have that. Wont matter. If you mean like the US carriers that lock & do bad stuff you might need to check out that particular forum.
Im a shift worker so getting back can be spotty but I have no problem with you pming me.
Click to expand...
Click to collapse
Woop, I did it last night bro & then went to sleep straight away. But yeah I did exactly what you told me in the first post you made and it worked like a charm! Once flashed I shut it down and boot it up into recovery mode and TWRP was there . It didn't ask me to disable the KitKat script thingy but I think it automatically did that because I booted into recovery 3 more times just to triple check it, I'm very cautious.
And yes I have the SM-N9005 International Version, since I'm in the right forum . Ohh okay I guess I'll just have to wait for someone to figure out how to downgrade . But will it be okay if I flash a Custom ROM without ROOT? Or would I need to ROOT then flash Custom ROM? Or is it the opposite way around? Unless the Custom ROM comes with ROOT then I know I can just flash the ROM.
Thanks bro, I'll PM you if anything is urgent; and take all the time in the world dude, I know people always get busy .
jaydeeph said:
Woop, I did it last night bro & then went to sleep straight away. But yeah I did exactly what you told me in the first post you made and it worked like a charm! Once flashed I shut it down and boot it up into recovery mode and TWRP was there . It didn't ask me to disable the KitKat script thingy but I think it automatically did that because I booted into recovery 3 more times just to triple check it, I'm very cautious.
And yes I have the SM-N9005 International Version, since I'm in the right forum . Ohh okay I guess I'll just have to wait for someone to figure out how to downgrade . But will it be okay if I flash a Custom ROM without ROOT? Or would I need to ROOT then flash Custom ROM? Or is it the opposite way around? Unless the Custom ROM comes with ROOT then I know I can just flash the ROM.
Thanks bro, I'll PM you if anything is urgent; and take all the time in the world dude, I know people always get busy .
Click to expand...
Click to collapse
I tend to root with new recovery, cuts down on problems later.... Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?
I use cf-autoroot, about 10 secs to flash and that includes opening odin, selecting file, putting phone in download mode and hitting start.... Heck, in the time it took me to type this I could've rooted 2 phones....:silly:
ultramag69 said:
I tend to root with new recovery, cuts down on problems later.... Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?
I use cf-autoroot, about 10 secs to flash and that includes opening odin, selecting file, putting phone in download mode and hitting start.... Heck, in the time it took me to type this I could've rooted 2 phones....:silly:
Click to expand...
Click to collapse
I did not get anything you said here: "Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?"
Haha, But I think I understand after reading 10 times xD. I don't have ROOT nor any Custom ROM. But wanted to know do I need to have ROOT in order to flash Custom ROM?
Also in the recovery mode, TWRP asks me to install SuperSU or something like that. Should I allow it? Would it be safe?
jaydeeph said:
I did not get anything you said here: "Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?"
Haha, But I think I understand after reading 10 times xD. I don't have ROOT nor any Custom ROM. But wanted to know do I need to have ROOT in order to flash Custom ROM?
Also in the recovery mode, TWRP asks me to install SuperSU or something like that. Should I allow it? Would it be safe?
Click to expand...
Click to collapse
Sorry long day with little sleep. If TWRP is asking to install Super SU then it will root for you, let it...
ultramag69 said:
Sorry long day with little sleep. If TWRP is asking to install Super SU then it will root for you, let it...
Click to expand...
Click to collapse
Okay thanks bro. And hey, don't need to say sorry . Make sure you rest :good:.
jaydeeph said:
Okay thanks bro. And hey, don't need to say sorry . Make sure you rest :good:.
Click to expand...
Click to collapse
Mate, I didn't even get any of the Easter holidays off and am working ANZAC day... Good pay, lousy hours and no social life....:silly:
ultramag69 said:
Mate, I didn't even get any of the Easter holidays off and am working ANZAC day... Good pay, lousy hours and no social life....:silly:
Click to expand...
Click to collapse
Wow, that sucks. I'm sure you have rights for Easter Holidays though, and bank holidays?

Root/TWRP/SD Fix/Init d/FlashPlayer/ADBlocking/debloating the SM-T900 / T900UEUAND4

Update 10/30/2014
There's no need to go back to the "B3" version any longer. The T900UEUANI1 is available on SamMobile, to be flashed w. Odin.
The cf-auto-root listed as "B3" on chainfire's site will work.
Note, I have not created any of this, please thank the original developers in their posts. This is simply a compilation of available info needed to have the most complete and working SM-T900, Samsung Galaxy Tab Pro 12.2.
The sole purpose is to make you save time. However, I'm not saying this will work, and it might even brick your device, but that risk is yours to take. However, it worked for me, so why shouldn't it... Trust the steps, there's a reason for this madness. Believe me when I say it; I've learned the hard way, and it has not been a pleasant journey.
If your SD cards looses necessary rw privileges it seems like not even a backup will correct them, even after wiping the SD cards and formatting data.
If you haven't yet upgraded from B3 to D4, I recommend you to do this first! There are major improvements between the two versions.
1. Rooting:
First flash the P900XXUANB3-RecoveryImg (forgetting this will create a softbrick, and you will have to start over, also use the Odin 3.07, supplied, I have not tested with the later 3.09)
then flash CF-Auto-Root-v2wifi-v2wifixx-smt900
for detailed method and files see: http://androidcentral.us/2014/05/root-galaxy-tab-pro-12-2-sm-t900/
I forgot, it's important to use original cables directly connected to the PC, a docking station connection, or an EOM cable might be a reason for flash failure.
2. install TWRP:
Flash openrecovery-twrp-2.7.1.0-v1awifi
link: http://forum.xda-developers.com/showthread.php?t=2679825
3. disable Knox:
Open SuperSU and answer yes to disabling KNOX
4. fix SD-card issue in KitKat 4.4:
Download and run JRummy's "SD KitKat Fixer" from market. I had no luck with any other comfortable fixing apps.
5. important!:
reboot into recovery and wipe both External and Internal SD, as well as Formatting Data. Don't forget to backup all files you want to keep onto your PC! for later re-installation. I know this must feel hard, but I sincerely advice you you follow this step. Most apps are not KitKat ready, as of now, and won't allow you to download or access the data if you haven't prepared your SD's in advance.
6. init d support:
Download and install Stericson's BusyBox from market
Download and install Uni-init v1.0
link: http://forum.xda-developers.com/showthread.php?t=1933849
7. Flash Player support:
Download and install fixed AdobeFlashPlayer 11.1
link: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-play-flash-video-android-4-t2548001
If you're using Dolphin Browser, also install the Dolphin JetPack, and modify Settings/Web Content/Flash Player/ to Always On.
8. ADBlocking:
Dowload and flash LATEST_MoaAB_ADBlocking_Super
link: http://forum.xda-developers.com/showthread.php?t=1916098
9. De-bloating:
for de-bloating at a maximum you can disable numerous of the Samsung apps, by pushing the three dots, upper right corner, while in the apps-screen mode.
Also, don't forget to un-check the de-bloated apps from auto-update in Play Store, as well as in the Samsung update if you signed up for this service.
10. (Re)-nstall your apps
You're done, and it's time to restore or download all the apps you need and it will work in KitKat 4.4
None of the modified stock ROM's currently available seem to mount correctly. If something goes wrong, you will most likely loose your SD card privileges. The original T900UEUAND4 stock ROM can be found here: http://www.sammobile.com/firmwares/3/?download=29102. Just unzip and flash with Odin, then start again with step 1.
Also, due to lack of time, I will not be able to monitor this post. I hope you will help one another out with clarifications, or anything I might have missed.
Best of luck,
Delete
Very nicely laid out. I've already done all this, but it's great to see a guide for new comers that may not know what to do. Thank you.
Thank you for the guide and gathering everything together. I just wanted to throw this out there, I followed the directions exactly....and I could not get mine to root. It would continually soft brick and a screen full of odd colors would come up every time. I read on the CF Auto Root thread that others had the same issue. One determined individual said he did it 10 times and it finally worked. Soooo....I continued to do it. And it finally worked, trying nothing different each time.
I tried 2 different computers, a win7 and win8, installed Kies to make sure drivers were there. Used official and another cable. I tried everything I could think of. In the end I would say as long as you're following the directions just keep trying.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
That's a link to the P900XXUANB3-RecoveryImg that my friend and I both used before getting root. Thanks again for the guide arcadia2uk!
So I was able to root and install TWRP but after an app caused some issues I went to wipe cache and brick. Flashed stock and had to do factory reset. However, I learned that attempting to restore a backup or wipe cache or do factory reset via twrp causes brick. Have to use Odin to flash back to factory. I also had to use the German region and lost my symbols on keyboard.
................edit..............
I updated kies and reinstalled all the drivers and flashed the cellular south firmware...All is well and current. Rooted, twrp, having fun.
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
{
"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"
}
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
deleted
robert1968 said:
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
Click to expand...
Click to collapse
The fix is actually put the m
Sent from my HTC One_M8 using Tapatalk
I don't know if it will help anyone else, but I just flashed TWRP 2.8 on my Galaxy Tab Pro 12.2 wifi with "D4" firmware using odin and it worked and I was able to make successfully a backup. Below is a link to the recovery I flashed. Of course your mileage may vary so do it at your own risk.
http://teamw.in/project/twrp2/244
The easiest way to debloat it is probably via titanium backup's batch mode actually.
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
saruba said:
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
arcadia2uk said:
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
Click to expand...
Click to collapse
Yey! U R the man! Thanks so much it works flawlessly!
I think I have 2 different recovery files and they both doesn't work I don't know why I got them from twrp site... Anyways just to let you know I've done every thing with Odin 3.09 so yeah I'm confirming that it works fine.
Sent from my HTC One using Xparent BlueTapatalk 2

[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.

Categories

Resources