[Q] Gnex and odin? plus other stuff =] - Samsung Galaxy Nexus

Hi guys,
Im sure that most of these questions will have been answered in the past but i would like to get a collective answer to some questions instead of looking at fragmented pieces here and there.
I have come to a Gnex from a galaxy s i9000.
Im not shy about flashing my phones at all. I flashed every single rom under the sun onto my galaxy s using pretty much every method and knew everything about everything with that phone.
Using a Gnex and thinking about flashing my phone i just want to clear some things up...
1) If i use the Gnex toolkit am i right in thinking that after i have unlocked my bootloader and rooted and flashed CWM that i have to rename the recovery to get into CWM? Otherwise i will have Andy with the red triangle and !?
2) If i want to flash back to pure 100% stock for future OTA updates can this be done straight from the Gnex toolkit? I used to just get a stock rom from samfirmware.com and slap it into odin and flash it onto my phone with repartition.
3) Can Odin be used with the Gnex and if so where do you get the .tar files and pit file etc from?
4) Im pretty sure that ive seen something about an odin mode? Soooo if Odin CAN be used do you use odin mode or download mode or are these the same thing and people are just calling it odin mode when its infact download mode?
Thats the 4 main ones i have right now.
Thanks for help given in advance.

Don't use toolkits.
Be a big boy and root it yourself. Link is stickied above...or in my sig.
You'll want the SDK set up in the event that you brick your phone.
And not knowing if you're device SHOULD be connecting but isn't is a huge troubleshooting barrier that you'll easily overcome by knowing ADB/Fastboot ARE working. Which you'll know after doing it manually.
The ODIN files can be found in the GNex general section. Stickied.
And download mode/odin mode are the same, yes.

Jubakuba said:
[snip]
You'll want the SDK set up in the event that you brick your phone.
Click to expand...
Click to collapse
Why would you recommend that he install the SDK? Unless he's a developer, there is no reason to install it. It's just a huge waste of space on your hard drive. Once he installs the Samsung driver, there are only 4 files that are needed if you are running Windows (only 2 if you are running linux or MacOS):
AdbWinUsbApi.dll
AdbWinApi.dll
adb.exe
fastboot.exe
And they are available in the first post of almost every toolkit or manual step-by-step thread there is.
Makes much more sense to have ~4MB worth of files on your PC rather than gigs, no?

efrant said:
Why would you recommend that he install the SDK? Unless he's a developer, there is no reason to install it. It's just a huge waste of space on your hard drive. Once he installs the Samsung driver, there are only 4 files that are needed if you are running Windows (only 2 if you are running linux or MacOS):
AdbWinUsbApi.dll
AdbWinApi.dll
adb.exe
fastboot.exe
And they are available in the first post of almost every toolkit or manual step-by-step thread there is.
Makes much more sense to have ~4MB worth of files on your PC rather than gigs, no?
Click to expand...
Click to collapse
SDK is 75MB on my system:what:
Sent from my Galaxy Nexus

bwcorvus said:
SDK is 75MB on my system:what:
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess you didn't install the full SDK. I guess 75MB is no problem then (but 4MB is better ).

Odin isn't really used with nexus. Use fastboot.

RogerPodacter said:
Odin isn't really used with nexus. Use fastboot.
Click to expand...
Click to collapse
Can you talk me through fastboot? Thats a new thing to me.
Cheers

Use my sig man.
It'll get you familiar with fastboot.
And ODIN can be used with our phones as well.
But fastboot is what's used to flash custom recovery.img's and such.
You can also return to stock with fastboot...using googles .img files.

Jubakuba said:
Use my sig man.
It'll get you familiar with fastboot.
And ODIN can be used with our phones as well.
But fastboot is what's used to flash custom recovery.img's and such.
You can also return to stock with fastboot...using googles .img files.
Click to expand...
Click to collapse
Oh ok i get ya. I just looked at the link in your sig.
So fastboot.exe is pretty much like adb.exe or an extension of.
I know my way around ADB pretty well so that looks to be pretty simple.
Nice tutorial BTW.
Thanks dude.

Related

Rooting with Heimdall

