[Q] SGS4 sick recovery needed - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

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.

Related

[Q] Clockworkmod Recovery on AT&T Galaxy S4

First, what I have is the Galaxy S4 from AT&T. It was running Android 4.2.2 but I installed the OTA 4.3 (MK2) update and rooted it. For some reason I can't get the CWM recovery to start. It always goes to the stock recovery. I have tried all the combinations and timings with the three buttons, reflashed CWM with ROM Manager, and tried with GOO Manager. Also, nothing with ODIN wants to work. I've seen countless YouTube vids of Odin working with 4.3 on at&t but it won't complete with mine. Am I missing something? I've been at this for hours. Any help would be great.
http://forum.xda-developers.com/showthread.php?p=48700200
http://forum.xda-developers.com/showthread.php?p=48625977
jd1639 said:
http://forum.xda-developers.com/showthread.php?p=48700200
http://forum.xda-developers.com/showthread.php?p=48625977
Click to expand...
Click to collapse
Yea I've read that thread before. I looked into safestrap and it doesn't work either.
striker24 said:
Yea I've read that thread before. I looked into safestrap and it doesn't work either.
Click to expand...
Click to collapse
Have you tried this http://forum.xda-developers.com/showthread.php?p=48557730
jd1639 said:
Have you tried this http://forum.xda-developers.com/showthread.php?p=48557730
Click to expand...
Click to collapse
Interesting. Although it does require 4.2.2 to work. I am running 4.3 and Odin doesn't like doing anything with my GS4 for some reason. It seems like they are getting closer but it might be I still just have to wait awhile.
HAHAHA. Read more bro? What how did you just acquire a MF3 still? Sounds like you know a little about what you are doing. But the boot-loader is locked down tight with sha-1 256 bit encryption..... Oh, Oh, Did you get a Red one, I really want one of those. Please read about q-fuse software flips.... With every bootloader update. Congrats have fun. Keep trying to flash twrp or cwm you won't even be able to boot into stock recovery. Sounds like you know what you are doing with Odin and all that.... Good Luck.
---------- Post added at 05:15 PM ---------- Previous post was at 04:52 PM ----------
Here is a tut I wrote some time back:
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.
Scratch that.... I'm sorry meant to post in another thread. What is above is all you lost out on homeboi!
---------- Post added at 05:42 PM ---------- Previous post was at 05:15 PM ----------
http://forum.xda-developers.com/showthread.php?p=48675052 Hashs' former post from bottom. Try that. Let us know.

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

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.

[Q] any rom for gty5363

There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
bwizz60 said:
There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
Click to expand...
Click to collapse
As far as I'm aware the 5363 is the o2 variant of the 5360
You might be able to just unlock the phone if not already unlocked (use galaxy toolbox) & flash 5360 firmware and use 5360 roms
Anything you do you do at your own risk - neither myself or xda are responsible for damage caused
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
bwizz60 said:
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
Click to expand...
Click to collapse
Why would you install cwm from rom manager? It's not supported - please do some searching and some reading else you will damage your device
There are two ways to get cwm on galaxy y
1- Flash temporary cwm zip in stock recovery - see http://d-h.st/u2m
2- Flash a kernel with cwm built in
If neither work on your variant you will need to flash 5360 firmware via odin at your own risk
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Hi.
Here is the CWM link: http://forum.xda-developers.com/showthread.php?t=2649475
Please do some digging first before asking.
Also, ROM Manager is not supported on our phones, so do not use it.
bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Don't know what you are clicking on as it's a zip file
Make sure you are clicking on the right download button & not an ad - Install ad blocking software on pc or an app on phone if required
I never post exe files - all my files on dev host are Flashable zips/tars unless otherwise stated
See below Screenshot - Just press the download button as shown in Screenshot
{
"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"
}
Also you should take note of what you are reading, where you are reading it & what device it relates to - rom manager has never been a compatible way of flashing cwm on a galaxy y
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
bwizz60 said:
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
Click to expand...
Click to collapse
It would only say 5360 if you flashed 5360 firmware via odin
Iv kept telling you if you want to use 5360 kernels you will probably have to flash 5360 firmware
Feel free to do what you want at your own risk
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
bwizz60 said:
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
Click to expand...
Click to collapse
With respect Iv told you both ways to get into cwm
With the temp zip I provided by Flashing in stock rom or by Flashing a kernel with cwm built in
You have chosen to ignore all what I'm telling you & trying to do things in unconventional ways - Therefore I can no longer offer you support
Just flash stock rom via odin
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
bwizz60 said:
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
I said to use galaxy toolbox to unlock your phone - ie remove network sim lock if your phone is locked to a specific network
At no point did I say use it to flash cwm
If you can't get into recovery you need to flash stock rom via odin
I do have alot of patience but I find it annoying when people don't read things properly especially when the answers have already been written for them
I do appreciate your help. I am now following the odin info "supplied by yourself on the site"
Ta
bwizz60 said:
I am now following the odin info "supplied by yourself on the site"
Ta
Click to expand...
Click to collapse
That sounds sarcastic...
FYI, this Odin info can be found in his signature. It is also a sticky in the Android dev section.
Search, search, search.
bwizz60 said:
I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
u wot m8
If you don't know what you're reading when it's filled with seemingly bizarre terminology (we've been at that stage one time or another), you do three things:
1) Read on and/or use Google.
Usually definitions will pop out after a while. If I'm not mistaken there are a few threads outlining terminology definitions and usage.
2) Follow everything that they say. And when I say follow, I mean follow 100%, by the book. Reread the instructions over and over to make sure you are actually doing it right.
3) PM another more well-informed member, and don't be afraid to ask.
As for patience, well...
He has dealt with countless people that were in about the same situation as you: thinking that they knew what they were doing and eventually getting into deep s**t with no way out. He has always tried helped them out. Problem is, some of them simply don't want to listen, even if he was correct (which he most likely was). Even then, he tries his best.
Trust me, he knows what he's doing.
Take a deep breath, reread EVERYTHING on this thread, and restart from square one: stock ROM.
If you're too lazy to find (I hope you're not) here is the link for Odin:
http://forum.xda-developers.com/showthread.php?t=2568853
Risky, but everything here is a risk, isn't it? I rarely hear of 5363 users getting stuck here, so this should be fine.
Good luck.
Why would I be sarcastic? there is volumes of stuff on the site all done by this guy.! I show appeciation of this . I can assure you I do spend hours trying to follow information. Some of the links don't work ,sometimes my Firefox security stops progress . very frustrating at times;.
Thanks Mr Smith, now unbricked. I could not find odin 3.184 "spent over an hour trying" 1.85 worked ok . Phone now wakes up as 5360! If the rom is less bloated than the 02 one .I might leave well alone! Stress level falling!
What he meant was Odin3 v1.84.
But, its nice to see things sorted out with your partner's phone.
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
bwizz60 said:
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
Click to expand...
Click to collapse
Root phone
Use Link2sd (playstore) to uninstall system apps
Use the temp cwm I posted a few pages back - place on root (not in any folder) of sd card & flash in stock recovery to get to cwm
Or use a custom recovery that has cwm built in eg hells fusion #50 for stock based roms
Can't give you any more support with this as I'm just repeating what Iv already said

