New Tools for Root and Flashing - AT&T Samsung Galaxy S II SGH-I777

Three new tools have been released or updated by their developers recently that may have a major impact on how we root and flash our phones. I will need to update the Guides with the new information, but first some confirmations are needed.
1) Chainfire has released a tool called Mobile Odin which will flash roms from the phone. There are two versions, Mobile Odin Pro which is available on the market for a small fee, and Mobile Odin Lite which is available free to xda members. Quoting from his thread: Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear. This tool was updated today (November 28, 2011) to work with a host of new phones, including SGH-I777.
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
3) CLShortFuse developed SuperOneClick Root over a year ago, and recently updated it (November 10, 2011) to include the ZergRush exploit and SU 3.0.
With these tools, if they work as advertised on our phone, it will be possible to root and install custom software without incrementing the flash counter. When you have used one or more of these tools, I would appreciate it if you would post your results back here in this thread so I can gather information to update the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!!
Thanks.

I have used the new version of SuperOneClick with the zergRush exploit to successfully root my SG2. However I will mention that the Unroot feature of SuperOneClick did not work. I simply used the unroot script DooMLoRD provided in his thread and I was able to unroot successfully. I am currently still unrooted as I have a business app I have to run that will not if it detects root. However, I assume either SuperOneClick or DooM's script will work once again if needed.

Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.

lambition said:
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
Click to expand...
Click to collapse
No. At some point we may figure it out to reset it through software, but until then only jigs reset the counter.
Sent from my páhhōniē

I recently noticed after flashing to UnNamed that the caution sign didn't appear. Has the ROM been developed to not trigger it or does it have to do with using the jig? I bought a jig a month ago from mobiletechvideo and I've only used it once. I've flashed CM7, Galnet MIUI and UnNamed since with no caution sign.

These tools will probably provide a new way to flash custom software without incrementing the flash counter. None of them will remove the warning triangle or reset the flash counter, however.
The only two ways to remove the warning triangle, and get the AT&T boot screen back, are 1) jig and 2) flash a stock kernel with Odin or Heimdall.
The only known way to reset the flash counter is with a jig.
The only thing that causes the I9100 boot screen with the warning triangle and increments the flash counter is flashing a custom kernel with Odin or Heimdall. So, you can flash with adb or Android Terminal Emulator or ClockworkMod Recovery, or appearantly with the new Mobile Odin, without incrementing the flash counter.
I'm definitely interested in hearing about peoples results using these tools. That is the main purpose of this thread. Thanks.

I used the DooMLoRD method, which is really easy, and it's been working for several weeks with no issues. I haven't needed to unroot, so haven't tried that yet.
[Edit] I haven't tried flashing a new rom, so I can't comment on the flashing without triangle. I just wanted root for a couple small issues, I'm going to wait to start flashing until some stable releases of ICS start appearing.

I've used SuperOneClick with Zerg to root, then installed Entropy's Daily Driver through Android Terminal then flashed UnNamed through CWM all without tripping any counters.
Love it!

So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!

Thanks for sharing

avidmovies said:
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Click to expand...
Click to collapse
The guide is still good. I'd like to provide all the options though.
At this point, it is clear that rooting with either SuperOneClick or ZergRush will be part of step 2 in the guide, and may be easier than using Odin or Heimdall.
Still waiting for any information on Mobile Odin. If it's easy to use on our phones, it may be an improvement over steps 3 and 4.

Thanks!
Sent from my Nexus S 4G using Tapatalk

Used the zergrush root and then mobile odin to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē

gr8hairy1 said:
Used the zergrush root and then mobile odin lite to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
Click to expand...
Click to collapse
Did you use lite or pro?
Could you describe using Mobile Odin, setting it up, how the flashkernel works, etc?

I downloaded the zergrush root package from the op. Then went to (edit):
http://forum.xda-developers.com/showthread.php?t=1347899
and downloaded mobile Odin lite.
First downloaded Samsung kies for the proper drivers then downloaded and opened zergrush. When you first open zergrush by opening 'run me' (i think it was called) it will tell you everything you need to have already done before plugging in your phone. It recommends changing your screen timeout to 10. I'm guessing this is for adb use, as adb can not connect to your phone if the screen is off.
I then plugged the phone in and pressed a key for it to start. All in all it took around 5 minutes. Majority of the time was processes coming up that waited 40 seconds. Guessing the phone was doing things that you couldn't see. At no time did I need to press anything on the keyboard or phone.
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case out would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on.
That gives you this screen:
{
"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"
}
After that:
The only main option is kennel, and that's all I neededafter choosing it I got:
It was stored on the root of my internal sdcard, so I selected internal and then seen:
It obviously automatically put the kernel at the top by itself. Picked it and then had:
Chose flash kernel, rebooted the phone, and it was done. Downloaded unnamed, used three button hold to get into recovery, sure enough CWM was there, chose unnamed. Rebooted and viola, custom rom. Through this whole process the boot screen never changd to i9100 with the yellow exclamation point or was the flash counter tripped.
Sent from my páhhōniē
(yeah, I typed that all on my phone, talk about a sore hand)

I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?

@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
gr8hairy1 said:
I downloaded the zergrush root package from the op. Then went on the android market and downloaded mobile Odin lite.
Click to expand...
Click to collapse
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
...
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case it would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on...
Click to expand...
Click to collapse
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.

iainash said:
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
Click to expand...
Click to collapse
Yeah buddy! Need to put that step in there.
Though I'm a yengling fan
Edit: lol, just seen my guinness spelling error. Nice to know swype appreciates a good beer
Sent from my páhhōniē

