This approach to customizing your phone involves the following steps:
1. Read the flash counter.
2. Root your phone:
- by using DooMLoRD's Easy Rooting Toolkit. (ZergRush Exploit)
- by using SuperOneClick Root. (ZergRush Exploit)
- by flashing Entropy512's Return/Unbrick to stock, Kernel + Rooted System Package using Odin or Heimdall.
3. Install a customized kernel containing ClockworkMod Recovery:
- by using Mobile Odin Lite or Mobile Odin Pro on your phone.
- by using adb on your computer.
- by using Android Terminal Emulator on your phone.
4. Flash the custom ROM package of your choice:
- by using ClockworkMod Recovery and a CWM flashable zip package.
- by using Mobile Odin.
PLEASE NOTE: While the following guide was written before AT&T officially released ICS, the principles contained in this guide are still applicable to our phone regardless of firmware version. However if your phone is currently running stock ICS UCLE5, using this method will install Gingerbread, taking your phone back to an earlier version. To root the phone while retaining ICS, please see the [Heimdall][Odin][Stock][Root]UCLE5 Stock ICS with Root thread.
JANUARY 2013 ROOTING UPDATE: In mid December of 2012, Samsung released an over-the-air update for the SGH-I777UCLK3, taking the operating system to version 4.0.4. Around the same time, XDA developer Chainfire released an application called ExynosAbuse APK which can be used to root the SGH-I777 with SuperSU, without the need to use a PC. ExynosAbuse APK is the best, and probably the only practical method for rooting UCLK3 without flashing some other distribution. In addition, it seems that this application is a good way to root any phone running 4.x operating systems, and possibly phones running 2.x operating systems as well. Be aware, there are possible risks involved with using this application. Please thoroughly read and understand Chainfire's thread linked above before using his application.
Discussion
The Samsung Galaxy S II contains an internal flash counter which is incremented each time a non-stock binary (kernel/rom) is flashed from a computer using Odin or Heimdall. (Using the new Mobile Odin on your phone does not increment the flash counter.) The purpose of the flash counter is believed to be to allow Samsung and or AT&T technicians to detect if the phone has a voided warranty through flashing non-stock firmware. The first time the flash counter is activated, the phone also displays a warning screen on boot up with a yellow warning triangle containing an exclamation point. The warning screen also contains the i9100 logo. (Evidently, Samsung did not change the warning screen from the International version of the Galaxy S II for the AT&T version.) Some rooting methods require that a non-stock kernel be flashed before rooting can be accomplished. So rooting and flashing custom software can both cause the dreaded yellow triangle, and increment the flash counter.
It is possible to remove the warning screen by two methods. One is by using a Jig to place the phone into download mode. The other is by flashing a stock kernel using either Odin or Heimdall. However, there is only one way to reset the flash counter, and that is with a micro usb Jig. This was true for the International version of the Galaxy S II as confirmed by Chainfire on the i9100 forums. This has also been confirmed for the AT&T Galaxy S II by dayv. Please see his post here, and then go to this post and read it and the following five posts for a complete description with screen shots.
pinoymutt adds:
On the newer versions of the i9100 ROMs apparently Samsung has updated the bootloaders to render the "jig trick" to reset the counter useless. This has also been observed in the latest ATT leak that DG posted in the General Forum (UCKJ2), where new bootloaders are included that render the jig reset obsolete.
Click to expand...
Click to collapse
Additionally, there have been rumors that there is a secondary counter hidden in the code of the Galaxy S II which increments each time the primary flash counter is reset to zero. This rumor was either started or strengthened over in the i9100 forums by Chainfire. He never did find any code, and later said he was not fully convinced there ever was any code. But the rumor has already had some discussion in these At&T forums, so it's worth mentioning. My opinion is that a secondary counter doesn't exist, but if it does, this would be an additional reason for this guide.
Some people may be reluctant to root their phone and/or flash custom software onto it, not wishing to take a chance on voiding their warranty. However, there is a way to completely avoid this problem. The solution is to never increment the flash counter in the first place, and never activate the yellow warning triangle. Using this guide to root and modify an AT&T Galaxy S II phone right out of the box, along with the ability to flash back to completely stock firmware followed by a wipe data/factory reset from stock 3e recovery, (see this Guide), will result in a phone that can be returned for warranty purposes to either AT&T or Samsung without fear of the warranty being denied.
Disclaimer: I didn't think all this stuff up. The following information is mainly gleaned from all the great developers and knowledgable users on this forum. A special thanks to Entropy512 for creating the stock + root package that makes this all possible.
Here is some additional information for noobs about the tools and techniques used in this guide.
1.) How to read the flash counter on an AT&T Samsung Galaxy S II
Boot into download mode by this method:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
At the top of the screen you will see:
ODIN MODE
PRODUCT NAME: SGH-I777
CUSTOM BINARY DOWNLOAD: NO --or-- YES (x counts)
CURRENT BINARY: SAMSUNG OFFICIAL --or-- CUSTOM
Once you have verified the information, remove the usb cable, and hold down the power button until the phone begins to reboot. (Do not do this if you are actually flashing the phone. Interrupting a flash can cause bad things to happen.)
You will not see the above information if you enter download mode by another method, ie. by using adb or the power menu, etc.
Now you can check on your flash counter at any stage of the foregoing guide.
To root UCKK6, use method 2c or 2d to flash UCKH7 stock plus root. Immediately after rooting, if you want UCKK6, open Settings and check for updates, download and install the OTA update, and it will retain root. Some have reported this works, and some say not. Alternatively, use Odin3 v1.85 to flash Entropy512's UCKK6 Stock plus Root package from his thread here.
Click to expand...
Click to collapse
2a.) How to root by using DooMLoRD's Easy Rooting Toolkit. (ZergRush Exploit) (Windows)
This rooting method does not work on the UCKK6.
This is the preferred method of rooting for users with the Windows operating system on their computer, and a phone running UCKH7.
Download the "DooMLoRD's Easy Rooting Toolkit v4.0" package from this thread and extract it to a directory on your hard drive using WinZip or a similar program.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
Both USB Debugging (Menu\Settings\Applications\Development) and Unknown Sources (Menu\Settings\Applications) should be enabled on your phone.
Increase the screen timeout on your phone to 10 minutes. (Menu\Settings\Display\Screen Timeout) Remember to set it back to a shorter interval after you are done rooting.
Connect the USB cable to the phone and the computer. Go to the directory where you extracted the package and execute "runme.bat".
The toolkit will open a command prompt window where you will see the progress of the rooting process. It takes between 5 and 10 minutes for the process to complete.
Success. You're rooted.
2b.) How to root by using SuperOneClick Root. (ZergRush Exploit) (Windows, Linux and Mac OS)
This rooting method does not work on the UCKK6.
Download "SuperOneClick v2.3.1 - Automatic Driver Installation" from DepositFiles (or look for links here) and extract it to a directory on your hard drive using WinZip or a similar program.
Please go the the SuperOneClick thread and read about the tool and how to use it. For Windows XP you need to have .NET Framework v2.0 or above installed. For Mac OS and certain flavors of Linux, you need to install Mono.
I have not tested this tool. It is included here because it claims to work for Mac OS and Linux, and provides a way to use the ZergRush Exploit on those operating systems. Since I am only familiar with Windows, I will be unable to support this rooting method. For problems, try posting questions in the SuperOneClick thread linked above.
If you try SuperOneClick on Linux or Mac, please post your (success or failure) results. Thanks.
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile | Dev-Host 268.64 MB.
Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
2d.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
Tested on Linux, should work on Mac OS
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here, or if you have difficulty with the links in his thread, there are alternative links for all his files in the Download Repository toward the bottom. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
Reboot the phone. Success. You're Rooted.
You must use a Gingerbread kernel when using this method. If you use an ICS kernel while your phone is running Gingerbread, it will not boot!!!
Click to expand...
Click to collapse
3a.) How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Mobile Odin Lite or Mobile Odin Pro
This is the preferred method to install a customized kernel onto your phone. In addition, Mobile Odin is a very useful tool that will allow you to install custom software directly on your phone without using a computer.
Mobile Odin Lite (free) can be downloaded and installed directly on your phone, or it can be downloaded to your computer and installed with adb. Alternatively, you can purchase Mobile Odin Pro for under $5.00 and install it directly from the market. It's easier, and you'll support the developer!
To use Mobile Odin Lite, download the file attached to the OP of this thread. You may need to be a registerd member of xda forums to download this file. Download directly on your phone, or to your computer and move or copy it to your phones sdcard. Using any file manager such as MyFiles or Root Explorer, select the file and install it. You can also install it from your computer using the following adb command:
Code:
adb install MobileODINLite-v2.30.apk
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel. There are several kernels available which can be found in the AT&T SGS II Android Development forum. You must use a Gingerbread kernel! Usually choose between the following two Gingerbread kernels: Entropy512's Daily Driver or Siyah 2.6.
Transfer the zImage to the root of your phone's internal or external sdcard, using a usb cable or another method such as dropbox.
On your phone, open the Mobile Odin program. If you installed Mobile Odin Lite, when it prompts you to install the add-in, click cancel. If you installed Mobile Odin Pro, you will have already downloaded and installed the add-in to activate all the features in the program. With Mobile Odin Lite, you will still be able to install the kernel.
In Mobile Odin, click on Kernel or Install Kernel, find and select the zImage on your internal or external SD card, and then click on Flash Firmware.
Mobile Odin will flash the kernel and then reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Market (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 version of ClockworkMod Recovery retains this button configuration but changes it to Power = select.
If you installed Mobile Odin Lite, and you don't want to keep it, you can uninstall it now. If you want to keep it and activate all its features, download the add-on MobileODIN_FlashKernel_I777-v1.0.apk from here and install it on your phone with adb using the instructions above.
3b.) How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from a pc, using Android Debug Bridge (Windows, Linux and Mac OS)
Download and install the Android Software Developer Kit (SDK) from here. You may need to run SDK Manager with administrator privledges.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel. There are several kernels available which can be found in the AT&T SGS II Android Development forum. You must use a Gingerbread kernel! Usually choose between the following two Gingerbread kernels: Entropy512's Daily Driver or Siyah 2.6.
Move or copy the zImage into the platform-tools directory (on older installations it is the tools directory) where adb.exe resides. This will be something like (on Windows) c:\android-sdk-windows\platform-tools.
On your phone, first enable USB Debugging (Menu\Settings\Applications\Development\USB Debugging) and then plug in your USB cable, connecting your phone to your computer.
Open a command prompt. Change directory to the tools directory, then enter the following at the command line:
Code:
adb push zImage /sdcard/zImage
adb shell
$ su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
# exit
$ exit
The dd command requires superuser permission on the phone represented by a # prompt. After you type su and hit enter, look for a superuser window on your phone and give the permission. If the permission request doesn't pop up, open superuser on your phone to force the phone to prompt for superuser permission. After approval, the adb session will be listed as Unknown in superuser.
After you've finished, the code in the Command prompt window will look something like this (your command prompt and some numbers will be different):
Code:
C:\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
4279 KB/s <4776784 bytes in 1.090s>
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
10153+1 records in
10153+1 records out
5198492 bytes transferred in 2.558 secs <2032248 bytes/sec>
# exit
exit
$ exit
exit
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Market (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 version of ClockworkMod Recovery retains this button configuration but changes it to Power = select.
3c.) How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Android Terminal Emulator
Download and Install Android Terminal Emulator onto your phone from the Market.
Download (onto your PC) the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel. There are several kernels available which can be found in the AT&T SGS II Android Development forum. You must use a Gingerbread kernel! Usually choose between the following two Gingerbread kernels: Entropy512's Daily Driver or Siyah 2.6.
Transfer the zImage to the root of your phone's sdcard, using a usb cable or another method such as dropbox.
On the phone, open a terminal session with Android Terminal Emulator.
A few points to be aware of:
Android is a version of linux so you are using linux commands. Linux commands are case sensitive, so you must for instance type "zImage" and not "zimage", if that is the way the file is spelled on the sd card.
Since this will be the first time you have used superuser.apk with the terminal, you may need to approve it on you phone. After that, superuser permission will be remembered.
When you first open a terminal session, you will be at the root of the phone, or essentially "/". The $ prompt means shell access, the # prompt means root file access.
You need a # prompt to complete this Step.
If your keyboard goes away, use the menu button options to get it back.
In the terminal session, type su and then enter. You will get a superuser request. Once you approve it, you will get the # prompt.
Then type the following:
Code:
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Press enter, wait till the zImage is copied over to the named block. (takes about 2 or 3 seconds)
To close the root session, type "exit" and enter. Use the back button to close Android Terminal Emulator.
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Market (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 version of ClockworkMod Recovery retains this button configuration but changes it to Power = select.
4.) Flash the ROM package of your choice using ClockworkMod Recovery and a CWM flashable zip package or Mobile Odin with any package
Your phone is now set up to flash custom software using ClockworkMod zipped install files in ClockworkMod Recovery. If you used and retained Mobile Odin, you can also flash custom software with it. Anything you flash on the phone using ClockworkMod Recovery, Mobile Odin, adb or terminal, will not affect the flash counter or invoke the warning triangle. Therefore, you can flash ROM's Kernels and Modems to your hearts content. Just avoid ever flashing anything containing a non-stock kernel with Odin or Heimdall from your computer. I would also caution against flashing any package with bootloaders. There is no valid reason to flash bootloaders on the SGH-I777 at this time, but some developers may include bootloaders in their CWM flashable zip files, or Odin flashable tar files.
Nice write-up. The info has been floating around on various threads and posts, but you did a great job putting all together into one nice step-by-step for folks looking to learn.
Hopefully it'll also cut down on the million of duplicate threads asking the same question!
---------- Post added at 05:02 PM ---------- Previous post was at 04:58 PM ----------
creepyncrawly said:
Discussion
It has been reported to be possible to remove the warning screen and reset the flash counter by two methods. One is by using a Jig to place the phone into download mode. The other is by flashing a stock kernel using either Odin or Heimdall. However, while it is confirmed that the jig will both remove the triangle and reset the counter, and that flashing a stock kernel with Odin or Heimdall will remove the warning triangle, it is not certain that flashing a stock kernel with Odin or Heimdall will actually reset the flash counter. The developer Chainfire on the i9100 forums says that on the International version of the Galaxy S II, it will not. This is yet to be confirmed or denied on the AT&T version of the phone, as far as I know.
Click to expand...
Click to collapse
On the newer versions of the i9100 ROMs apparently Samsung has updated the bootloaders to render the "jig trick" to reset the counter useless.
This has also been observed in the latest ATT leak that DG posted in the General Forum (UCKJ2), where new bootloaders are included that render the jig reset obsolete.
Great guide, lots of information in here! Thanks for preparing it.
Sent from my SAMSUNG-SGH-I777 using xda premium
I think this guide is sticky worthy.
Sent from my SAMSUNG-SGH-I777 using XDA App
Awesome guide, thank you for putting this all together in one place. Very helpful for a guy coming to Samsung from HTC.
+1 for sticky worthy!
Sent from my SAMSUNG-SGH-I777 using Tapatalk
THANKS! Helped me when I got stuck!
Sent from my SAMSUNG-SGH-I777 using xda premium
This is exactly what I needed.... yesterday (as you know)... my Search and Question buttons almost caught fire from over-use looking for all the pieces of the puzzle. I did the Entropy512 "Kernel + Rooted System Package via Odin3 v1.85.... extracted the zImage from Codeworkx's CWM Kernel, and pushed it to phone via adb push. I got hung up on the "permission" to write to the block, but finally got it solved. Creepyncrawly: you might want to add a bullet step to your OP#1 to open SuperUser app on phone just prior to the adb shell "su" command. When I did this, phone prompted for superuser permission... after acceptance, it is stored as "Unknown" in the superuser app list. Once this occurred, then I got the "#" prompt and could dd write to block to flash CWM.
Absolutely stellar post as it puts it all in one place. This will definitely help others who might stumble in adb as I did. Thanks again to all the forum members who posted helpful advice and links.
DAMN! My JIG just got here!
Thanks for the nice write up!
Great write up OP. however like the above poster my JIG just got here too and I just used it, and it was quick and painless.
Alucardis666 said:
Great write up OP. however like the above poster my JIG just got here too and I just used it, and it was quick and painless.
Click to expand...
Click to collapse
Jigs don't work in 2.3.5 so these methods will be extremely helpful for others
Sent from my SAMSUNG-SGH-I777 using xda premium
This post should be a sticky, or at least the sticky should link to this post.
arctia said:
This post should be a sticky, or at least the sticky should link to this post.
Click to expand...
Click to collapse
It's linked in the sticky FAQ thread. I'd rather not see too many sticky threads. That seems to me to be more confusing than helpful.
Great write up in easy steps tyo follow.
I have a question, on removing the yellow triangle. I rooted with Jivy26 easy root and was wondering can I reroot with Entropy512 to remove the yellow triangle or can I just do step 2a from link?
Would like to be able to return to stock if i need to send in for warranty. Also should we use CWM manager for backing up?
ElCamino said:
Great write up in easy steps tyo follow.
I have a question, on removing the yellow triangle. I rooted with Jivy26 easy root and was wondering can I reroot with Entropy512 to remove the yellow triangle or can I just do step 2a from link?
Would like to be able to return to stock if i need to send in for warranty. Also should we use CWM manager for backing up?
Click to expand...
Click to collapse
Follow the instructions from 2a on, and it will remove the triangle and you will maintain root.
Sent from my SAMSUNG-SGH-I777 using XDA App
Can you check to see if I understood correctly?
I flashed my kernel using Odin to get root , flashed the CWM file to get the recovery using Odin as well. You're saying that I can re-root the phone using your method, and the yellow triangle will disappear, as well as reset my counter?
Also, if I were to get a jig, it resets the counter? Or just removes the triangle?
Sent from my SGH-I777 using XDA App
Blaze9 said:
Can you check to see if I understood correctly?
I flashed my kernel using Odin to get root , flashed the CWM file to get the recovery using Odin as well. You're saying that I can re-root the phone using your method, and the yellow triangle will disappear, as well as reset my counter?
Also, if I were to get a jig, it resets the counter? Or just removes the triangle?
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
You should still be rooted, if I understand what you are saying. Root consists of /system/app/superuser.apk and /system/xbin/busybox. You can verify that you are rooted by looking for the superuser app in your app drawer. If it's not there, then you are not rooted.
If you flash Entropy512's stock + root package with Odin, you will clear the yellow triangle and be rooted, on full stock kernel and stock system image. Then follow the rest of the guide if you want to take it further. We believe flashing the stock kernel with Odin will both remove the warning triangle, and reset the counter, but read the discussion in the Guide, as it points out that over in the i9100 forum, they say flashing the stock kernel will clear the warning but not reset the counter.
The Jig will do both.
creepyncrawly said:
You should still be rooted, if I understand what you are saying. Root consists of /system/app/superuser.apk and /system/xbin/busybox. You can verify that you are rooted by looking for the superuser app in your app drawer. If it's not there, then you are not rooted.
If you flash Entropy512's stock + root package with Odin, you will clear the yellow triangle and be rooted, on full stock kernel and stock system image. Then follow the rest of the guide if you want to take it further. We believe flashing the stock kernel with Odin will both remove the warning triangle, and reset the counter, but read the discussion in the Guide, as it points out that over in the i9100 forum, they say flashing the stock kernel will clear the warning but not reset the counter.
The Jig will do both.
Click to expand...
Click to collapse
Thanks for clarifying that mate. I think Im going to order a jig then. Any "fake" ones I should know about?
Sent from my SGH-I777 using XDA App
Blaze9 said:
Thanks for clarifying that mate. I think Im going to order a jig then. Any "fake" ones I should know about?
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
I don't own a jig. I'm told that the SGS II has a closer tolerance for the 301K ohm value than the Captivate does, so some jigs that work with the Captivate won't work with the SGS II. I've read you can trust the jigs from Mobil Tech Videos, and the owner is quite active in the forums here, so that would be a safe and sensible choice.
but read the discussion in the Guide, as it points out that over in the i9100 forum, they say flashing the stock kernel will clear the warning but not reset the counter.
The Jig will do both.
Click to expand...
Click to collapse
This is correct, the counter that shows the number of times you have flashed a custom kernel does not get reset by flashing a stock kernel - just the warning triangle gets removed by flashing to stock.
And yes the download mode jig does both reset the counter number to "No" as well as remove the triangle.
I have tested with a jig from http://www.mobiletechvideos.com/blo...s-download-mode-jig-so-easy-a-baby-can-do-it/
Sent from my SAMSUNG-SGH-I777 using XDA App
Very awesome, wish there was a guide on how to reset current to default w/o a kernel change.
Related
There appear to be two main options for rooting Samsung devices on linux and mac.
Option 1: (un-tested) root.zip (recovery)
This method roots your stock 2.3 rom from in recovery (stock or CWM)
1. Copy Root.zip to your sdcard.
2. Turn your phone off
3. Boot your phone into recovery mode. (Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Select “apply update from sdcard”
5. Find and select Root.zip
6. When it’s done installing, select “reboot system now”
7. Go to apps and look for 'superuser'. If you see it, your phone is rooted.
Option 2: (un-tested) flash CWM from stock recovery:
This gives you the freedom of a custom recovery, flashed on the device from stock recovery
1. Download recovery-clockwork-5.0.2.6-galaxyace-fix.zip
2. Put recovery-clockwork-5.0.2.6-galaxyace-fix.zip on your sdcard
3. Boot into current stock (default) recovery (zip also compatible with CWM recovery)(Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Go to "apply update from sdcard"
5. Select "recovery-clockwork-5.0.2.6-galaxyace-fix.zip"
6. When it finishes, power off and boot back into recovery mode to check it has installed (it should say "ClockworkMod Recovery v5.0.2.6" somewhere)
Option 3 (un-confirmed): use Heimdall.
An open source, cross-platform, alternative to Odin.
Heimdall is officially supported on the Galaxy S (and S variants including Galaxy Tab)
It allows you to do pretty much anything Odin can do (interact with download mode), and so you can flash a root kernel to gain root and CWM recovery.
Although supposedly untested on the Galaxy Ace, heimdall should be able to flash the usual root precedure (rooting kernel with CWM).
It would be great if someone could verify heimdall works for the Galaxy Ace
Option 4: (un-tested) root your ROM using the zergRush exploit (from the Revolutionary team).
zergRush rooting scripts: Linux, Mac, Windows
For the zergRush exploit scripts, you only root your firmware, so CWM will need to be installed manually afterwards if you want it.
Now that you have root, you should be able to (optionally) flash CWM from an app or over adb using flash_image) (DO YOU NEED ROOT IF THIS IS DONE IN RECOVERY(STOCK)?)
Apps that can flash CWM include:
* CWM Manager
* Flash image GUI
_DO NOT USE_ ROM Manager (reported unstable)
To flash using ADB and flash_image, download flash_image and an CWM recovery img then run:
Code:
cd directory-containing-files/
adb remount
adb push flash_image /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
adb push recovery.img /sdcard/
adb shell
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
Or from the phone's terminal (if BusyBox is installed):
first put recovery.img & flash_image onto /sdcard/
Code:
cd directory-containing-files/
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /sdcard/flash_image /system/bin/flash_image
chmod 0755 /system/bin/flash_image
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
DISCLAIMER: I do not personally own a Samsung phone, and have not yet tested these methods (although I am interested to hear how well they work,and will do my best to update the post). I am however planning to root a friends Galaxy Ace and possibly also an Galaxy S2, so will be testing some of these soon (I'm not sure I should try the untested heimdall on a friends Ace though)
This seems almost utterly pointless, prove me wrong?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
+1... I don't understand the point.. Why take a longer way when the shorter way is faster, efficient and trustworthy...
ace_viknesh said:
Why take a longer way when the shorter way is faster, efficient and trustworthy...
Click to expand...
Click to collapse
Sorry, which way is this shorter more trustworthy way?
The point of this is listing the methods I believe to be compatible with linux (and by extension mac)
I am new to Samsung phones and do not possess one myself, but understand that using Odin is restricted to Windows.
I will be flashing CWM Recovery to a Galxacy Ace soon and will try methods that have been tested (friend's phone)
If you know of other methods or if one of the listed methods does not work, I will update the post
Also if anyone can confirm heimdall to work with the Ace this would be the first time on xda (searching I've found only people saying it may work) the Ace is not on its supported list, however as it uses the same protocol (right?) it should work?
If however the mods believe this post to be useless or irrelevant, they are welcome to move it to the appropriate location
Point 1- Hopefully useful for Linux and Mac users.
Point 2- If on Windows its much easier and takes very less time..
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
I use OS X exclusively and this was a very useful post, and at least well written and clear. Most guides blindly assume we all use Windows, not everyone does!!!
For context, owning OS X I originally used the upd1.zip method, flashed via original recovery and it worked, which I suppose is the fastest method you don't cover.
I certainly didn't know about heimdall, great to see an open-source cross platform alternative to odin! Don't need to use it just yet, though testing will be invaluable for future use...
So thanks to the OP for writing clearly about alternative options.
But instaling CWM isn't rooting, you can have CWM without root.
Wysłane z mojego GT-S5830 za pomocą Tapatalk
actually speaking in case of SGA you don't need a PC to root or to anything except heavy logcat
What restrictions using odin on windows are you referring to?
Restriction: it doesn't work if you're not using Windows is the restriction... ;-)
dragonnn said:
But instaling CWM isn't rooting, you can have CWM without root.
Click to expand...
Click to collapse
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
Prashanthme said:
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Click to expand...
Click to collapse
I've updated the post advising against using ROM Manager, thanks
Prashanthme said:
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Click to expand...
Click to collapse
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
matts95 said:
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
I've updated the post advising against using ROM Manager, thanks
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
Click to expand...
Click to collapse
Anyone tested Heimdall yet?
This is a Heimdall/Odin flashable pre-rooted stock UCLE5. This is the exact version that was released over Kies, and contains the bone stock kernel, plus rooted system, modem, cache.img and hidden.img. There are no bootloaders in this package. With this package, you can root stock ICS without incrementing the flash counter.
WARNING: THIS ALMOST CERTAINLY CONTAINS THE eMMC SUPERBRICK BUG.
See this for my considered opinion.
This package is safe to use as long as you read and follow the instructions here, and replace the stock kernel with a known good kernel.
Before 7/8/2012 there were no actual reports of damage from the eMMC brick bug in this firmware release. However, someone has bricked their phone by doing a wipe data/factory reset from a phone with UCLE5 installed and the stock kernel still installed on the phone. Please see this thread. Read the whole thread, but especially pay attention to posts #12 and 16 by Entropy512, one of our elite developers who is very knowledgable about this phone. The person with the bricked phone has confirmed by testing that eMMC memory block mmcblk0p10 was damaged during the wipe data/facotry reset, thus appearantly confirming that the eMMC brick bug is present in the UCLE5 stock kernel. It is particularly important for anyone using this firmware to be careful. It will be completely safe to use this firmware with a known safe kernel. But with the stock kernel still installed, anyone's phone could potentially be at risk.
If flashing this from another base, you should perform a wipe data/factory reset before you flash this package. The stock kernel in this package can potentially cause eMMC chip damage to phones with suseptable memory chips while performing certain memory erase operations. Therefore, it is imperative to avoid doing a wipe data/factory reset with this kernel, and also a very good idea to replace this kernel with a known safe kernel. If flashing this package from UCLE5 to obtain root, it should be fine to flash it without doing a wipe, and retain your personal settings.
This Rooted package does not include busybox. If you need busybox, you can install it from the Google Play Store.
Kernel + Modem + Cache + Rooted UCLE5 System Package: Hotfile | Dev-Host 292.18 MB
Download and extract the tar package using 7-Zip, which can be downloaded from http://www.7-zip.org/download.html. Put UCLE5_Stock_Rooted.tar in the PDA slot in Odin.
Download the Odin3 v1.85 package from MediaFire or xda-developers, or another source of your choice. Odin3 v1.82 will also work.
To flash with Heimdall command line, extract the individual files from the tar and flash the components with heimdall from the commandline as follows:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img --modem modem.bin --cache cache.img --hidden hidden.img
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.2 at this writing.)
Three different ways to install a customized kernel containing ClockworkMod Recovery onto your Rooted phone without incrementing the flash counter.
You must use an ICS kernel, and it must work with Samsung firmware, and be the no-mic-swap version. If you install a Gingerbread kernel the phone will not boot.
The main Kernel options are: Siyah v4.3.3 by Ktoonsez | Siyah v5.1.1 by AJ Newkirk (use the one without mic swap)
Kernel options are: AJ Newkirk/Siyah v3.3.3d ICS | ktoonsez/Siyah v3.4.3 ICS | N.E.A.K. ICS
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Mobile Odin Lite or Mobile Odin Pro
This is the preferred method to install a customized kernel onto your phone. In addition, Mobile Odin is a very useful tool that will allow you to install custom software directly on your phone without using a computer.
Mobile Odin Lite (free) can be downloaded and installed directly on your phone, or it can be downloaded to your computer and installed with adb. Alternatively, you can purchase Mobile Odin Pro for under $5.00 and install it directly from the Google Play Store. It's easier, and you'll support the developer!
To use Mobile Odin Lite, download the file attached to the OP of this thread. You may need to be a registerd member of xda forums to download this file. Download directly on your phone, or to your computer and move or copy it to your phones sdcard. Using any file manager such as MyFiles or Root Explorer, select the file and install it. You can also install it from your computer using the following adb command:
Code:
adb install MobileODINLite-v2.45.apk
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Transfer the zImage to the root of your phone's internal or external sdcard, using a usb cable or another method such as dropbox.
On your phone, open the Mobile Odin program. If you installed Mobile Odin Lite, when it prompts you to install the add-in, click cancel. If you installed Mobile Odin Pro, you will have already downloaded and installed the add-in to activate all the features in the program. With Mobile Odin Lite, you will still be able to install the kernel.
In Mobile Odin, click on Kernel or Install Kernel, find and select the zImage on your internal or external SD card, and then click on Flash Firmware.
Mobile Odin will flash the kernel and then reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 and later versions of ClockworkMod Recovery retain this button configuration but change it to Power = select.
If you installed Mobile Odin Lite, and you don't want to keep it, you can uninstall it now. If you want to keep it and activate all its features, download the add-on MobileODIN_FlashKernel_I777-v1.0.apk from here and install it on your phone with adb using the instructions above.
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from a pc, using Android Debug Bridge (Windows, Linux and Mac OS)
Download and install the Android Software Developer Kit (SDK) from here. You may need to run SDK Manager with administrator privledges.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
You will need busybox. If not already installed, download and install busybox from the Google Play Store.
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Move or copy the zImage into the platform-tools directory (on older installations it is the tools directory) where adb.exe resides. This will be something like (on Windows) c:\android-sdk-windows\platform-tools.
On your phone, first enable USB Debugging (Menu\Settings\Applications\Development\USB Debugging) and then plug in your USB cable, connecting your phone to your computer.
Open a command prompt. Change directory to the tools directory, then enter the following at the command line:
Code:
adb push zImage /sdcard/zImage
adb shell
$ su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
# exit
$ exit
The dd command requires superuser permission on the phone represented by a # prompt. After you type su and hit enter, look for a superuser window on your phone and give the permission. If the permission request doesn't pop up, open superuser on your phone to force the phone to prompt for superuser permission. After approval, the adb session will be listed as Unknown in superuser.
After you've finished, the code in the Command prompt window will look something like this (your command prompt and some numbers will be different):
Code:
C:\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
4279 KB/s <4776784 bytes in 1.090s>
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
10153+1 records in
10153+1 records out
5198492 bytes transferred in 2.558 secs <2032248 bytes/sec>
# exit
exit
$ exit
exit
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 and later versions of ClockworkMod Recovery retain this button configuration but change it to Power = select.
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Android Terminal Emulator
Download and Install Android Terminal Emulator onto your phone from the Google Play Store.
You will need busybox. If not already installed, download and install busybox from the Google Play Store.
Download (onto your PC) the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Transfer the zImage to the root of your phone's sdcard, using a usb cable or another method such as dropbox.
On the phone, open a terminal session with Android Terminal Emulator.
A few points to be aware of:
Android is a version of linux so you are using linux commands. Linux commands are case sensitive, so you must for instance type "zImage" and not "zimage", if that is the way the file is spelled on the sd card.
Since this will be the first time you have used superuser.apk with the terminal, you may need to approve it on you phone. After that, superuser permission will be remembered.
When you first open a terminal session, you will be at the root of the phone, or essentially "/". The $ prompt means shell access, the # prompt means root file access.
You need a # prompt to complete this Step.
If your keyboard goes away, use the menu button options to get it back.
In the terminal session, type su and then enter. You will get a superuser request. Once you approve it, you will get the # prompt.
Then type the following:
Code:
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Press enter, wait till the zImage is copied over to the named block. (takes about 2 or 3 seconds)
To close the root session, type "exit" and enter. Use the back button to close Android Terminal Emulator.
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 and later versions of ClockworkMod Recovery retain this button configuration but change it to Power = select.
You are awesome
Thank you for this creepy!
Sent from my SGH-I777 using Tapatalk 2
You da man!!!!
Been having issues with broken CWM for awhile. Used your guides to unroot... then root again and flash custom Kernel with CWM again. Thanks fixed all my issues.
Thanks I will be using this later
Excellent write-up creepy (as usual)...this is what alot of people have been waiting for and you have delivered! Covered all the bases too...now all anyone needs to get the official ICS is this thread and some reading comprehension!
Hi - can this tar be installed using Mobile Odin Lite and the i777 flash kernel? Or do I have to use heimdall or desktop odin only?
Tophaholic said:
Hi - can this tar be installed using Mobile Odin Lite and the i777 flash kernel? Or do I have to use heimdall or desktop odin only?
Click to expand...
Click to collapse
Did you even read the OP?
jack man said:
Did you even read the OP?
Click to expand...
Click to collapse
Dude...i am not asking about custom kernel - my question is can i use mobile odin to flash the root injected stock tar.
Tophaholic said:
Dude...i am not asking about custom kernel - my question is can i use mobile odin to flash the root injected stock tar.
Click to expand...
Click to collapse
Like he said he says you can in the op
transmitted from the Dark Obelisk
Tophaholic said:
Hi - can this tar be installed using Mobile Odin Lite and the i777 flash kernel? Or do I have to use heimdall or desktop odin only?
Click to expand...
Click to collapse
Mobile Oden will flash from a tar file. I haven't tested it but I assume it will flash everything in this tar file, since there are no boot loaders. Since you are asking, I assume you are already rooted in have mobile oden.
Sent from my SGH-I777 using xda app-developers app
creepyncrawly said:
Mobile Oden will flash from a tar file. I haven't tested it but I assume it will flash everything in this tar file, since there are no boot loaders. Since you are asking, I assume you are already rooted in have mobile oden.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Thank You!!!...someone finally gets my question. Its so easy on these forums to say "did you read the OP?" of course I did - not once but 10 times. but did not see anything about using mobile odin for flashing the tar file.
Yes I am rooted and have been toying with various ROMs and kernels. Was thinking about installing the stock UCLE5 with stock kernel (take the risk) and see if I like it. If not will install a custom kernel with CWM.
one more question for you - The brick bug that was there on the leaks was only if u restored from CWM after flashing the leak? So if I flash the above official release and keep the stock kernel whats my risk if I do not restore from CWM?
Tophaholic said:
one more question for you - The brick bug that was there on the leaks was only if u restored from CWM after flashing the leak? So if I flash the above official release and keep the stock kernel whats my risk if I do not restore from CWM?
Click to expand...
Click to collapse
No. I don't understand all the internal details, but I think it is when erasing from eMMC memory. Thus a wipe data/factory reset will also damage the chip, and maybe a few other operations.
You could always untar the whole archive and copy all the pieces to your phone for Mobile Odin.
The eMMC dealio is some erase method they compiled the kernel with that happens to corrupt the memory when you wipe. Its both a kernel problem as well as buggy firmware with the internal memory.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Battery Question.
Installed this ROM with no problems. Interestinly I can once again use KIES which I couldn't since rooting with other kernels, and ROM's. My question is has anyone had issues with batrtery performance since the ROM install as my battery life seems to be really dismal?
Ok so just to get it clear....i can wipe my UnNamed and install the package in cwm without encountering the flash problem and just to be safe i can install a custom kernel to replace the stock. Usually i would install it with cwm then why do i have to use mobile odin or any other methods stated here. is it because of the eMMC chip issue?
dhaval33 said:
Ok so just to get it clear....i can wipe my UnNamed and install the package in cwm without encountering the flash problem and just to be safe i can install a custom kernel to replace the stock. Usually i would install it with cwm then why do i have to use mobile odin or any other methods stated here. is it because of the eMMC chip issue?
Click to expand...
Click to collapse
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
creepyncrawly said:
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
Click to expand...
Click to collapse
Ok i see thanks.
dhaval33 said:
Ok so just to get it clear....i can wipe my UnNamed and install the package in cwm without encountering the flash problem and just to be safe i can install a custom kernel to replace the stock. Usually i would install it with cwm then why do i have to use mobile odin or any other methods stated here. is it because of the eMMC chip issue?
Click to expand...
Click to collapse
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
dhaval33 said:
Ok i see thanks.
Click to expand...
Click to collapse
I mis-read your original question. I gave you the wrong answer. You can not flash a tar in cwm. You will need to use Odin or Heimdall from a personal computer. Or, since you are coming from UnNamed, you can install Mobile Odin and flash it from your phone if you wish.
I'm having trouble getting my s2 recognized by odin, I've tried the drivers on the samsung site and the ones that come with kies mini and odin still doesn't recognize it. Can anyone help me?
Okay now im using the drivers from the not mini version of kies and it detects the phone but it now shows 2 different ID:COMs. I'm not sure if thats normal or not, i think one is the samsung mobile usb modem and the other is the samsung mobile usb cdc composite device.. It lets me select which one i want to use but idk which one i want to use and idk which is which..
Nevermind. idk what the other thing it detected was because i have nothing else plugged into my computer but i unplugged the phone and the first port went away on odin and the modem and cdc composite device both left the device manager so i plugged it back in and just clicked the first one and now it works
creepyncrawly said:
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
I mis-read your original question. I gave you the wrong answer. You can not flash a tar in cwm. You will need to use Odin or Heimdall from a personal computer. Or, since you are coming from UnNamed, you can install Mobile Odin and flash it from your phone if you wish.
Click to expand...
Click to collapse
Ok so do i need to wipe and then use mobile odin or no wipe will do?
IMPORTANT: THE S3 MINI MODULE SUPPORTS 4 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-I8190 INTERNATIONAL GSM MODEL
GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
GT-8190L LATIN/USA GSM MODEL
GT-8190T LTE MODEL
Click to expand...
Click to collapse
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
***reserved if needed***
thanks developer!!!!!!!!!!!!!!!!!!!
will report feedback after tested
Great work MSKIP the safest way and easy way to root and stock your phone thank you testing in progress.
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
SinisterGrey said:
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
Click to expand...
Click to collapse
you should pm mskip he will link you a download
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Thanks we are waiting them...
sent from the super siii mini GT-I8190 using xda premium app.
SinisterGrey said:
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
Click to expand...
Click to collapse
Sending you a link to the test file.
Mark.
mskip said:
INTRODUCING THE SAMSUNG GALAXY S3 MINI TOOLKIT
IMPORTANT: THIS TOOLKIT SUPPORTS 3 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-I8190 INTERNATIONAL GSM MODEL
GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
GT-8190L LATIN/USA GSM MODEL
Now uploading files and waiting for testers
Mark.
Click to expand...
Click to collapse
would like to test, thanks
Click to expand...
Click to collapse
funiewski said:
mskip said:
INTRODUCING THE SAMSUNG GALAXY S3 MINI TOOLKIT
IMPORTANT: THIS TOOLKIT SUPPORTS 3 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
would like to test, thanks
Click to expand...
Click to collapse
Pm me as soon as you are available to test and I will send you the installer link. It needs to be tested on an unmodified stock rom and I would advise making a nand backup before doing any testing so you can easily get back to your previous state when you are done.
If anyone else can test as soon as possible please pm me for a link as testing is going a bit slow. I would have like to have it tested on all 3 variants and released by now but as long as I know its working on 1 variant I can release it.
Mark.
Click to expand...
Click to collapse
Works great thanks. :good: Let me know if u need a logcat (default)
Can't wait to get the Pro version and donate to the toolkit. :fingers-crossed:
Great work
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Would like link also please.
Sent from my GT-I8190 using xda premium
Count me in as a tester, I can spare a few minutes here and there.
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Me too
Sent from my GT-I8190 using xda premium
i have a variant i8910L the latin american version..stock movistar peru rom unmodify so u can send me the link to test it and see what happen
Can I ask you for the link, too, please? Thank you.
SAMSUNG GALAXY S3 MINI TOOLKIT RELEASED TO PUBLIC VERSION
The Toolkit has now been tested to my satisfaction and has been released for download in the 1st post. Please remember that this is the first release and I dont own the device so there may be some textual errors or minor bugs that need ironing out. If you find any problems please post in this thread and they will be fixed as soon as possible. Do not pm me as any pm's that should be posted in a public thread will be ignored.
Enjoy
Mark.
Re: [GALAXY S3 MINI TOOLKIT V1.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Superb!!!!
Great work Mark. I'm glad to see new developers joining us.
I see an option to re-flash stock recovery but now implemented yet. If nobody provided a stock recovery for you to implement, here you go then.
So I have been trying to root my samsung phone but it has not been working. I tried downloading towel root, but it says that my phone is not supported. My phone is running build number KOT49H.I545VRUFNG6 and android 4.4.2 with kernel version 3.4. I have tried using Odin 3.09 to flash the NG5 build number to see if towelroot would work with that, but when I plugged my phone into my computer and tried going into download mode on my phone, it would not work. I already factory reset my phone twice to see if that would work, but it has not. Are there any other ways to root my phone, or am I doing something obviously wrong that is easy to fix? Any help would be appreciated.
hamglass - TowelRoot won't root NG6; you will continue to receive that "not supported" error message every time unless you downgrade. Go to this link below, and then scroll down until you find the section I pasted below the link. You'll want to download the second file, the NC5 rar, then follow the steps prescribed.
______________________
http://forum.xda-developers.com/showthread.php?t=2720163
All you need to do is download one of the following 2 all in one upgrade rar files:
I545VRUFNC2-AIO-incl-modem-hlos-nobootloaders-gogolie.rar
or
I545VRUFNC5-AIO-incl-modem-hlos-nobootloaders-gogolie.rar
Each .rar file when unpacked (NC2 or NC5 .rar files must be unpacked!) contains the following apps / odin flashable images:
Odin 3.10 (The newest and best option for Odin.)
SuperSu 1.94 (IN both a flashable thru Safestrap .zip and a .apk - thanks to Chainfire)
SafeStrap 3.72 (Thanks to Hashcode)
SeLinux Permissive Enabler / Mode Changer 1.2 (Thanks to MrBIMC)
TowelRoot v2 (Huge Thanks to geohot)
Android Terminal Emulator v1.0.53.apk
and finally...
I545VRUFNCx-AIO-incl-modem-hlos-nobootloaders-gogolie.tar
YOU CAN KEEP THE ODIN PROGRAM AND FLASHABLE FILE ON YOUR COMPUTER BUT MOVE ALL APKS TO PHONE OR SDCARD 1ST.
which is the magic file you select in Odin under AP slot and press flash to upgrade without bootloaders. This is a modified Odin image I made that also includes a .pit for mapping itself and a modem/hlos so its essentially a 1 and done file! You might need to boot into recovery and do a data wipe if you receive any FC's or issues on 1st boot (then restart and should be good to go). This is a no-wipe odin flashable image with no bootloaders or other crap just firmware and system.img and modem.
Directions to enable Root on NC2 or NC5 stock ROM & to get SafeStrap fully working:
1. Flash the odin image in AP slot for either system you want to upgrade to. (NO BOOTLOADERS OR GARBAGE FLASHED!)
2. Boot up system. If any errors occur restart to recovery (vol-up and power) then wipe data and restart. Or wipe data before flashing!
3. Once booted open TowelRoot.apkl and install and run the app. Then click on the T logo/gray box to root 4.4.2! NO REBOOT REQUIRED!!! [EisBlade: not mentioned is that it's necessary to click the box in settings to allow installs from unknown sources. Do that then return and retry install of TowelRoot apk.]
4. Now open the SeLinux Permissive Enabler / Mode Changer 1.2.apk and install the app. Open the application and click the "Permissive" box.
5. Next install Safestrap and open the app. Click install Recovery once booted. Then you can flash SuperSu .zip like normal in Safestrap. You can also also install from the Playstore or from the .apk in the AIO .rar file. However SuperSu isnt necessary its useful if you intend on controlling your ROOT.
6. Finally for a custom ROM you would reboot to Safestrap and install it in the Main/Stock Slot. Keep root by following any ROM install with SuperSu.zip!!!
7. Enjoy the easiest upgrade method known to man. Be sure and donate or thank, me or one of the fine developers mentioned above.
Hello everyone,
I want to share my experience with rooting (n00b). So for the first time ever, I managed to root my g900t and my p-600 note --needless to say, I was very excited. When everything checked out and Root Checker told me that I was indeed rooted, the first thing I did was going to Youtube to see what I could do first.
The very first thing that came up was to create a Custom Recovery...fair enough. I watched multiple videos that guaranteed to install the CR "easily". Well, I think I'm an idiot because I couldn't get anything to work.
I tried TWRP, CWM, Philz Touch and TWRP and Philz both loaded on my recovery boot but I still kept getting messages on Rom Manager that I didn't have a custom recovery. At times I also got a lot of errors. I not only tried to get information from the forum but their respective sites and matching my device, installing it through flash & Odin--no luck.
Anyways, I soft-bricked both my g900t and my p600 and after reading hundreds of posts here and other forums and spending all day, I managed to get them running again.
Right now, I'm thankful that I have both devices running and rooted but I still don't know if I have a custom recovery and frankly, I'm scared to try it again. How important is it to get a CR?
By the way, is it bad that all those bad CRs that I installed are still there (if they are)?
I read the rules and also a a lot of forum posts with different variations of CRs for my devices with no luck.
For reference:
Galaxy s5 (5.1.1) Rooted SM-G900T
Samsung Note 10.1 (5.1.1) (Wi-fi) Rooted SM-P600
Thanks guys!
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from twrp.me
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
many thanks
lost_ said:
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from ]
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
Click to expand...
Click to collapse
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
molotovgod said:
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
Click to expand...
Click to collapse
No offense intended, I think you're lost and confused. My post was never about rooting. I did understand you were rooted already. I was outlining how to install a custom recovery, which TWRP and CWM are. Yeah, if you're having a hard time sorting things out based on what I outlined, I don't know how else to get you going. Perhaps start over with your research and read up again on some basic Android 101 (not a HOWTO but an explanation on what is what). Good luck!
ps: this thread should be on the Q&A forum, but we're all helpful and friendly here and you should ask specific questions on that forum instead.
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 & https://dl.twrp.me/klte/ 2.8.7.0
kn00tcn said:
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 &TWRP 2.8.7.0
Click to expand...
Click to collapse
I have the same phone and cannot flash custom recovery either, as I am a linux user I used heimdall and here is my output
Code:
[[email protected] Downloads]# heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[[email protected] Downloads]#
I flashed my wife's Samsung Galaxy S3 (GT-i9300) and my Galaxy Tab 2 (GT-P5113) a successfully using the procedure described in each device wiki in cyanogenmod page, but same procedure in my phone fails.
My Samsung Galaxy S5 (GT-G900T) is running Samsung's stock Android 5.1.1 (not rooted btw) and stock recovery.
Can you spot what I am doing wrong? Thank you in advance.
pablomino said:
I am a linux user I used heimdall
Click to expand...
Click to collapse
https://github.com/Benjamin-Dobell/Heimdall/issues/209 i couldnt use heimdall either, but there is a patch in that thread that might work for you, you just have to recompile yourself if they didnt update the linux binary
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
kn00tcn said:
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
Click to expand...
Click to collapse
I moved to a physical Win7 PC, it didn't work either, same error. Could it be because the device is already on Android 5?
Thank you a lot.
Code:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\>cd heimdall
C:\heimdall>heimdall version
v1.4.0
C:\heimdall>cd Drivers
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>cd ..
C:\heimdall>heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
C:\heimdall>
---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------
kn00tcn said:
you just have to recompile yourself
Click to expand...
Click to collapse
Anyway I will try compiling the tool from source, I will update with my results. Thank you lot.
pablomino said:
I moved to a physical Win7 PC, it didn't work either, same error.
Click to expand...
Click to collapse
i said to use odin, i have done it several times already, although some people say a newer odin is needed for lollipop based samsung installations... i mentioned 3.07 earlier, today i did 3.10.7 with the latest G900TUVS1FOL1 complete package from sammobile so i can update my baseband & bootloader easily, then once again odin->flash twrp without reboot->remove battery->boot into twrp recovery->flash CM
heimdall does not have the code update that supposedly fixes the PIT error in the official windows binaries, so heimdall will never work on windows unless you compile the fix yourself
(if using odin, always check the exe on virustotal, always get it from someplace reliable like sammobile or an active thread here rather than google)
kn00tcn said:
i said to use odin
Click to expand...
Click to collapse
This solved my problem, thank you a lot.