Develop Bugs

[ROOT] Rooting the Galaxy S2 LTE from Rogers I727R

I just obtained the Galaxy S2 LTE from Rogers, which is a an upgrade from the one I obtained from Bell.
As a result I found myself looking for an easy way to root the device, which led to multiple posts but no clear solution as to how to achieve this on my newly obtained device.
This post is merely a recollection of the posts and threads that have helped me achieve root on the SGH-I727R sold by Rogers in Canada.
Warning: I take no responsibility if you brick your phone. Do at your own risk.
Phone specs:
Samsung Galaxy S2 LTE by Rogers
Model: SGH-I727R
Baseband: I727RUXKJ7
Android version: 2.3.5
Kernel version: 2.6.35.11
Build number: GINGERBREAD.RUXKJ7
References:
Superuser.apk and su binary: http://androidsu.com/superuser/
ZergRush binary: https://github.com/downloads/revolutionary/zergRush/zergRush.zip
http://forum.xda-developers.com/showpost.php?p=18373159&postcount=30
http://forum.xda-developers.com/showpost.php?p=18544480&postcount=46
The process
My research took me to the posts above which focus on the use of the root exploit ZergRush.
1 - Download all the necessary files
ZergRush binary
Superuser.apk
su binary
2 - Run ZergRush as follows:
This requires the Android sdk with and the use of adb, which can be found in platform-tools on the sdk directory.
open a command line (cmd.exe) and type the following commands
type in "adb push C:\[location of zergRush]\zergRush /data/local"
type in "adb shell"
type in chmod 755 /data/local/zergRush
type in "/data/local/zergRush"
This is the output to be expected (this may be different for your device. Let the binary do it's job):
Code:
$ /data/local/zergRush
/data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x00030730
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000307f8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25d9d 0xafd3975f
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
This will temporarily root your device (until the next reboot).
3 - Push Superuser.apk and su binary
Type the following commands in your command line shell:
adb remount
adb push c:\[path_to_Superuser.apk]\Superuser.apk /system/app
adb push c:\[path_to_su_binary]\su /system/bin
adb shell
chmod 644 /system/app/Superuser.apk
chmod 4755 /system/bin/su
reboot
This is the expected result:
Code:
C:\[path_to_SDK]\platform-tools>adb remount
remount succeeded
C:\[path_to_SDK]\platform-tools>adb push c:\[path_to_Superuser.apk]\Superuser.apk /system/app
4461 KB/s (785801 bytes in 0.172s)
C:\[path_to_SDK]\platform-tools>adb push c:\[path_to_su_binary]\su /system/bin
2713 KB/s (22228 bytes in 0.008s)
C:\[path_to_SDK]\platform-tools>adb shell
# chmod 644 /system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# reboot
reboot
Once the device has rebooted, you will have the application Superuser with root privileges which will allow other apps to benefit from it.
it is far from a one click app, and doesn't include any goodies that may be found in CMW4, but it's better than no root at all.
All credit goes to the creator of ZergRush and the people who contributed to the conversation on the original ZergRush thread.

Awesome.... I was wondering whether we were getting our own section or staying on the i9100 forum, glad you posted here.
Sent from my SGH-I727R using XDA App

To be honest, I didn't really know where else to put it.
Since it still somehow falls in the SGS2 category, I opted to put it here.
Hope this helps as we wait for the good stuff.

we might have to wait until it comes out on AT&T... unless we got more CDN devs that can bring on the good stuff sooner.
Have you tried installing CWM?

certainly a step in the right direction....

cue_32 said:
we might have to wait until it comes out on AT&T... unless we got more CDN devs that can bring on the good stuff sooner.
Have you tried installing CWM?
Click to expand...
Click to collapse
I haven't had a chance to play around with the roms yet. I'll probably have time this week to try and see what happens.

only way we gonna get our own section is if people start voting on that page.

How can we vote on a page? we need one!! I really want to root but im afraid to follow these experimental directions.. I cant risk bricking my phone

Could any of you fine folks clarify whether the Rogers GS2 is running Exynos or Snapdragon? I am 95% sure it's Snapdragon, but ALL info I find states "1.5ghz dual-core" and leaves it at that
Thank you, and I hope you are enjoying your phones

euphoria47 said:
Could any of you fine folks clarify whether the Rogers GS2 is running Exynos or Snapdragon? I am 95% sure it's Snapdragon, but ALL info I find states "1.5ghz dual-core" and leaves it at that
Thank you, and I hope you are enjoying your phones
Click to expand...
Click to collapse
Crapdragon, just like the AT&T Skyrocket.
You should put this in either Skyrocket dev section, or nowhere. (The I777 community is getting annoyed with all the ****rocket clutter in general/Q&A.)
What the hell were the XDA mods thinking putting the ****rocket dev section under the I777? If it were lumped with anything it should've been the T-Mobile T989 which is 98% identical.

We need our own forum someone setup the voting
Sent from my SGH-I727R using XDA App

Thanks. It worked. Took lots of tries to get everything working.
Cheers

Do we have to unlock the boot loader for this?
Hey,
The only device I have rooted before was Nexus one, where you had to unlock the bootloader first as far I remember when I did it. Do we need to unlock the boot loader to do this on the Galaxy S2 LTE. As well is there away we can revert back to original rom to avoid invalidating the warrenty? I just got the device and would hate to scrap it!!
Thanks.

digg1980 said:
Hey,
The only device I have rooted before was Nexus one, where you had to unlock the bootloader first as far I remember when I did it. Do we need to unlock the boot loader to do this on the Galaxy S2 LTE. As well is there away we can revert back to original rom to avoid invalidating the warrenty? I just got the device and would hate to scrap it!!
Thanks.
Click to expand...
Click to collapse
This is not a ROM.
The only thing you are doing is using the ZergRush exploit to gain access as root to the device and adding 2 files to your filesystem, namely Superuser.apk and su.
As far as performing the procedure, you just have to put your phone in debug mode when plugged to usb and use adb shell from the android SDK.
To go back to the original state of the device, all you have to do is remove those 2 files from their respective locations.

Entropy512 said:
Crapdragon, just like the AT&T Skyrocket.
You should put this in either Skyrocket dev section, or nowhere. (The I777 community is getting annoyed with all the ****rocket clutter in general/Q&A.)
What the hell were the XDA mods thinking putting the ****rocket dev section under the I777? If it were lumped with anything it should've been the T-Mobile T989 which is 98% identical.
Click to expand...
Click to collapse
I don't see why people keep calling it Skyrocket... There is no such denomination in Canada.
As far as the device itself, it is understandable that you don't own the device. This makes your criticism of it purely based on second hand experience - I assume that by "I777 community" that you mean you.
Some people other than you does own it, and might be interested in reading this. If you're not, why bother wasting a post in stating how much you hate the I727R and how the post is located in the wrong section (isn't that the role of the mods?).
Technically, they all fall into the Galaxy S2 category, the XDA mods should actually create one big SGS2 forum and put sub-forums for the I9100, the I777, I727R and the T989 instead of having 14 different forums for each device that is the SGS2 and they should most definitely call them by their code names instead of the carrier selected names, which throws everyone into confusion when looking for answers.