[Root] CFAutoRoot For SM-T807T/SM-T807P + Firmwares

Note: I did not make any of these root methods. Credits of the people who confirmed/ported cfautoroot is at the end of this post. I got permission to post these root methods here as most of the discussion happened in the General thread. I am not responsible for any damages done to your device. This will trip knox as always and this root method is only for the TMobile and Sprint Tab S 10.5! You've been warned!
Root is now available for these devices! Hope you enjoy and hopefully this should get some development going!
CFAutoRoot for SM-T807T(Tmobile)
Ripx88 confirmed T805 Cfautoroot works for SM-T807T, but you may have a broken recovery. He also confirmed that Twrp and Philz CWM for SM-T805 also works on the SM-T807T. Thanks to him!
Download: http://download.chainfire.eu/477/CF...-Auto-Root-chagalllte-chagallltexx-smt805.zip
CFAutoRoot For SM-T807P (Sprint)
Goriell ported Cfautoroot to this model. Props to him! Still awating for others to confim.
Download: https://mega.co.nz/#!eoB3TbxI!fdUUK-GJFfDx7ietfosnxxHHB2WN4tV0SGieQsdL9tA
Mirror: https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
Odin Download
http://forum.xda-developers.com/showthread.php?p=33970642
How to install
Make sure that in settings>general>security reactivation lock is OFF
edan1979 said:
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA (AP in odin v3.x) button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, manually shutdown your device and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Flashing with Odin
1. Put your phone into download mode. To do this turn the phone off and then press volume down+home button+power button at the same time. You will then get a warning saying press up to continue and down to cancel, press volume up and you are now in download mode
2. Start Odin
3.At this point please make sure that ONLY TWO OPTIONS TICKED are "Auto Reboot" and "F.Reset Time" (otherwise you could end up with a very expensive paperweight)
{
"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"
}
4. If there was only one tar file when you extracted the firmware put it in the PDA section.This just means this file contains the PDA+PHONE+CSC all in one firmware
If there are three files they should have one of PDA/PHONE/CSC in their names look for this and put them in the corresponding section.
5. Plug your device into the computer, wait for the drivers to install and then wait for the ID:COM section to turn blue.
6.ONCE AGAIN CHECK YOU HAVE NOT TICKED RE-PARTITION OR PUT IN A PIT FILE
7.Press start and the flash will begin, once this has started do not remove the usb cable or turn of your computer or the device the phone will reboot once the flash has finished.
Click to expand...
Click to collapse
Thanks:
-Chainfire for Cfautoroot method
-Ripx88 for confirming root working on T807T. Helped ALOT!
-goriell for explaining how to port and porting it to SM-T807P. Helped ALOT!
-Samsung
-Samsung updates for firmware... took me 14 hours to download and mirror
-Many many more
-Tkkg1994 for help on somethings
Post from main thread.
CF-Auto-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root. In essence, it does nothing but install and enable SuperSU on your system, so apps can gain root access.
Donate
CF-Root and CF-Auto-Root have been available for many devices (over 50 different models !) and have clocked over 9 million downloads. This is not even counting custom ROMs that include CF-Root (non-Auto) kernels. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every user had donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery (note that any other recovery you may have installed will be overwritten !)
What's the difference between CF-Auto-Root and CF-Root, and/or other root solutions ?
CF-Root (non-Auto) are manually built rooted kernels and/or flashables that usually provide more than "just root". CF-Auto-Root is built on an automated system that I am constantly improving that takes a stock recovery image and returns an automated rooting packages. These packages are designed to install and enable SuperSU on your device, so apps can gain root access, and nothing more.
The difference with many other rooting solutions is that those will often install a custom recovery for you (I am personally moving away from custom kernels and recoveries, for various reasons), while with CF-Auto-Root you will end up with a stock recovery again.
Not included - custom recovery
A custom recovery like CWM or TWRP is not included.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
Bugs.
WIFI Bug Fix: In root explorer go into system/etc/dhcpcd/dhcpcd-run-hooks
It needs to have permissions fixed to "execute" by "user" "group" and "others" by using your favorite file explorer
this will fix your "obtaining ip address loop" without having to ever use static ip address- goriell
You know what.. here is the kernel and stock recovery for the SM-T807T.
Bop! https://mega.co.nz/#F!PwwT3JLQ!KHZNbb3ddgfStcdcB4rmlQ
Firmware to SM-T807T: https://mega.co.nz/#!ylYEBA4D!yWUPtuT60dLCIy_zCN_rqnN2L319oZYSCSFtOC_Pv6Q
Firmware for SMT807P: https://docs.google.com/file/d/0B5DZenb7A53caXhNQkhMb0NkMFU/edit?usp=docslist_api
Bop! Recovery and boot image for SMT807P: https://www.dropbox.com/sh/h5zw61wdn6rx319/AADS2Wb8OFDw3DxpuES7GI2Va?dl=0
Incase anything goes wrong Enjoy
Will look into this later this evening. I have been patiently waiting for a root method for my Sprint Tab S, so I'm really hoping this pans out. Thanks for posting the info!
wosiek said:
Will look into this later this evening. I have been patiently waiting for a root method for my Sprint Tab S, so I'm really hoping this pans out. Thanks for posting the info!
Click to expand...
Click to collapse
Please let me know if it works smoothly. I'm still in the process of tweaking it and looking for bugs.
Anyone have the firmware for the T807P? I see the T807T is up there, but think us Sprint users would need the correct firmware correct or we can run the TMo variant and be fine? Just want to confirm. If that is all we need. I'll go ahead with the process right now.
gorriel said:
Please let me know if it works smoothly. I'm still in the process of tweaking it and looking for bugs.
Click to expand...
Click to collapse
Hey do you have the firmware downloaded? If so can you mirror it for us? I dont have an extra 14 hours to download and upload the firmware
Tried to download the CFAutoRoot file (Sprint SM-T807P) from the link in the OP, but the webpage couldn't be found.
Anyone else experience similar behavior?
wosiek said:
Tried to download the CFAutoRoot file (Sprint SM-T807P) from the link in the OP, but the webpage couldn't be found.
Anyone else experience similar behavior?
Click to expand...
Click to collapse
Works fine for me. Are you on att? Mirror to google drive will be coming. Standby
Yeah, the WAN at the office is managed by ATT. Are they notorious for having issues with MEGA?
I'll try downloading again from home this evening - meant to do that last night, but it fell off my radar.
wosiek said:
Yeah, the WAN at the office is managed by ATT. Are they notorious for having issues with MEGA?
I'll try downloading again from home this evening - meant to do that last night, but it fell off my radar.
Click to expand...
Click to collapse
Att blocks mega because of the history of mega and copyright claims. Ill make another mirror with google drive.
For anyone having trouble with the T807P root please post information on what happened and I will try to troubleshoot it. It is suppose to be a quick and easy CFAutoRoot using ODIN. I will say that it doesn't work if you are trying to use Odin on a virtual machine. It will stop as it tries to upload the cache.img. There is something about virtual machines that blocks it or Odin just doesn't like.
Uploading Sprint firmware now Will also upload the boot.img amd recovery if a dev wants them.
CFAutoRoot For SM-T807P (Sprint)
Can you host the
CFAutoRoot For SM-T807P (Sprint) on something other than mega, Like Drive or Dropbox please. I have Time Warner and i can't download it for some reason.
kingakuma said:
Can you host the
CFAutoRoot For SM-T807P (Sprint) on something other than mega, Like Drive or Dropbox please. I have Time Warner and i can't download it for some reason.
Click to expand...
Click to collapse
Will do hold on
DUHAsianSKILLZ said:
Will do hold on
Click to expand...
Click to collapse
Thank you my good sir.
kingakuma said:
Thank you my good sir.
Click to expand...
Click to collapse
Here ya go https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
DUHAsianSKILLZ said:
Here ya go https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
Click to expand...
Click to collapse
Thank you worked great with Odin 3.09
I can only access odin download mode, i can't access any recovery, how can I flash back to stock?

Categories

Resources