I've been searching for a guide that shows how to root the e4gt using Heimdall in linux. I can't find anything specific and I'm definitely not familiar with the way these things are rooted/flashed. I flashed my Evo like every 2-3 weeks. I also rooted through adb, but this is greek to me. Can someone point me in the right direction please? I have tried odin through virtualbox in Ubuntu but I am not having any luck. Thanks in advance.
Sent from my SPH-D710 using xda premium
From my understanding, you can flash just like Odin, but being more specific. You can flash a kernel to the kernel, modem to modem, etc.
Here is Heimdall with some basic instructions. v 1.3.0 has a graphical interface.
Download the pit file from the E4GT forum, and the rooted kernel you want, in a .tar format.
As I posted in another thread: To flash the kernel, click on the "flash" tab. Click "browse" for the proper PIT file and select the E4GT PIT file. Click "Add". Under "Partition Name" select "Kernel" then browse. Select the .tar file of the kernel you want to flash. Put your phone into download mode, attach, then click "start" when everything's ready.
I haven't done it to the E4GT yet, so I have no idea if it will work and claim no responsibility if you brick your phone. Personally, I'm too timid to try right now.
ODIN flashable files are all tarballs even if their extension isn't .tar. Extract them using 'tar -xvf filename'. The files inside are named for what they are with the exception of the kernel, which is called zImage.
Installing Heimdall varies by Linux distro, so install it according to your distro's instructions. I use Arch and it's in the AUR so I just used yaourt to install version 1.3.
Screw the UI, go commando line and type 'heimdall'. It will print out its usage. You can pretty much figure out what options to use based on the filenames that extracted from your tarball.
Put your phone into download mode (power all the way off, wait a sec, then hold Volume Down, the Home button on the front, and Power, then Volume Up when you get the warning screen). I haven't taken the time to figure out why, but sometimes I don't have to hold the Home button and sometimes I do. May have something to do with what ROM I was running at the time?
Attach the phone to the USB cable attached to your bad-ass Linux machine. Type 'heimdall detect'. If it tells you 'Detected' and doesn't error out, you're good to flash. If you're paranoid, do it a second time. If it errors, get thee to googlin'.
Next type 'heimdall flash --kernel zImage' and it will flash that kernel to your phone and it will reboot. If there are more files than just zImage, use the appropriate options. I read somewhere that it is recommended to use every file in the tarball--don't skip any unless you're very sure what you're doing.
Note: You need super-user privileges to run these commands so either su to root or use sudo.
It really is all that easy! And I can confirm that Heimdall v1.3 works with my ET4G. I've used it to flash the Zedo, Shabby and Stock kernels from two different Arch Linux machines.
And you hardly ever need the PIT file to flash. The only time you ever need it is if you're repartitioning.
Oh, and I am just sharing my procedures here--not telling you to do them--so I am not responsible in any way|shape|form for whatever you do to your phone.
Heimdall flash via b1g.p0ppa's instructions a success. Flash via the GUI a no go. Thanks dude!
b1g.p0ppa said:
ODIN flashable files are all tarballs even if their extension isn't .tar. Extract them using 'tar -xvf filename'. The files inside are named for what they are with the exception of the kernel, which is called zImage.
Installing Heimdall varies by Linux distro, so install it according to your distro's instructions. I use Arch and it's in the AUR so I just used yaourt to install version 1.3.
Screw the UI, go commando line and type 'heimdall'. It will print out its usage. You can pretty much figure out what options to use based on the filenames that extracted from your tarball.
Put your phone into download mode (power all the way off, wait a sec, then hold Volume Down, the Home button on the front, and Power, then Volume Up when you get the warning screen). I haven't taken the time to figure out why, but sometimes I don't have to hold the Home button and sometimes I do. May have something to do with what ROM I was running at the time?
Attach the phone to the USB cable attached to your bad-ass Linux machine. Type 'heimdall detect'. If it tells you 'Detected' and doesn't error out, you're good to flash. If you're paranoid, do it a second time. If it errors, get thee to googlin'.
Next type 'heimdall flash --kernel zImage' and it will flash that kernel to your phone and it will reboot. If there are more files than just zImage, use the appropriate options. I read somewhere that it is recommended to use every file in the tarball--don't skip any unless you're very sure what you're doing.
Note: You need super-user privileges to run these commands so either su to root or use sudo.
It really is all that easy! And I can confirm that Heimdall v1.3 works with my ET4G. I've used it to flash the Zedo, Shabby and Stock kernels from two different Arch Linux machines.
And you hardly ever need the PIT file to flash. The only time you ever need it is if you're repartitioning.
Oh, and I am just sharing my procedures here--not telling you to do them--so I am not responsible in any way|shape|form for whatever you do to your phone.
Click to expand...
Click to collapse
That is exactly what I was looking for. Just to make sure that I understand you correctly, by flashing the kernel as you instructed above that will root my phone? If that's the case that is very simple. Thank you very much. I'm running Ubuntu 11.04 btw which I was able to get a .deb for Heimdall.
Sent from my SPH-D710 using xda premium
Yep. A long as you make sure to download a pre-rooted kernel it will.
If you haven't flashed anything at all yet, have you experienced the loss of signal problem that people are reporting? They're asking people to share their experiences in one of the other threads.
Sent from my SPH-D710 using XDA App
b1g.p0ppa said:
Yep. A long as you make sure to download a pre-rooted kernel it will.
If you haven't flashed anything at all yet, have you experienced the loss of signal problem that people are reporting? They're asking people to share their experiences in one of the other threads.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Wow that is so much easier than my Evo ever was. To answer your question, no I haven't had any of the LOS problems yet. Hopefully I never do lol. That's one of the things that has me concerned about rooting right now. Now that I know how to do it I might just wait for a few more roms to come out. I'm really curious to see how CM does on this phone. Thanks again for your help.
Sent from my SPH-D710 using xda premium