Agreed, Thanks. I understand the skyrocket is the other closest north american variant and so we should be following its development closely.
I've been trying to get other i727r owners to post requests as well.
I hope those asking for voting to be set up have actually also gone to the thread request post and added "+1 Galaxy S2 I727R".

That's what I did, however the post mod stated that it already had a forum and to stop requesting:
http://forum.xda-developers.com/showpost.php?p=19195950&postcount=1788
It's not even in the request list even though people are requesting it.

I don't see the forum anywhere?? Am I blind? I put a request in.

The mod assumed we were talking about the sky rocket so everyone go request in there "+1 SGH-I727R"
Sent from my SGH-I727R using XDA App

ninja0n3 said:
Technically, they all fall into the Galaxy S2 category, the XDA mods should actually create one big SGS2 forum and put sub-forums for the I9100, the I777, I727R and the T989 instead of having 14 different forums for each device that is the SGS2 and they should most definitely call them by their code names instead of the carrier selected names, which throws everyone into confusion when looking for answers.
Click to expand...
Click to collapse
Very good idea...

[Q] Cant root Fire

I'm trying to root my Kindle Fire, I've setup the Android-sdk and have the Google USB driver file edited and the adb_usb.ini edited to allow my Kindle Fire to be seen by adb. When I run adb devices I can see the Kindle Fire listed. My Kindle Fire is running 6.2 (3101920).
When I run SuperOneClick 2.2 it fails on one of the steps:
Code:
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118[*] Scooting ...[*] Sending 149 zerglings ...[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
I've also tried manually pushing the zergRush exploit manually and running it via adb but it fails at the same point. So I can't get temp root to get permanent root. Has anyone any ideas?

Not sure, never saw that message. But yea, Hellions with Blue Flames wreck zerglings.

Yeah they don't seem to like them at all. Really annoying as I want to be able to run CM once its released.

So I tried SuperOneClick 2.3.1.0 and it failed as well
Code:
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
END:99210export PS1=""
export PS1=""
Any idea's?

abundantmussel said:
Yeah they don't seem to like them at all. Really annoying as I want to be able to run CM once its released.
Click to expand...
Click to collapse
Oh it has already been released.
You need to activate "Download Mode"

asb2164 said:
Oh it has already been released.
You need to activate "Download Mode"
Click to expand...
Click to collapse
Download Mode?

I use "Unroot" button in SuperOneClick v2.3.1
http://depositfiles.com/files/gi9h09en5
http://www.filesonic.com/file/4092555145/SuperOneClickv2.3.1-ShortFuse.zip
SuperOneClick v2.3.1
Posted on December 4, 2011
85
As promised:
Click here to download SuperOneClick v2.3.1
Let’s see if driver installation is a thing of the past now.
You’ll notice the file size has bumped up to 10mb. This is because the driver folder is now included with the latest (at the time of writing) ADB drivers from Google.
Enjoy!
Update: I have a 5mbit upload so at times the download queue may be full. You might have to be a bit patient with my server. If somebody would like to post a download, you can do so in the comments.
Update2: v2.3.1 is up (had to remove testing code that conflicted with XP systems)
Update3: Links are now mapped to a multiupload sharing. (My internet connection has been slowed ridiculously)
Click to expand...
Click to collapse
Then reboot the Kindle Fire.
"Root" button again and gain the superadmin.

Got it working. Tried it in Linux using the newest zergRush file I could find. CM7 is awesome.

Problems rooting the kindle
I have windows 7. I downloaded the sdk and finally got the tools, platform tools, and the google usb driver, and the web driver to install. I can't install any version of the api's. The file I'm missing is adb_usb.ini so I can't go in and add what I need to. I added the stuff in the other file. I can't update the driver because it doesn't give me the option. And obviously it's not seeing anything in command prompt. I have followed all directions. It took four or so tries before the usb driver would even install. So there is no adb file or document anywhere. There is no kindle folder anywhere, just the android folder, but still doesn't have that one file I need. I was told to put twrp on my computer and that would install the adb driver, but that's not doing anything but messing my computer up.

abundantmussel said:
I'm trying to root my Kindle Fire, I've setup the Android-sdk and have the Google USB driver file edited and the adb_usb.ini edited to allow my Kindle Fire to be seen by adb. When I run adb devices I can see the Kindle Fire listed. My Kindle Fire is running 6.2 (3101920).
When I run SuperOneClick 2.2 it fails on one of the steps:
Code:
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
I've also tried manually pushing the zergRush exploit manually and running it via adb but it fails at the same point. So I can't get temp root to get permanent root. Has anyone any ideas?
Click to expand...
Click to collapse
To root KF, use BurrittoRoot3 explained at
http://forum.xda-developers.com/showthread.php?p=20668030
Or use Kindle Fire utility explained at
http://forum.xda-developers.com/showthread.php?p=20455567
Sent from my Amazon Kindle Fire using Tapatalk

Sabrina said:
I have windows 7. I downloaded the sdk and finally got the tools, platform tools, and the google usb driver, and the web driver to install. I can't install any version of the api's. The file I'm missing is adb_usb.ini so I can't go in and add what I need to. I added the stuff in the other file. I can't update the driver because it doesn't give me the option. And obviously it's not seeing anything in command prompt. I have followed all directions. It took four or so tries before the usb driver would even install. So there is no adb file or document anywhere. There is no kindle folder anywhere, just the android folder, but still doesn't have that one file I need. I was told to put twrp on my computer and that would install the adb driver, but that's not doing anything but messing my computer up.
Click to expand...
Click to collapse
would recommend to read this first:
http://forum.xda-developers.com/showthread.php?t=1552547

kindleadb.zip
i need a link to kindleadb.zip that actually work anyone have it?

The standard android ADB will work once you edit the .ini to include the vendor code for lab126 (Amazon).

Check out this thread: http://forum.xda-developers.com/showthread.php?t=1443071
I used this to root my KF and it was super easy. Also, I had very little experience rooting or with SDK or ADB and I was able to do it. The author, northmendo is very nice and helped me out a lot even with stupid questions. I highly recommend KindleWater and northmendo.
I hope this helps.
Sent from my Kindle Fire using Tapatalk 2

Thanks for the links but this thread is very old, I got the Fire rooted in early December all these links didnt exist then

i have a question when i press Volume Up, Power, Menu buttons

it takes me to android recovery, i noticed theres a option that says apply update from sd card,
if i put the super user zip to my sd card will it root it? i dont want to brick it though! any suggestions?
please help!

well i just tried installing superuser zip that i got from here http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-mac-osx/
and it said signature verification failed. hmmm

Need custom recovery to flash that.

damn i got all happy for a seconds thinking i can root my s3 without using my mac!!!
:crying: still unable to root! damn you jellybean! hahaha
is downgrading to ics to root s3 troublesome?

Use the methods that are stickied. Can HARDLY ever go wrong there. I say hardly cause some forums for older phones are not up to date, these are.

mt3g said:
Use the methods that are stickied. Can HARDLY ever go wrong there. I say hardly cause some forums for older phones are not up to date, these are.
Click to expand...
Click to collapse
yeah ive been looking and the only way to root it is with a pc, which the closest one is the library that doesnt enable downloads! =(

beto0216 said:
yeah ive been looking and the only way to root it is with a pc, which the closest one is the library that doesnt enable downloads! =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1946149&highlight=root+with+mac
this won't work?

mt3g said:
http://forum.xda-developers.com/showthread.php?t=1946149&highlight=root+with+mac
this won't work?
Click to expand...
Click to collapse
nope this is what i get.
***************************************************************
*
* One-Click Root Script for Galaxy S3!
*
* brought to you by Ultimatedroid.blogspot.com
*
* Credit goes to XDA user sparkym3 for exploit & Max Lee.
*
***************************************************************
This script will give you
1. Root !
Please read full tutorial at Ultimatedroid.blogspot.com
***************************************************************
waiting... If you get stuck here, try another USB port.
* daemon not running. starting it now *
* daemon started successfully *
Start Rooting...
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
All Done rooting Galaxy S3, install SuperUser or SuperSU app from Play Store to get full root!
rootmac.sh: line 40: unexpected EOF while looking for matching `"'
rootmac.sh: line 42: syntax error: unexpected end of file

I don't have a mac so I don't have the issues obviously but did you do what it said to do? Go to play store and install Super SU just to test? also, can you not use ODIN? Since no one else is helping I figured I would jump in and spit ball ideas.

Rooting Issues

Hey, first here's some information on my phone:
Arc S
Model Number: LT18i
Android Version: 4.0.3
Build Number: 4.1.A.0.562
Bootloader Unocked: Yes
So, I unlocked the bootloader and I'm now trying to root the device; in order to install Cyanogenmod. I've tried both methods at (I can't post links =__=):
techdraginfo.blogspot.com/2012/06/root-sony-xperia-arc-arc-s-official.html
Click to expand...
Click to collapse
neither have worked for me.
Here's what I've done and what isn't working.
For method 1:
I've installed the ADB drivers, get up to step 8, put the phone in fastboot mode, enter the command fastboot boot ARC-DooMKernel-ICS-BETA-v04-lower-boot.img and I'm prompted with:
Device Waiting
Click to expand...
Click to collapse
It never gets past this point.
For the One-Click method;
I've installed the ADB drivers, extracted DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su.zip to C:\, run the .bat script and I get a whole bunch of issues related to ADB, such as:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
--- creating temporary directory
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
It continues like this for the rest of the script. I don't understand why it will not connected to the ADB server. I've killed any ADB processes previously running prior to running this script and turned off my anti-virus changes.
Any idea why this is?
Cheers

Slycs said:
I've tried both methods at (I can't post links =__=):
Click to expand...
Click to collapse
Use the methods from xda, you can find them in the stickys or browsing general, or what you should have done first, searching - root arc s

If you want to install CyanogenMod and you have unlocked your bootloader, then just install kernel and install ROM from it. No root necessary.
Sent from LT18i with custom firmware by myself.

Can't do IMEI/NVRAM backup MTK, can't root

Hey, guys.. I can't get through following issues. Phone's firmware is full vanilla since the very beginning - only updated from Jelly Bean/ICS to 4.4.2 with OTA.
I want to install TWRP Recovery and then try some custom firmwares. I started with making a backup of IMEI/NVRAM by MTK Droid R&T just to be safe.
I can't, IMEI/NVRAM button is greyed out. Log:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
I've looked for solutions. They suggest e.g. searching for MTK app from different source. It doesn't help.
Setting up a root is also a trouble. I tried to use the simpliest, well known method within the reach based on Batch script.
Log:
Code:
[*] Waiting for device...(Connect your LGOG via USB in Charge Only Mode)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
Beginning Root Process
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
Press any key to continue . . .
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
Device is properly connected to adb.
Code:
(...)\ZV9-ZVB-Universal-Root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
LGE9751acf27d9 device
I'm aware that those problems might be trivial to fix. In that case, sorry for wasting your time. Still, thank you greatly for help. I can provide all needed info.
<< I can't post screenshots :/ - newbie user.

Glaeqen said:
Hey, guys.. I can't get through following issues. Phone's firmware is full vanilla since the very beginning - only updated from Jelly Bean/ICS to 4.4.2 with OTA.
I want to install TWRP Recovery and then try some custom firmwares. I started with making a backup of IMEI/NVRAM by MTK Droid R&T just to be safe.
I can't, IMEI/NVRAM button is greyed out. Log:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
I've looked for solutions. They suggest e.g. searching for MTK app from different source. It doesn't help.
Setting up a root is also a trouble. I tried to use the simpliest, well known method within the reach based on Batch script.
Log:
Code:
[*] Waiting for device...(Connect your LGOG via USB in Charge Only Mode)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
Beginning Root Process
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
Press any key to continue . . .
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
Device is properly connected to adb.
Code:
(...)\ZV9-ZVB-Universal-Root>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
LGE9751acf27d9 device
I'm aware that those problems might be trivial to fix. In that case, sorry for wasting your time. Still, thank you greatly for help. I can provide all needed info.
<< I can't post screenshots :/ - newbie user.
Click to expand...
Click to collapse
How I root my device:
1. Download the towelroot apk http://towelroot.en.uptodown.com/android
2. Go to Settings > Security > Unknown Sources (enable/allow it)
3. Select the towelroot on the notification dropdown and install
4. Launch towelroot and root your device
5. Download Root Checker on Playstore to double check if you've successfully rooted your device

@erkasmoter
App returns message: "This phone isn't currently supported". :/ Thx, tho. I really want to get TWRP working..