creepyncrawly said:
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
Click to expand...
Click to collapse
You're right, I downloaded it from xda. Not sure how I got that mixed up. I'll update my post. Though I had taken a vicodin, alieve, and 2 benedryl around 1am, and it was almost 2am when I posted that. Stupid butt surgery is kicking my butt.
And correct, I did not download his flashkernel. I was tempted to flash it to check out what it did but it wasn't my phone I was working on. I stuck with flashing what I knew would get me cwm, and flashed Entropy512's kernel. Flashed with no issue.
Sent from my páhhōniē

creepyncrawly said:
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
Click to expand...
Click to collapse
First I wanted to say THANK YOU for all your help. I was able to follow your guide to flash my phone with out incrementing the flash counter.
But before I did that I did try DoomLoRD root fix. It worked as advertised and was exactly how the instructions were documented. I had no issues.
Again big thanks to you for all your help!

Related

Can't root using SuperOneClick???

Bear with me guys, this month my phone seems to be having so many issues for no reason at all...
I odin'd today..
and I was going to root just as usual. on stock JFD, going to root by using superonelick - placed phone in usb debugging mode -
started it up and then i get this:
{
"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"
}
if image not showing: http://grab.by/aC2j
I will root using another method for now, but I'm wondering why it didnt work?
http://forum.xda-developers.com/showthread.php?t=849028
use the update.zip from somewhere in there
superoneclick never worked for me, always ended up not responding just after starting and i had to close it with tas manager
Damn noobs
Sent from my GT-I9000 using XDA App
Try using the Toolbox for Vibrant, you'll find it in the dev section or in the Vibrant bible. For some reason it has always done what or programs couldn't. Good luck.
Sent from my GT-P1000 using XDA Premium App
why root? there is no need to root in JFD to get CWM working. here is the update.zip, put it on sdcard, and boot into it, and then flash CM7 by hand. BAM! you're golden!
no need for root.
Yea just copy update.zip to sd card, reboot into standard recovery, apply update.zip, hit it a second time and then boom your in cwm.
You do have usb debugging enabled when your trying to root right? And usb is not connected as a mass storage device? If you do it wont work...!
Sent from my SGH-T959 using XDA Premium App
the noob guide I wrote has both methods, each with their own update.zip
I don't like superoneclick. neither does your pc's antivirus.
bfranklin1986 said:
Damn noobs
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hey hey hey..... don't player hate.... player participate. Lol
s15274n said:
the noob guide I wrote has both methods, each with their own update.zip
I don't like superoneclick. neither does your pc's antivirus.
Click to expand...
Click to collapse
Actually. To all mentioning the update that's 'd the method is used and it was from your thread.
Also to the guy calling me a noob.
lol.
geoffcorey said:
why root? there is no need to root in JFD to get CWM working. here is the update.zip, put it on sdcard, and boot into it, and then flash CM7 by hand. BAM! you're golden!
no need for root.
Click to expand...
Click to collapse
That Noob guide is titled for rooting method.
so that thread is misleading because it only install CWM without rooting the vibrant phone.
souleater11 said:
That Noob guide is titled for rooting method.
so that thread is misleading because it only install CWM without rooting the vibrant phone.
Click to expand...
Click to collapse
Option A is for rooting.
Option B is for installing CWR and then flashing a new ROM straight away.
That is actually how I rooted my with Option A and messed around and cleaned the bloat from my stock ROM before I decided on which custom to flash b/c I hate Superoneclick and have never got it to work correctly on any phone. Some others have, I haven't.
Woodrube said:
Option A is for rooting.
Option B is for installing CWR and then flashing a new ROM straight away.
That is actually how I rooted my with Option A and messed around and cleaned the bloat from my stock ROM before I decided on which custom to flash b/c I hate Superoneclick and have never got it to work correctly on any phone. Some others have, I haven't.
Click to expand...
Click to collapse
Thank you for this clarification.
btw, i plan to use method A.
it seems steps 3 to 5 (OP Noob Guide) is exclusively for method B.
1. can you share me your experience in the steps 3 to 5 for using method A?
2. Do I have to Select Reinstall packages again for method A ?
If all you are wanting to do it root your phone, just download Option A.
This is what I did (without ever plugging my phone into PC once).
1. I downloaded Option A to my SDcard.
2. Booted into stock Recovery and since it was already labeled Update.zip, I just installed it that way. (You could rename it something like Rooter.zip and then you would pick the option in Recovery to :install from SD
3. Booted up and made sure Superuser.apk was there. It was.
4. Went to market to download CWR (free version) and installed it.
5. Made back up through CWR
6. Removed Bloater,blah blah blah and not once did I ever plug my phone in. Maybe I got lucky, maybe it was something else, but it worked for me. Later on I did copy all that to my PC because as you know, links do tend to get broken around here.
Less than a week later I had read and picked out custom ROM and flashed that. Most custom ROMs have a recovery already built into them.
Good luck and remember the first thing that you should do whenever you Root a phone is to get into Recovery and make a back up then and there, so that if/when you ever have to warranty your phone, you can restore it and remove the SU.apk and they will be none the wiser.
Note that Option B does have CWR included and I have read here and there that CWR free isn't in the market for some reason. Not sure about that though.
Thanks a lot. its a great help. i will try this.
it seems the free version of ROM manager is not anymore compatible in Android 2.1
Whitehawxx (spelling is probably off on that) has a 2.2 full bloat in the Dev thread if you want to use that and then you can use CWR from market. Just read the OP. Good luck and I am out for the day.
Thanks for the suggestion but I will root from stock 2.1 and just install an old version of ROM manager from 4shared.com
Woodrube said:
If all you are wanting to do it root your phone, just download Option A.
This is what I did (without ever plugging my phone into PC once).
1. I downloaded Option A to my SDcard.
2. Booted into stock Recovery and since it was already labeled Update.zip, I just installed it that way. (You could rename it something like Rooter.zip and then you would pick the option in Recovery to :install from SD
3. Booted up and made sure Superuser.apk was there. It was.
4. Went to market to download CWR (free version) and installed it.
5. Made back up through CWR
6. Removed Bloater,blah blah blah and not once did I ever plug my phone in. Maybe I got lucky, maybe it was something else, but it worked for me. Later on I did copy all that to my PC because as you know, links do tend to get broken around here.
Less than a week later I had read and picked out custom ROM and flashed that. Most custom ROMs have a recovery already built into them.
Good luck and remember the first thing that you should do whenever you Root a phone is to get into Recovery and make a back up then and there, so that if/when you ever have to warranty your phone, you can restore it and remove the SU.apk and they will be none the wiser.
Note that Option B does have CWR included and I have read here and there that CWR free isn't in the market for some reason. Not sure about that though.
Click to expand...
Click to collapse
if I follow your rooting method (A), is it safe to flash a miui gingerbread mod roms (miui nb or miui galnet) ?
to paraphrase, is it safe to flash from a newly rooted Android 2.1 to custom rom Android 2.3 ?
assuming I successfully flashed to Android 2.3, is my Super User still intact?
I just apprehensive about your method A, because some rooting methods (Z4root) when transfer to another firmware can cause a lost of Super user permission.

[Q] Help wrong kernel (I9100) Solution?

Hi XDA
First of all id like to apologize if there is something not clear it’s just that English is not my native language.
I recently got my AT&T SGSII from the US and as I live in Bolivia the first thing I wanted to do was to root and unlock it to be able to use the phone here.
Unfortunately I rushed things and made a stupid mistake. I think I flashed an incorrect kernel, one that is for the SGSII I9100.
In Odin I marked “PDA” and flashed the kernel: “XWKDD_insecure” the phone rebooted and shows the loading screen: “Samsung Galaxy S II I9100” with the yellow triangle. Then I wanted to run the “s2 root” to complete the process but didn’t work, there was when I realized that something was wrong.
After unplugging the phone, the “Back” and “Search” buttons didn’t work at all. Now, as I didn’t complete the rooting process and I am a newbie I don’t know what do.
I’d appreciate if someone could help me. Should I reflash an original kernel to have the phone like before? If so, which one exactly?
Thanks a lot in advance.
This is the information showed about the phone now:
Android Version: 2.3.4
Baseband Version I777UCKH7
Kernel Version 2.6.35.7
SrGiO said:
Hi XDA
First of all id like to apologize if there is something not clear it’s just that English is not my native language.
I recently got my AT&T SGSII from the US and as I live in Bolivia the first thing I wanted to do was to root and unlock it to be able to use the phone here.
Unfortunately I rushed things and made a stupid mistake. I think I flashed an incorrect kernel, one that is for the SGSII I9100.
In Odin I marked “PDA” and flashed the kernel: “XWKDD_insecure” the phone rebooted and shows the loading screen: “Samsung Galaxy S II I9100” with the yellow triangle. Then I wanted to run the “s2 root” to complete the process but didn’t work, there was when I realized that something was wrong.
After unplugging the phone, the “Back” and “Search” buttons didn’t work at all. Now, as I didn’t complete the rooting process and I am a newbie I don’t know what do.
I’d appreciate if someone could help me. Should I reflash an original kernel to have the phone like before? If so, which one exactly?
Thanks a lot in advance.
This is the information showed about the phone now:
Android Version: 2.3.4
Baseband Version I777UCKH7
Kernel Version 2.6.35.7
Click to expand...
Click to collapse
My brother also did something like you when he tried to root his AT&T SGSII, we just flashed a new one, not entirely sure which version tho.
But you can try one from http://forum.xda-developers.com/showthread.php?t=1286432
Already covered. Try looking in the sticky and find the 'return to stock' thread.
{
"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"
}
I was too busy to read.
Sent from my SGH-I777 using xda premium
Intub8 said:
View attachment 930201
I was too busy to read.
Click to expand...
Click to collapse
Nice first post!
Thanks for replying and im sorry i took this much to reply, i broke my laptop and i ve been disconnected these days :s.
I read the posts u suggested me, and yes im a total newbie so i would appreciate if someone can tell me if i should flash only the sotck kernel to fix the buttons that are not working or is it necessary to flash a rom or a rom/kernel combination to fix the problem? Thanks in advance
SrGiO said:
Thanks for replying and im sorry i took this much to reply, i broke my laptop and i ve been disconnected these days :s.
I read the posts u suggested me, and yes im a total newbie so i would appreciate if someone can tell me if i should flash only the sotck kernel to fix the buttons that are not working or is it necessary to flash a rom or a rom/kernel combination to fix the problem? Thanks in advance
Click to expand...
Click to collapse
Flash back to stock completely. Then start over again with correct flashitis apparatus!
Sent from my SAMSUNG-SGH-I717 using xda premium
SrGiO said:
Thanks for replying and im sorry i took this much to reply, i broke my laptop and i ve been disconnected these days :s.
I read the posts u suggested me, and yes im a total newbie so i would appreciate if someone can tell me if i should flash only the sotck kernel to fix the buttons that are not working or is it necessary to flash a rom or a rom/kernel combination to fix the problem? Thanks in advance
Click to expand...
Click to collapse
If you flashed just the I9100 kernel then you can correct it by flashing only an I777 kernel. From reading your OP I'm pretty sure that is the case. However, if you flashed a complete I9100 firmware, then you will need to flash the complete I777 firmware.
creepyncrawly said:
If you flashed just the I9100 kernel then you can correct it by flashing only an I777 kernel. From reading your OP I'm pretty sure that is the case. However, if you flashed a complete I9100 firmware, then you will need to flash the complete I777 firmware.
Click to expand...
Click to collapse
Thanks a lot!
Yes i only flashed the kernel and according to you i will have to flashed the official i777 kernel.
I ve been reading posts from some people who had problems tryin to get back to stock and i dont know if doing a wipe would help not to have a failed process. I ask this because as I flashed the wrong kernel now when i get into the recovery mode i cant select with the on/off button so basically i cant do anything in it.
I would aprecciate if someone could tell me what method should i use in order to have less problems. Is Odin the rigth one or should i use another?
Thanks a lot
SrGiO said:
Thanks a lot!
Yes i only flashed the kernel and according to you i will have to flashed the official i777 kernel.
I ve been reading posts from some people who had problems tryin to get back to stock and i dont know if doing a wipe would help not to have a failed process. I ask this because as I flashed the wrong kernel now when i get into the recovery mode i cant select with the on/off button so basically i cant do anything in it.
I would aprecciate if someone could tell me what method should i use in order to have less problems. Is Odin the rigth one or should i use another?
Thanks a lot
Click to expand...
Click to collapse
It doesn't have to be the official (stock) I777 kernel. You could flash Entropy's Daily Driver kernel or SiyahKernel.
Go to the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter linked in my signature and use one of step 3a, 3b or 3c.
creepyncrawly said:
It doesn't have to be the official (stock) I777 kernel. You could flash Entropy's Daily Driver kernel or SiyahKernel.
Go to the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter linked in my signature and use one of step 3a, 3b or 3c.
Click to expand...
Click to collapse
I really appreciate your help, i only have one more question. As i am planning to unlock the phone, should i use one of those kernels to be able to root it? Is there any difference if i use one of them over the insecure version of the official one or there is an specific in this case?
Thanks!!!
Entropys kernel has root and its insecure.
Sent from my SGH-I777 using Tapatalk
SrGiO said:
I really appreciate your help, i only have one more question. As i am planning to unlock the phone, should i use one of those kernels to be able to root it? Is there any difference if i use one of them over the insecure version of the official one or there is an specific in this case?
Thanks!!!
Click to expand...
Click to collapse
I should have been more clear in my previous answer. I gave you the wrong advice since your attempt to root with s2 root was unsuccessful. If you follow my guide, you must root first, then install the kernel. All of methods 3a, 3b and 3c require root. You can use one of the methods in step 2 to root. DooMLoRD's Easy Rooting Toolkit is the preferred method if you are on 2.3.4, which your original post says you are.
Yes, Entropy512's Daily Driver kernel is insecure, meaning that you can use it to root the phone, if you can get it onto a phone that is not already rooted. However, he does not make an Odin flashable tar version available, only CWM flashable zip files, so you would have to use heimdall to flash the zImage. If you want to use that method before you root, follow the instructions in step 2d of the guide, except flash only the kernel as such:
Code:
heimdall flash --kernel --zImage
creepyncrawly said:
I should have been more clear in my previous answer. I gave you the wrong advice since your attempt to root with s2 root was unsuccessful. If you follow my guide, you must root first, then install the kernel. All of methods 3a, 3b and 3c require root. You can use one of the methods in step 2 to root. DooMLoRD's Easy Rooting Toolkit is the preferred method if you are on 2.3.4, which your original post says you are.
Yes, Entropy512's Daily Driver kernel is insecure, meaning that you can use it to root the phone, if you can get it onto a phone that is not already rooted. However, he does not make an Odin flashable tar version available, only CWM flashable zip files, so you would have to use heimdall to flash the zImage. If you want to use that method before you root, follow the instructions in step 2d of the guide, except flash only the kernel as such:
Code:
heimdall flash --kernel --zImage
Click to expand...
Click to collapse
There should be an Odin-flashable .tar for 1/23 - it's not the latest, but the idea is to have one Odin-flashable release from which someone can flash another release.
creepyncrawly said:
I should have been more clear in my previous answer. I gave you the wrong advice since your attempt to root with s2 root was unsuccessful. If you follow my guide, you must root first, then install the kernel. All of methods 3a, 3b and 3c require root. You can use one of the methods in step 2 to root. DooMLoRD's Easy Rooting Toolkit is the preferred method if you are on 2.3.4, which your original post says you are.
Yes, Entropy512's Daily Driver kernel is insecure, meaning that you can use it to root the phone, if you can get it onto a phone that is not already rooted. However, he does not make an Odin flashable tar version available, only CWM flashable zip files, so you would have to use heimdall to flash the zImage. If you want to use that method before you root, follow the instructions in step 2d of the guide, except flash only the kernel as such:
Code:
heimdall flash --kernel --zImage
Click to expand...
Click to collapse
Maybe Ive been asking obvious questions because Im a newbie, so thanks for the help.
Well Im indecisive now , the phone must rooted to use your method and I cant flash Entropy512's Daily Driver kernel via Odin, plus I really dont know much about flashing through CWM (And now I cant do it directly from CWM because the SELECT button doesnt work).
Do you think that flashing the original secure kernel in order to fix the "SELECT" button problem would be a better option? That way i would be able to flash via CWM, and start again. If so, this should return the phone back to stock completely? Even the yellow triangle will be gone? If this is not the best thing to do can u suggest me another one?
Thanks!
SrGiO said:
Maybe Ive been asking obvious questions because Im a newbie, so thanks for the help.
Well Im indecisive now , the phone must rooted to use your method and I cant flash Entropy512's Daily Driver kernel via Odin, plus I really dont know much about flashing through CWM (And now I cant do it directly from CWM because the SELECT button doesnt work).
Do you think that flashing the original secure kernel in order to fix the "SELECT" button problem would be a better option? That way i would be able to flash via CWM, and start again. If so, this should return the phone back to stock completely? Even the yellow triangle will be gone? If this is not the best thing to do can u suggest me another one?
Thanks!
Click to expand...
Click to collapse
Personally I always flash stock KH7 and then root it with superoneclick 2.3
SrGiO said:
Maybe Ive been asking obvious questions because Im a newbie, so thanks for the help.
Well Im indecisive now , the phone must rooted to use your method and I cant flash Entropy512's Daily Driver kernel via Odin, plus I really dont know much about flashing through CWM (And now I cant do it directly from CWM because the SELECT button doesnt work).
Do you think that flashing the original secure kernel in order to fix the "SELECT" button problem would be a better option? That way i would be able to flash via CWM, and start again. If so, this should return the phone back to stock completely? Even the yellow triangle will be gone? If this is not the best thing to do can u suggest me another one?
Thanks!
Click to expand...
Click to collapse
As Entropy noted above, he does have one tar package of his daily driver kernel which you can flash in Odin. Go to the OP of his thread in development and it is the top item of the downloads named: DD_01232012.tar - [Click for QR Code] (5.00 MB, 348 views). I had forgotten that he made that tar package available.
If you flash the original (stock) secure kernel, it contains 3e recovery which does not contain ClockworkMod Recovery flashing tools. However, you can follow the sequence in my guide by flashing back to the stock kernel, rooting, and then installing the insecure kernel.
creepyncrawly said:
As Entropy noted above, he does have one tar package of his daily driver kernel which you can flash in Odin. Go to the OP of his thread in development and it is the top item of the downloads named: DD_01232012.tar - [Click for QR Code] (5.00 MB, 348 views). I had forgotten that he made that tar package available.
If you flash the original (stock) secure kernel, it contains 3e recovery which does not contain ClockworkMod Recovery flashing tools. However, you can follow the sequence in my guide by flashing back to the stock kernel, rooting, and then installing the insecure kernel.
Click to expand...
Click to collapse
Yes, I think I will use the second option by flashing to stock kernel and go on. When you tell me to follow the sequence of your guide, do you refer to one of the methods of [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter? or are you talkin about any other post refered to flashing stock kernel and then follow your guide to root the phone?
Can I use your post I777UCKH7 Return/Unbrick to Stock (or Root) Odin3 One-Click Downloaders to flash the stock kernel or Im taking the wrong way?
Thanks
I just wanted to say thanks to everybody who helped me with my problem, i could succesfully go back to stock, root and unlock my GSII following the guides.
Thanks everybody! especially to Entropy for the guides and creepyncrawly for the patience

How to Unlock Your Bootloader - Firmware Version VRALJB

This technique will not work if you have applied the OTA update from 18January2012. Go here: http://forum.xda-developers.com/showthread.php?t=2118348
This device is now unlocked to the point of development board status. After you finish this process, you will have the ability to destroy your device so make sure you flash CAREFULLY. Using only the files in this guide, there is no way to brick your device. Stay away from Odin once you've finished this process unless you're flashing back to stock.
TLDR version: Put your device into USB Debug Mode. Run CASUAL Injection 9. Flash the Suck It Verizon Bootloader with Odin3 If CASUAL calls you a Noob, flash the PIT and Bootloader Baseline package with Odin.
Introduction
The instructions have changed DRAMATICALLY since initial release. It's super simple. You are expected to be stock running I605VRALJB version of software. If you have modified your device using another procedure previous to this, undo it. This is where you start.
Prerequisites
any I605VRALJB stock bootloader and a stock ROM or a rooted stock ROM.
Downloads (in the order you need them)
The Pit File This is the stock i605VRALJB Pit file. It works to make your device partitions stock again. Flashing this will prepare your device for unlock.
The Bootloader Baseline package - Odin Package This is a stock I605VRALJB bootloader, params, kernel and recovery. Flashing this will prepare your device for unlock and relock your device in a safe manner. *This will reset your device if you screw up during the process so you can start over.
Odin3 is a tool from Samsung used to flash Odin packages.
CASUAL Suck It Verizon Injection 9 CASUAL stands for Cross-Platform ADB Scripting Universal Android Loader. In this case, it deploys the Suck It Verizon exploit. To use CASUAL you must enable "Settings>Developer Options>USB Debugging" on your device. CASUAL is used as an automation tool so that you don’t have to use ADB, watch for results, upload files, download files, make decisions and enter commands. CASUAL will make those determinations for you. This guide is much shorter because of it. Source code for CASUAL can be found at http://android-casual.googlecode.com. The exploit was designed by Ralekdev, packaged, tested and made safe by AdamOutler. --DON'T MIRROR, this is in development.
Suck It Verizon Bootloader 2- Odin Package provides a bootloader which has been modified to ignore all security checks at the highest level possible. This firmware runs every time you turn on your device. The SBoot's job is to validate Download Mode flashes. It also validates and executes the kernel. This bootloader will not validate, only download and execute. It will also allow you to flash anything you like, including firmware packages which will destroy your device. This bootloader replacement is not only a Bootloader Unlock, this is an IROM Unlock... The lowest level unlock possible. The bootloader was developed by Ralekdev, conceptualized by Rebellos, tested and packaged with a Sprint GN2 TWRP Recovery by AdamOutler.
Instructions
If these instructions dont quite make sense, check out the video below.
Part 1: Install the Baseline
Launch Odin or click the "reset" button at the bottom if it's already open.
Place the sch-i605-16gb.pit into the "PIT" section of Odin.
Place BootloaderBaseline2.tar.md5.gz into the "Bootloader" section of Odin.
Click Start
Part 2: Run the CASUAL Exploit
Put your device into development mode. Settings>Developer Options>USB Debugging
You need Java installed to double-click or run with "java -jar path_to_file.jar" Do you have java?
Click the "Root and Unlock Me Now!" button and accept( or continue) any notifications which may pop up on the phone or CASUAL.
When prompted by the phone, press the Volume Up key then continue to Part 2.
Part3: Install Suck It Verizon Insecure Bootloader+Recovery
Start Odin or click the "reset" button at the bottom if it's already open.
Place SuckItVerizon_Odin_Package2.tar.md5.gz into the "Bootloader" section of Odin
Click Start
You may now flash a custom ROM of your choice to your 100% IROM/Bootloader unlocked device. You are now Rooted and have the ability to install any CWM recovery zip with TWRP.
Video instructions
Troubleshooting Windows
Q. Why is CASUAL calling me a noob?
A. You need to Install the "Bootloader Baseline" with odin. We only support ONE bootloader, that's VRALJB.
Put your device into Odin Mode by powering on with Volume Down and Home pressed.
Put the BootloaderBaseline.tgz from above into the "Bootloader" section of Odin.
Click Start.
Q. Why am I bootlooping or the device won't boot?
A. You flashed the wrong thing at the wrong time. Flash the bootloader baseline in Odin, then repeat the instructions above.
Q.Why isn't CASUAL working correctly
A. Try redownloading the latest CASUAL package. Also make sure you're running the latest version of Java.
Q.Why is Odin is failing to open or use the package?
A. The download was damaged. Redownload it.
Q.Other unexplained problems?
A.Try using the proper drivers.
1. Go to device manger right-click and uninstall on the device.
2. Go to add/remove programs, uninstall any driver packages.
3. Unplug your device
4. Install Samsung Kies http://www.samsung.com/us/kies/
Q. How come CASUAL didn't start the first time?
A. Unplug and replug your device, or click CASUAL again and deal with both windows. This is a known issue. I cannot reproduce it in my development environment, it only happens on production compilations in JAR format and affects only Windows. If you'd like to submit a patch, you can get the source and I can add you as a contributor to http://android-casual.googlecode.com.
Q. Why won't CASUAL connect to the device?
A. If you've already installed the PROPER drivers, try disabling any firewalls. ADB uses a network connection to talk to your device. ADB is a network transparent protocol.
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Troubleshooting Device
Q.Why does CASUAL fail to find a rooted device?
A. Check the SuperSU/Superuser Permissions app to verify that you have not inadvertently denied root access to shell.
Q. Why won't my phone start? why is it saying unauthorized software?
A. You unlocked, flashed something, then relocked. You need to flash back to stock VRALJB then repeat the unlock procedure. Use this guide http://forum.xda-developers.com/showthread.php?t=2040264
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Pictures
Heres some pictures to show the newfound capabilities of your device.
TWRP Recovery
{
"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"
}
CASUAL
Verizon device running AT&T firmware
Verizon device running International Firmware
Download count of 63 from testing- Note, do not flash any i9300 ROMs.
Conclusion
Congratulations, You're Unlocked. Your Galaxy Note 2 has gone from the most secure device on the market, to the least secure device publicly available. Your device will now accept any flash. Be careful and dont flash with Odin again. Stick to CWM zip packages so as to lower your risk.
Reserved for technical details
Thanks everybody involved! quick question, you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Edit* Yes you can odin back to a stock i605 rom only!
Thank you Adam. Really appreciate all your hard work
Sent from my SCH-I605 using Tapatalk 2
Thanks! Will report back downloading now
Sent from my SCH-I605 using xda app-developers app
You Rock!
droidstyle said:
Thanks everybody involved! quick question; you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Click to expand...
Click to collapse
Yeah I would like to know that as well.
Can't wait to do thus after school! Can't wait for the roms to start flooding the forums.
Sent from my rooted galaxy note 2... U mad?
Amazing, I am speechless!!! Thanks for all your hard work!
awesome work thanks
Thanks for all your work
FTW
Very cool. Great stuff Adam. Suck it Verizon indeed. :highfive:
Well...2 hours to download the Revision3 file on our crappy work internet (but damned if I'm going to wait until I get home). At least I'll get to watch the successes/failures roll in in the meantime.
Also...you mention to stick to flashable zip packages. If I understand correctly, flashing through recovery will still run the typical recovery checks, but ODIN will not?
Is there any reason I can't use Heimdall?
If we want to relock later, we can just flash a stock bootloader?
I already have my system setup how I like it and would like to not have to overwrite it with Revision. Will CASUAL work anyways as long as I have the dependencies?
Thanks so much Adam and Team!
:good:
awesome!
Thank you everyone involved!
I'm assuming that when running AT&T firmware/international firmware it won't recognize our VZW SIM correct? Awesome work though! Super excited about this.
I just wanna thank all of you for Guinea pigging this (so to speak). I'm gonna wait for droidstyles broke down step by step before i do this. Its probably not as bad as I'm making it out to be but I error to the side of caution.
Has anybody actually done this with no problem yet??
This guy is the f*ckin' man!!!
Thanks to everybody involved! Cant wait, I might just leave work now
Sent from my SCH-I605 using xda app-developers app

[SPH-L720] CF-Auto-Root

Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-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.
Donate
CF-Root has been available for many devices (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus, Galaxy S3, and many more) and has clocked over 13 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Why isn't this just called CF-Root
The traditional CF-Root's included a custom recovery (CWM, TWRP, etc) and were meant for devices that had a single kernel/recovery combination. CF-Auto-Root doesn't include a custom recovery and is meant for devices that have kernel and recovery separate (so you can manually install any custom recovery you wish). The Auto part comes from the fact that a large part of the process is automated (though it constantly needs adjusting)
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/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
ODIN Installation (detailed)
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 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, pull the battery, 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!
You may now optionally want to install and run Triangle Away to reset the flash counter.
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download
SPH-L720: CF-Auto-Root-jfltespr-jfltespr-sphl720.zip
Other models
International Samsung Exynos GT-I9500: http://forum.xda-developers.com/showthread.php?t=2292615
International Qualcomm Snapdragon GT-I9505: http://forum.xda-developers.com/showthread.php?t=2219803
Canadian: http://forum.xda-developers.com/showthread.php?t=2293800
T-Mobile: http://forum.xda-developers.com/showthread.php?t=2294005
AT&T: Bootloader locked, do not use CF-Auto-Root on it
VZW: Bootloader locked, do not use CF-Auto-Root on it
History
2013.05.20: SuperSU v1.30
You sir rock. Already rooted my device but this will just make things even easier for friends down the road. Thank you
So going to used this. Getting my s4 this Friday.
SPH-L710_ TW.MOAR!
awesome thanks =)
I'll have a video on this very soon, thank you Chainfire!
UPDATE: How To VIDEO can be found HERE!
How do I get recovery, I'm rooted.
mapcom1 said:
How do I get recovery, I'm rooted.
Click to expand...
Click to collapse
Better served in the QA thread but here you go.
http://forum.xda-developers.com/showthread.php?p=40860694
Sent from my SPH-L720 using xda premium
Thank you for this Chainfire. This will save a ton of aggravation and headaches for many folks going forward.
Under 1 minute...Awesome work! Since it is stock root this would be odexed?
tkgadgetman said:
Under 1 minute...Awesome work! Since it is stock root this would be odexed?
Click to expand...
Click to collapse
Correct
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
Simply Awesome!
Muchas Gracias!!
I tried every root method available and none of them worked with the MDL update I tried this one last night and it worked flawlessly the first time I used it.... It was done in less than 30 seconds... Awesome job man now I need a red theme
Sent from my SPH-L720 using xda premium
You're the man Chainfire! I had a stock, fully OTA updated phone. Your CF-Auto-Root worked perfectly.
Note: It sort of hung and did not reboot the first time. I clicked the reset button in Odin and did it again, worked fine the second time. Took like 15 seconds.
If anyone has an issue using this even if on MDL you can also install a custom recovery through Odin and reboot immediately to recovery and install a ROM/kernel combination. Much easier method this way though to be honest IMO. Good going, CF
Sent from my SPH-L720 using Tapatalk 2
Any help on doing this for Mac?
So I followed the steps to the T and my phone gets root access, checked it with root checker. But then when I activate Titanium it says that it does not have root access and I go back to root checker and even that fails.....I'm fully updated with OTA on stock. Any suggestions?
{
"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"
}
5-25-13 3:20pm EST- lol........Ok....so it now works without a problem. I did a factory reset, cleared the cache. Fired up Odin re-did everything without Auto Reboot and.....it hung but I restarted the phone with the power button and now....I have full root with updated MDL and OTA.
Works 100%
Thanks CF! Got the S4 on Friday...told myself would wait a couple of weeks before messing with it. But...rooted stock isn't really messing with it! Thanks for the easy, FAST, root!
worked great! thanks chainfire, my sprint ota update took away my root this fixed it in a few seconds

How To Root TMO S5 on Latest NK2 or NH5 Firmware..Keep Knox @ 0x0.*UPDATED 11-29*.

Here is a way to gain root if you all ready have the latest NH5 or NK2 firmware on your phone.. This way you dont have to revert back to an older complete firmware. This method also does not wipe out any of setting or mods that you may have done before you decided to root, like ringtones, clock settings, alarm settings, notifications etc.... If you update to the latest firmware and you use wanam or xposed, You will have to re install the framework from xposed to get all you settings restored. Once you install the Xposed framework you will have to restart the phone, all the modules should be restored to the way it was before you did the update.....This method should not trip Knox.
Before you try this method, you should disable Lookout apk and go into settings-general-security and uncheck verify apps, also put a check on unknown sources, then under security policy updates, uncheck the update box, also make sure to uncheck send security reports. This should prevent any hang ups while trying to install super user apk and disabling knox hang.
After you get root and back on NH5 or NK2 you can go back and put those checks back only if you plan on using the Knox security stuff, but it is not necessary if you dont. It does not affect anything you do with your phone anyway. This is up to you to decide. HAPPY ROOTING.. LOL
Thanks goes to @iworkout for pointing it out, as i did not run into the hang under superuser install for i just automatically do this when i root a phone without thinking.
.
.
1. Download these files to your computer and unzip them.. (ATTENTION,,, These boot.tar are not the bootloader.tar that everyone thinks it is. These are just boot.img (Kernels) needed to root and return back to latest stock with root.)
A- NE6 Boot.Tar----- NE6 BOOT.ZIP<<<< This is the kernel to root with.
.
B- NH5 Boot.tar------ NH5 BOOT.ZIP <<<< Earlier firmware before NK2, you only need to use this if you want to stay on NH5 otherwise skip this one..
.
C- NK2 Boot.tar------ NK2 BOOT.ZIP <<<<< This is the latest TMO Firmware as of 11/10/2014​.
Download these files to your phone:
.
C- Download Towel Root from here ( TowelRoot ), and SuperSu ( from the Play Store) to your Phone.​.
2. Once you have the files unziped, Open up PC ODIN 3.09 which you can get here PC ODIN 3.09 .
.
3. Once you have opened up PC odin, click on AP and load the NE6 boot.tar.md5 file into the slot.
.
4. Put your phone into Download mode, By powering off the phone and holding the volume down and home button at the same time and press the power button, once you see the phone start to boot let go of the power button and you phone should go to download mode, Make sure you press the volume up button to enter download mode.
.
5. Connect the phone to the computer, Make sure the PC ODIN sees your phone, (If not make sure you have the latest drivers loaded.) Once PC odin sees your phone and you have the file loaded in the AP slot, you can go ahead and start the flash, this should only take about 30 seconds to complete and the phone should reboot. Once your phone reboots you should have NE6 Kernel loaded onto you phone. You shouldnt have any fc's ( as i did this and did not have any FC's).
.
6. Once your phone reboots click on Towel root and click on " Make it Rain". Your phone should now have root, You can close towel root,
.
7. Open up SuperSu and install the Binarys into your phone, Make sure you click Normal install and not CWM/TWRP. You then will be prompted to Disable knoxs, You click yes, (I clicked disable and have had no side effects.) You will have to reboot to make sure Super user takes effect. You can check to see if you have root by downloading root checker of your choice from the playstore.
7a, If you some reason you get an error saying the super user failed to install, Dont worry, just reboot your phone and and re run super su apk and you will see that it actually did install super user, you can verify by using root checker to verify. You do not need to restore your phone back to stock and start over.
.
8.Once you verified that you have root, You can now go back to step 3 and load the NH5 or NK2 Boot.tar.mds into the AP slot of Odin, and follow steps 4- 5. That is it. You now should be back on the latest NH5 or NK2 kernel and have root. You can check by usng root checker and to see if all your info, you can download Samsung Phone Info from the playstore, and this will show you all the files and knoxs should be 0x0.
.
Here is the full T-Mobile Stock NK2 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NK2 Rom 11/10/2014​.
Here is the full T-Mobile Stock NH5 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NH5 Rom​.
If you are having issues with odin failing, I would try a different cable, one that is not usb 3.0. I have read on the forums that some people have been having issues with odin failing due to the new usb 3.0 cable that samsung has issued with the Galaxy S5. Most people are using computers that are not able to support 3.0 usb, and this may be an issue for some with odin. This is just an idea so it may or may not work for you. If it still fails i would try a different usb, maybe one on that is on the back of a desktop instead of one in front, and maybe a different computer all together..
.
.
I only use a windows (Currently using Window 7) / linux pc to do most of my work on android. So i know this method and odin works. It seems that some users are having issues with mac and odin, so be carefull. Personally if you plan on working on android you should purchase a cheap windows pc or laptop. Plus you can dual boot a win pc to do linux as well. Linux is what i use to do alot of my cooking of roms with. So if you are using an apple product to do your flashing, than unfortunatly I can not help you with that.. Sorry.
​.
Now remember that I am not responsible if you void your warranty or if you break your phone. This method worked for me and i found it easier and quicker this way. If something did not work then you did something wrong or did not read the instruction correctly.
.
If this method helped you in any way please hit the thanks button .. If the Mods would like to make this a sticky, please do. Thanks
Can anyone confirm that this works
{
"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"
}
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
iworkout said:
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
Click to expand...
Click to collapse
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
galaxyuser88 said:
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
Click to expand...
Click to collapse
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
iworkout said:
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
Click to expand...
Click to collapse
Yeah i didnt have that issue, as soon as i got the phone i disabled that lookout crap. Also already had the security check also disabled, as when you install apks from outside the playstore, you are told to disable the security checks.
I will have to add that to the op when i get home and at my laptop.
It works
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Works!
​
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
AndreTheShadow said:
​
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
Click to expand...
Click to collapse
Yeah that is something with superuser and not the method. Maybe when they upgrade the supersu apk, it may correct that. But good to see that this helped out to acheive root for ya.
Thx worked like a charm. SuperSu did hang when i tried to disable knox. I just rebooted and used SuperSu again and it disabled with no problems. Now if someone could just point me to the volume boost hack I will be good. I cant find it for the life of me.
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Hypoxic1 said:
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Click to expand...
Click to collapse
Iam not sure what will not work if disable knox. I dont use anything that might need knox, so i can not help you there. I have had no negative affect from disabling knox.
You can always try it and see what happens. The worst thing you will have to do is odin back to stock and try again. This is how i found disabling knox did not affect my phone or the apks i use in anyway. Yes you can choose not to disable knox and you will still have root.
As far as upgrading, you can do it 2 ways.
1. Odin back to stock and take the upgrade. But be warned that if you take a stock update, you may lose the ability to root, if the update closes the holes.
2. You can wait for one of the great devs to take the update and clean it and post it in xda. This is the safer bet.
Thank you for the quick & informative response! I really do appreciate your time.
Hmm, I took the plunge & CAREFULLY read, re-read, re-read again to be sure of the instructions. It keeps giving me a fail now. When I click START in ODIN, it's like it doesn't wait for the phone to do it & gives me the fail. When looking at the phone, I can see the line/bar thing drawing from left to right & before it is finished "drawing" that line, ODIN gives me the fail. Great...
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Hypoxic1 said:
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Click to expand...
Click to collapse
Ok why did you go back to ne6? If you all ready were on nh5, than my methods works perfectly, except for a hiccup in su. Seems like you did something wrong. I would load the full factory stock nh5 rom thru odin and try my method again. This only works on a full nh5 stock rom. If you were on some other firmware(older) then trying to upgrade to nh5 with my file will not work. It is only the kernel and not the whole rom. Hence the title.
If pc odins fails before you start, then it sound like the drivers are not loaded correctly, or one of the files you downloaded is corupt. Check to make sure the md5 matches and or redownload the files again, and try to use chrome to download. Afh seems to have issues with other explorers. Dont ask cause i do not have a clue as to why. Also if you continue to have issue, i would try a different usb port, different cable and or a different pc.
I know this method works. For i have done it about 20 times, i like to flash stuff on my phone to see what works.
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Hypoxic1 said:
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Click to expand...
Click to collapse
If you are afraid to use my method, then purchase mobile odin pro and use that to upgrade to nh5. Read the thread were you got the full ne6 and follow his directions. I honestly can not understand what the issue is that you are having. Cause like i said before, I have done a full odin back to nh5 and used my method with no issues. My phone also came with NH5 from tmo. Sorry.
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Hypoxic1 said:
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Click to expand...
Click to collapse
That is why i figured out my method, too many steps with the other thread. I orignally did it his way many times on my phone and it does work, just alot of steps and it takes alot longer to flash and root and then flash again.. The problem with mobile odin pro is it doesnt flash all the files that a stock rom has in it, this is why you need to flash some files with pc odin and then the rest with mobile odin pro..

Categories

Resources