[HOWTO] ROOT [KERNEL] SGH-T989 UVKID // Insecure // Root // Busybox

SGH-T989 UVKID // Insecure // Root // Busybox
What does all this mean?
As many of you know, we can already root our phone's but if you want to bypass all the extra steps ClockworkMod brings with it, I've got a kernel and an easier method just for you.
Features
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Code:
/sbin/*
/sbin/userscript.sh //runs the script that installs root
/sbin/su //the superuser binary we all know and love
/sbin/superuser.apk //a neat little app to manage all your root permissions
/sbin/busybox //the busybox binary we all know and love, that keep developers happy
Once you flash this you will have a fully rooted T-Mobile Galaxy S II, that also carries the benefits of an insecure kernel.
Why should you root your SGSII?
There a whole bunch of reasons a person would want to root there brand new SGSII. Any and all of the root applications in the market, some of the best apps at that, require you to root your phone.
By rooting your phone you also gain access to flash roms and themes that are popping up around the Android Development forum, by flashing ClockworkMod Recovery with Rom Manager.
What is better about this root method compared to Slayher's original method?
Since the root is maintained mostly inside of the kernel, removing root is as easy as flashing the stock kernel I posted and uninstalling the Superuser app.
Downloads
You can reference the second post on how to flash the kernel itself, but you can grab it from here now.
If you like my work..
and wish to donate you can buy me my very own T-Mobile Samsung Galaxy S II by using the details posted here.
How to Flash
We are going to be using Odin in this explanation to flash the stock kernel to your phone.
Downloads
First you are going to want to start by downloading all the needed files onto your computer and then place them onto your Desktop.
Samsung Kies
Odin3-v1.85.zip
SGH-T989-UVKID-Insecure-Root.tar
Process
Once you have everything downloaded and on your desktop, you are going to want to first install kies.
After this is done you should restart your computer for proper driver installation.
Next, extract Odin to a new folder on your Desktop. Leave the tar in the form it is.
Now, open up Odin by double clicking the .exe in the folder you extracted it to.
The most important step is now, you need to put your device into Download/ODIN mode so your computer will recognize it and be able to flash to it. To do this simply turn your phone off completely (or pull the battery). Then you are going to want to use the following button combination to force your device into download mode:
Hold the volume up/down and power button all at the same time.
Click to expand...
Click to collapse
Now ODIN should have recognized your device ( it may take a while for the drivers to complete installation so don't panic the first time).
Lastly, we want to click on the PDA button and then search for the SGH-T989-UVKID-Insecure-Root.tar we download earlier and placed on the Desktop.
If all of the above has taken place you are free to hit the Start button.
Done!
If all has gone well at this point the flash should be proven successful and your phone should reboot like normal.
If so, please feel pressured to give yourself a pat on the back, that was tough!
You da man!
Sent from my SGH-T989 using Tapatalk
So im guessing this supports init.d?
Sent from my SGH-T989 using xda premium
bubby323 said:
How to Flash
We are going to be using Odin in this explanation to flash the stock kernel to your phone.
Downloads
First you are going to want to start by downloading all the needed files onto your computer and then place them onto your Desktop.
Samsung Kies
Odin3-v1.85.zip
SGH-T989-UVKID-Insecure-Root.tar
Process
Once you have everything downloaded and on your desktop, you are going to want to first install kies.
After this is done you should restart your computer for proper driver installation.
Next, extract Odin to a new folder on your Desktop. Leave the tar in the form it is.
Now, open up Odin by double clicking the .exe in the folder you extracted it to.
The most important step is now, you need to put your device into Download/ODIN mode so your computer will recognize it and be able to flash to it. To do this simply turn your phone off completely (or pull the battery). Then you are going to want to use the following button combination to force your device into download mode:
Now ODIN should have recognized your device ( it may take a while for the drivers to complete installation so don't panic the first time).
Lastly, we want to click on the PDA button and then search for the SGH-T989-UVKID-Insecure-Root.tar we download earlier and placed on the Desktop.
If all of the above has taken place you are free to hit the Start button.
Done!
If all has gone well at this point the flash should be proven successful and your phone should reboot like normal.
If so, please feel pressured to give yourself a pat on the back, that was tough!
Click to expand...
Click to collapse
I am already rooted, can I still Odin this on top.
sebmw said:
I am already rooted, can I still Odin this on top.
Click to expand...
Click to collapse
Yes, it won't hurt anything.
Sent from my SGH-T989 using xda premium
Thanks so much! Just flashed this with odin and went without a problem!
Sent from my SGH-T989 using xda premium
I'm planning on picking up my Galaxy S2 from Telus once it gets released (end of the week I've heard). Will this method work on the Telus version?
I noticed the original 784MB I had dropped to 778MB after flashing is this normal.
TY
Rooting this way is ridiculously easy, especially for those of us who don't want to muck about with a custom CWR or custom ROM just yet. Basically, all I wanted to do was to have Titanium Backup running and to delete that annoying tethering manager app!
You might want to clarify that you press both Vol+ and Vol- simultaneously then plug in the USB. The other way you mention (Vol+, Vol-, Power) puts the device into recovery not download mode.
Kudos!
kennyp987 said:
So im guessing this supports init.d?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes it does.
marleyfan61 said:
I'm planning on picking up my Galaxy S2 from Telus once it gets released (end of the week I've heard). Will this method work on the Telus version?
Click to expand...
Click to collapse
No, once I am able to work with those on Telus to figure certain things out I will also develop there, do not flash anything from this forum though.
sebmw said:
I noticed the original 784MB I had dropped to 778MB after flashing is this normal.
Click to expand...
Click to collapse
Yes, you should notice that the Superuser application is installed upon flashing and a few root binaries are copied over to /system/bin so the drop in size is due to that, and actually occurs with any root method, not just this.
bubby323 said:
No, once I am able to work with those on Telus to figure certain things out I will also develop there, do not flash anything from this forum though.
Click to expand...
Click to collapse
What kind of things would you be needing for the Telus version? I am going to the store as soon as it opens to get it
Sent from my Milestone using xda premium
How will the coming update for wifi calling effect this flash? Should I wait til after that update?
Sent from my SGH-T989 using XDA App
I have a the telus version in hand, what do you need from it. I'm no dev but am happy to follow directions.
Sent from my Xoom using xda premium
If this kernel is insecure how can we expect it to perform any of its tasks confidently?
Thanks for the info but fyi the download link for Odin is broken.
Edit: looks like its the inspiringandroid page that is down. Does anyone have a mirror somewhere?
I came here to ask the same thing as above. Is there a mirror somewhere? Thanks in advance!
I am having the same problem as others. The SGH-T989-UVKID-Insecure-Root.tar link is down. Anyone have an alternate source for this file?

[ODIN][ROM][ICL53F][FACTORY] Full Factory ODIN restore 4.0.2 with radios - unrooted

Full factory restore ODIN with radios (both LTE and CDMA), kernel and recovery. This will bring you back to the current unrooted 4.0.2 release of Android for the Galaxy Nexus.
*** WARNINGS AND NOTICES ***
** Flashing this will wipe ALL userdata and your sdcard partition!! Make a BACKUP AND COPY IT OFF OF YOUR PHONE!!!
** It will bring your device back to stock running Android 4.0.2 Build ICL53F with EK05 CDMA and EK02 LTE radios.
** It WILL NOT relock the boot loader. You must relock your bootloader after flashing this ODIN to be 100% factory
Instructions:
1. This assumes that you already have the Samsung driver installed, the phone is unplugged from the computer and turned off.
2. Download the 7zip file and Odin3.
3. Open Odin3
4. Connect the phone to the computer
5. Enter download mode (hold the vol down key and press power). Odin3 should now see the phone.
6. In Odin3 click 'PDA' and select the PDA ODIN file from the archive
7. In Odin3 click 'PHONE' and select the PHONE ODIN file from the archive
8. Click Start! After it is completed the phone will reboot. The Odin3 screen should look like at attached screen.
File: VzW-SCHi515-FactoryODIN-ICL53F-4.0.2.7z
Link: http://bit.ly/zEVmoP
md5 : b94776ca0102f8be02ccea90dcaaf271
Size: 158 MB
File: Odin3_v1.3.exe
Link: http://bit.ly/wcTDuO
md5 : a93c47f0589153249f453375be7d8643
Size: 406 KB
Inside the 7zip file:
File: VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar
md5 : 6ff33e5b0d6b2da1c13824e0d90e97d9
File: VzW-PHONE-ODIN-SCH-I515.EK02_LTE.tar
md5 : b8d16828a1b777e4938834cba9e8f601
thank you for this!
---------- Post added at 11:08 PM ---------- Previous post was at 11:07 PM ----------
also is there a mac version of odin?
I'm pretty sure odin is Windows only. You could probably find it in a wine wrapper which will trick it into thinking it's running on a Windows machine.http://androidforums.com/samsung-galaxy-s2-international/403407-odin-mac-download.html
drivers
housry23 said:
I'm pretty sure odin is Windows only. You could probably find it in a wine wrapper which will trick it into thinking it's running on a Windows machine.http://androidforums.com/samsung-galaxy-s2-international/403407-odin-mac-download.html
Click to expand...
Click to collapse
What about my mac recognizing the phone??? How do I get drivers or where do I get them??? The Odin screen works just fine....
I don't have a Mac. I don't know buddy. I wish I could help. I do know that there is a program for Mac and Linux that works just like Odin and uses the same files to restore, flash or upgrade your phone. It's called Heimdall. I don't know much about it, so Google will be your friend for more info.
bryannh said:
thank you for this!
---------- Post added at 11:08 PM ---------- Previous post was at 11:07 PM ----------
also is there a mac version of odin?
Click to expand...
Click to collapse
housry23 said:
I'm pretty sure odin is Windows only. You could probably find it in a wine wrapper which will trick it into thinking it's running on a Windows machine.http://androidforums.com/samsung-galaxy-s2-international/403407-odin-mac-download.html
Click to expand...
Click to collapse
Don't waste your time, do this the easy way and just fastboot flash the factory images from Google (http://code.google.com/android/nexus/images.html). There is a flash-all script which will automatically flash each individual image for you.
Thanx for getting Odin files...best thing that has happened to galaxy nexus. I've used Odin before and it is a great tool in case you soft brick your phone.....but thank you once again....I will easily be able to put it back to stock if I need warranty replacement
Sent from my Galaxy Nexus using xda premium
Just to be clear, this will return *everything* to stock? Including recovery? (I know I have to relock the bootloader.)
My Nexus is randomly rebooting more and more since I got it last week, and I'm going to be exchanging it later today.
Thanks!
I thought we were using Odin3-v1.85 for the nexus. Also, am I reading this right that we do in fact use the "phone" button and not solely "pda". I have a fascinate and using phone would insta-brick.
wideopn11 said:
I thought we were using Odin3-v1.85 for the nexus. Also, am I reading this right that we do in fact use the "phone" button and not solely "pda". I have a fascinate and using phone would insta-brick.
Click to expand...
Click to collapse
I was thinking the same thing.....never use anything but the PDA button...but I did notice 2 zip files....the phone zip has sthe modem and radios I think
xaronax said:
Just to be clear, this will return *everything* to stock? Including recovery? (I know I have to relock the bootloader.)
Click to expand...
Click to collapse
This will take it back 100% stock (just make sure you lock the boot loader after). This will even wipe your sdcard partition.
wideopn11 said:
I thought we were using Odin3-v1.85 for the nexus. Also, am I reading this right that we do in fact use the "phone" button and not solely "pda". I have a fascinate and using phone would insta-brick.
Click to expand...
Click to collapse
I am sure it will work with v1.85, but I had the older version and used it just fine. As for the Phone vs PDA button, you use both on this flash. Make sure you use the correct file for each. The file for PHONE has phone in the name.
err... wtf ?
http://forum.xda-developers.com/showthread.php?t=1394051
Beat you to it by about... a month ?
Also, you probably should really use 1.85, on other devices older versions have caused bricks. Just saying.
Chainfire said:
err... wtf ?
http://forum.xda-developers.com/showthread.php?t=1394051
Beat you to it by about... a month ?
Also, you probably should really use 1.85, on other devices older versions have caused bricks. Just saying.
Click to expand...
Click to collapse
err... wtf what? So you released a stripped odin a month ago that isn't 100% factory and won't bring it back to 100% clean stock.
p.s. Love StickMount!
pentafive said:
err... wtf what? So you released a stripped odin a month ago that isn't 100% factory and won't bring the back to 100% clean stock.
p.s. Love StickMount!
Click to expand...
Click to collapse
So ok, now where's the GSM files?
Mawdo said:
So ok, now where's the GSM files?
Click to expand...
Click to collapse
Don't have them... Just LTE. Sorry!
Chainfire said:
Beat you to it by about... a month ?
Click to expand...
Click to collapse
Speaking from a user viewpoint, I'd wish this kind of stuff would be dealt with outside of a thread posting.
I saw the stripped-down version a while back, but I was more interested in a 'non stripped-down' version, which has been supplied here. Each version may serve differing needs and interests ... just my 2 cents. Its all about variety and choices, isn't it?!
Is this official from Samsung or user-created?
Nice job Penta
Thanks for this.
open1your1eyes0 said:
Is this official from Samsung or user-created?
Click to expand...
Click to collapse
Full Factory = not user-created

Root method for Macs?

I've already searched around, and it would seem there's currently no root method unless you have Windows. I'm already rooted, but I'd like to help my mom root hers and she's back in Philly. She actually put CM10 on her Touchpad all by herself lol.
My guess is that she may just have to wait, but if anyone could point me in the right direction that'd be great. Thank You
Sent from my SPH-L900 using Tapatalk 2
there is a way she can root it right now. she can go out and get herself a real computer!
I'm just kidding of course. what has to happen is for a dev (ie someone who knows what they are doing) that had a Mac to get involved. that's what has held up Mac root on every other device. which is kind of obvious I guess since you would need a Mac to make a root method for a Mac...
I'm not too used to Macs so I don't know if it's possible, but she could live boot her Mac onto a Linux distro, get wine, and do it the Windows way.
Sent from my SPH-L900 using xda app-developers app
Theoretically we could use Heimdall instead of Odin to flash the necessary bits. I am also without a windoz machine, so will hopefully find some time this weekend to try it out. I did see that Heimdall 4rc1 is supposed to support the sgn2. I'll post an update here if I find out any more.
Sent from my SPH-L900 using xda premium
Also, she could run a virtual windows over the Mac os. There's Apple boot camp and Parallel.
Sent from my SPH-L900 using xda premium
OK, here is what I figured out for getting root using Heimdall, which should work with Win, Mac, or Linux.
I found "How to Root and Install TWRP on Sprint Galaxy Note 2" where zedomax talks about rooting and in the video I heard mentioned Mac and Linux instructions and to go to http://galaxynote2root.com/ where I found examples of using Heimdall for Linux and Mac, though they are not specifically for the Sprint version.
So, what I did was get the latest Heimdall 1.4 Release Candidate 1 and compiled it on my Linux Mint desktop, though the precompiled 1.3.2 binaries found on the Heimdall home page should also work (get the Mac version here).
Instead of using the Sprint root method from galaxynote2root.com, I went with the CF-Auto-Root v1.0 compliments of chainfire.
Next I downloaded the Sprint SGN II CF-Auto-Root package from the bottom of http://autoroot.chainfire.eu/.
Then unzipped the file to get CF-Auto-Root-t0ltespr-sphl900.tar.md5 which I further extracted to get cache.img and recovery.img.
Then simply booted my phone into download mode (turn off phone, then hold VolDown+Home+Power to boot and when prompted press VolUp) and connected the phone to my computer and ran:
sudo heimdall flash --cache cache.img --recovery recovery.img
That's it! This will install SuperSU v0.96 and after rebooting I found the play store has an update to v0.97. This method also preserves the stock recovery, so I also installed TWRP 2.3.1.1 using the GooManager Android App Install Method.
Finally, I rebooted into recovery and did a full backup of the phone making sure to also backup the EFS partition as suggested here which has other useful information.
Hope this helps and isn't too confusing to follow.
Thanks for the info, but I'm either going to need something like the toolkit for Windows in a Mac environment or files & commands that can be pushed through terminal. Any updates on this?
Sent from my Galaxy Note II using Tapatalk
You only need two things. The mac version of heimdall and the cf-autoroot package for our phone. Then just flash the cache and recovery images from the terminal.
At that point you will have root and can also install TWRP for flashing other ROMs and things.
Sent from my phabtastic Galaxy Note II.

Another I think I'm bricked thread

I have looked through some of the threads on bricked phones and none have seemed to help. Right now all that shows up is Samsung. I found a video that said to get a file from samsung-update so I did. I used Odin to flash that and everything seems fine. This all started after I decided to try and go back to stock from liquid smooth. I just wasn't a fan of it and wanted to try tomorrow for a touchwiz rom. When I tried to flash back it didn't work so I thought if I used the tool kit to unroot it would put the original stock back. All it did was unroot. Any help? When I check my flash count it is around 4. If they check that at Sprint will I be able to have my phone fixed or will I just be SOL?
Hello shazo85,
If you can get to download mode (which it sounds like you can, seeing your flash counter), you can flash a stock ROM via Odin.
Try this thread and here download the package for your device.
http://forum.xda-developers.com/showthread.php?t=2017470
Kind of off topic but what is a flash counter and how do I check it lol?
Joe0113 said:
Kind of off topic but what is a flash counter and how do I check it lol?
Click to expand...
Click to collapse
Its shows if you have flashed a custom rom and another way for carriers to know if you have rooted your phone. So every time you flash a custom rom rom your phone counts it. But you can always reset the flash counter with triangle away.
Joe0113 said:
Kind of off topic but what is a flash counter and how do I check it lol?
Click to expand...
Click to collapse
It is exactly what it's called it counts the number of flashes you do lol you can see it by going into download mode(volume down +power) it will be in the top right corner.
Sent from my SPH-L710 using xda app-developers app
Overstew said:
Hello shazo85,
If you can get to download mode (which it sounds like you can, seeing your flash counter), you can flash a stock ROM via Odin.
Try this thread and here download the package for your device.
http://forum.xda-developers.com/showthread.php?t=2017470
Click to expand...
Click to collapse
The LJ7 with count reset for 32 didn't work. I'm trying the L13 right now. It seems to be doing something now.
That worked. I'm on 4.0.4, but I have a working phone.
shazo85 said:
The LJ7 with count reset for 32 didn't work. I'm trying the L13 right now. It seems to be doing something now.
That worked. I'm on 4.0.4, but I have a working phone.
Click to expand...
Click to collapse
Cool, now you can root and flash an updated rom so that you dont need to download the three OTAs again
Sent from my PG06100 using xda premium
CNexus said:
Cool, now you can root and flash an updated rom so that you dont need to download the three OTAs again
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
True however I'm the type of person that has to make sure I know what I'm doing to unroot also. So now that I'm rooted again I want to unroot and make sure I do it right. Then find a touchwiz rom that I like that is fully working.
shazo85 said:
True however I'm the type of person that has to make sure I know what I'm doing to unroot also. So now that I'm rooted again I want to unroot and make sure I do it right. Then find a touchwiz rom that I like that is fully working.
Click to expand...
Click to collapse
Ok, look for the "ODIN 1-clicks" thread, it takes you back to stock, stock recovery, and resets your flash counter in one
As for good touchwiz roms, I would recommend either MOAR (Mother of All ROMS) or TPR (the peoples rom)
You can find both in the "Android development" subforum"
CNexus said:
Ok, look for the "ODIN 1-clicks" thread, it takes you back to stock, stock recovery, and resets your flash counter in one
As for good touchwiz roms, I would recommend either MOAR (Mother of All ROMS) or TPR (the peoples rom)
You can find both in the "Android development" subforum"
Click to expand...
Click to collapse
I will check them out. I'm currently trying to use the toolkit that was posted to unroot. I'm sitting at the TWRP ADB Sideload screen now. All I have is a bar at the bottom and above it cancel. I'm guessing it is installing adb sideload filename.zip? Not sure how long this will take. I will look for the ODIN 1-clicks thread later. To help narrow it down any idea as to what forum it was posted in?
shazo85 said:
I will check them out. I'm currently trying to use the toolkit that was posted to unroot. I'm sitting at the TWRP ADB Sideload screen now. All I have is a bar at the bottom and above it cancel. I'm guessing it is installing adb sideload filename.zip? Not sure how long this will take. I will look for the ODIN 1-clicks thread later. To help narrow it down any idea as to what forum it was posted in?
Click to expand...
Click to collapse
I'll post the link here in a bit, just give me a second
For the most failsafe process I would recommend to go with ODIN if you wanna reset to stock
CNexus said:
I'll post the link here in a bit, just give me a second
For the most failsafe process I would recommend to go with ODIN if you wanna reset to stock
Click to expand...
Click to collapse
Thanks. TWRP seems to be taking a long time to install the files it needs to do the sideload. Nothing seems to have changed, but when I try to go further in the toolkit it just gives me an error that it can't find the device.
shazo85 said:
Thanks. TWRP seems to be taking a long time to install the files it needs to do the sideload. Nothing seems to have changed, but when I try to go further in the toolkit it just gives me an error that it can't find the device.
Click to expand...
Click to collapse
Hmm, dont know what to tell you, I've always just used ODIN to go back to stock
Anyway, heres the one clicks thread: http://forum.xda-developers.com/showthread.php?t=2017470
shazo85 said:
Thanks. TWRP seems to be taking a long time to install the files it needs to do the sideload. Nothing seems to have changed, but when I try to go further in the toolkit it just gives me an error that it can't find the device.
Click to expand...
Click to collapse
Just saw your other post in my thread and it sounds like you didnt do it correctly. Interested to see the output from the box on the one click, with that said load this onto your sdcard http://forum.xda-developers.com/showthread.php?t=1904099
then factory reset and flash in custom recovery
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
Also I just noticed your OP says you came from liquidsmooth. That is CM10.1 based. CM10.1 does not show the galaxy S3 screen when booting. Which tells me that u still have that kernel and a touchwiz based system. Whatever you did to return from liquidsmooth didnt flash a new kernel. You also have to wipe before switching back to a touchwiz rom like stock, my zip above is a fix for all that
billard412 said:
Just saw your other post in my thread and it sounds like you didnt do it correctly. Interested to see the output from the box on the one click, with that said load this onto your sdcard http://forum.xda-developers.com/showthread.php?t=1904099
then factory reset and flash in custom recovery
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
Also I just noticed your OP says you came from liquidsmooth. That is CM10.1 based. CM10.1 does not show the galaxy S3 screen when booting. Which tells me that u still have that kernel and a touchwiz based system. Whatever you did to return from liquidsmooth didnt flash a new kernel. You also have to wipe before switching back to a touchwiz rom like stock, my zip above is a fix for all that
Click to expand...
Click to collapse
Thanks, I will give that a shot. The link was posted above by someone. I didn't know that was the same one you were talking about. Seems like it isn't as easy to root, flash and even to unroot the S3 as it was the EVO 4G. I only had issues with some roms on that.
This is a samsung. Its easier than any HTC to unroot and go back to stock. Your just not used to it yet
billard412 said:
This is a samsung. Its easier than any HTC to unroot and go back to stock. Your just not used to it yet
Click to expand...
Click to collapse
Agreed. Samsung bootloader is unlocked by default. That means rooting is as simple as an Odin flash of a recovery. With HTC (locked bootloader), you had to use a program such as unrevoked to gain access to it. And each and every update HTC tried to re-lock the bootloader, so it was difficult to know if you should update (this is one reason why we get so many threads on here that say "how do I root with MB1?!?!?!").
As far as I'm aware, rooting with GS3 has been accomplished using the same method for quite a while.
Now, rooting using the Odin method is a bit more involved than it was with unrevoked, but really the only steps are clicking through a couple of files. The steps are stated clearly. It's just new and feels different. I was really wary of using Odin (still am, if I can be honest), but I was much more uncomfortable with unrevoked.
Samsungs seem harder because everybody and their mother has a tutorial on how to root it and nobody uses the most quick, clear cut 30-sec root possible, CF AUTO ROOT is easy and quick as hell, yet people treat it like the redheaded step child and ignore its presence. I dont get why
*Not lying when i say 30-sec either.
FInd me an easier method than that
billard412 said:
Samsungs seem harder because everybody and their mother has a tutorial on how to root it and nobody uses the most quick, clear cut 30-sec root possible, CF AUTO ROOT is easy and quick as hell, yet people treat it like the redheaded step child and ignore its presence. I dont get why
*Not lying when i say 30-sec either.
FInd me an easier method than that
Click to expand...
Click to collapse
More information on CF Auto-Root:
Website (look up d2spr in the big table).
XDA Thread. Has instructions and further clarifications.
I had honestly never heard of it before, but it seems like a good (and quick) option for getting root from stock.
Could be that I'm just not used to it. I only ever had to root the EVO if I was coming back from Sprint. If I remember right the unroot was just load up 2 zip files. Nice that this is just one to unroot. I will have to look into that CF Auto Root.
I too was one of those people looking for how to root MBI. I didn't know it was all the same. Chances are I would have never donated to the toolkit if I would have known. I also would have never used the toolkit. It would be nice if we had just one thread on rooting instead of 3 or 4 that we have. Might be less confusing that way.
EDIT: Forgot to say that the zip file for the unroot and counter reset did work. I had my phone back up and working just as I clocked in for work. All night I have had apps downloading.

Categories

Resources