Develop Bugs

[GUIDE] Instructions to Root G2 [Temp Root]

NOTE: The below info is all pretty outdated now that the fantastic Paul O'Brien has created a one-click temp root app called VISIONary. I recommend using that - get it from his thread! In case you don't want to do that (what are you, some kind of masochist?), or want to see the old way of getting temp root, keep reading this thread.
Insert the usual disclaimers about "if this breaks your device, it's not my fault... do this at your own risk... voiding warranty... etc."
Note that for now, this is a TEMPORARY root. And things are now well over my head... I just got lucky with figuring out the first few steps. For now, I'm going to leave it to the fantastic folks over in the thinktank thread to figure out how to make this permanent, and will help out wherever I can.
Update 10/6/2010:
Per suggestions later in the thread, I've compiled a zip file of everything needed to set up a temp root. I've also made some tweaks to the root script, included in the archive as "root" - notably, it will now create symlinks to busybox for commands not included with default android (example: cp).
Here are updated instructions to use with the attached zip file. USB Debugging needs to be enabled:
Stage 1: On your PC
1. adb push su /sdcard/su
2. adb push Superuser.apk /sdcard/Superuser.apk
3. adb push rage /data/local/tmp/rage
4. adb push busybox /data/local/tmp/busybox
5. adb push root /data/local/tmp/root
6. adb shell chmod 0755 /data/local/tmp/rage /data/local/tmp/busybox /data/local/tmp/root
7. Disconnect phone from pc
Here's an alternate Stage 1, thanks to Aphotix:
Aphotix said:
If you really want to optimize (or be lazy if you are like me), just use this batch file (for windows obviously) using the pc side of the instructions already provided.
Code:
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push rage /data/local/tmp/rage
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
just place it inside of the G2TempRoot folder and double click. Then its just two commands on the phones terminal and you have root.
Click to expand...
Click to collapse
BATCH FILE DOWNLOAD HERE
Stage 2: On your phone (Assumes you have already installed Android Terminal Emulator from the market)
1. Launch Terminal Emulator
2. /data/local/tmp/rage
3. Wait for the message: "Forked #### childs."
4. Menu > Reset Term - Terminal Emulator will exit.
5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
6. /data/local/tmp/root
Stage One only needs to be done once. Stage 2 needs to be repeated every time you reboot your phone.
Follow the Thinktank thread for progress on a permanent root solution.
Special Thanks:
The dude that made rageagainstthecage - http://c-skills.blogspot.com
gariak, for the ideas in the root script
rpmccormick - improvements in the later PC steps
Aphotix - Windows batch file to make the first part easier

You're a beast. Thank you.

So do we get any roms soon after rooting?
Sent from my T-Mobile G2 using XDA App

Well, that's up to the rom developers. Will probably take time.
Note that currently, this is a TEMPORARY root. And things are starting to get a bit over my head... I just got lucky with figuring out the first few steps. For now, I'm going to leave it to the fantastic folks over in the thinktank thread to figure out how to make this permanent. I'm working to figure out what I can, but I fear my own usefulness is fading
(added that info to OP, since it's probably important)

Ill wait til its permanent
Sent from my T-Mobile G2 using XDA App

This is interesting.. you need to try to get a rooted recovery made.. from there once you get this temp root working try to flash the recovery through terminal.. if it takes then you would be able to flash rooted roms... i wonder if clockwork is working on a recovery already??...

Whew, I was starting to think the phone might be unrootable.
Sent from my T-Mobile G2 using XDA App

OgBrog said:
Whew, I was starting to think the phone might be unrootable.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
What the heck are you talking about? This phone hasn't even been released officially and you are already tired of waiting on root? why don't you learn some stuff and crotribute to helping us get root?
Guys, I know the thought of developing on linux is scary but you can always start with simple stuff like boot animations and themes. Don't you notice how most developers have left xda because all people do here is ask and not give. quit crying, complaining, and posting stupid ****! learn to contribute!
sorry I was up all night last night and got no sleep working on trying to ROOT this damn phone and figuring out what the deal is with our missing storage space on the g2. I'm just cranky. and btw, this isn't directed just at this guy but a lot of people here. sorry to single you out. nothing personal.

weird I dont know what I messed up because the commands for the phone are alot of typing so I copied that text and made a script minus the '#' symbol for all lines and when I run it can;t kill process says can't find and won't remount but if I type it into the phone working fine
here is exactly what I put in on the script for terminal on device
/data/local/tmp/busybox killall rageagainstthecage-arm5.bin
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
/data/local/tmp/busybox cp /sdcard/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /sdcard/su /system/bin/su
/data/local/tmp/busybox cp /sdcard/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system

sino8r said:
What the heck are you talking about? This phone hasn't even been released officially and you are already tired of waiting on root? why don't you learn some stuff and crotribute to helping us get root?
Guys, I know the thought of developing on linux is scary but you can always start with simple stuff like boot animations and themes. Don't you notice how most developers have left xda because all people do here is ask and not give. quit crying, complaining, and posting stupid ****! learn to contribute!
sorry I was up all night last night and got no sleep working on trying to ROOT this damn phone and figuring out what the deal is with our missing storage space on the g2. I'm just cranky. and btw, this isn't directed just at this guy but a lot of people here. sorry to single you out. nothing personal.
Click to expand...
Click to collapse
I think you may have singled out the wrong person. As I understood it, his post was stating that he was worried we weren't going to be able to root the phone at all...intending the post to be a 'sigh of relief' if you will. There was no implication of being impatient.
And I know it's annoying when people demand stuff without contributing, but if were to open a restaurant and everything on the menu was free, guess what? You'd have a crapload of customers, and they'd all be asking for stuff for free. Once development picks up, there will be a lot less posts about people wanting root and such...just be patient. Coming from a guy who pre-ordered the g1, I think I know a little bit about waiting for good things to happen.

M9x3mos said:
weird I dont know what I messed up because the commands for the phone are alot of typing so I copied that text and made a script minus the '#' symbol for all lines and when I run it can;t kill process says can't find and won't remount but if I type it into the phone working fine
here is exactly what I put in on the script for terminal on device
/data/local/tmp/busybox killall rageagainstthecage-arm5.bin
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
/data/local/tmp/busybox cp /sdcard/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /sdcard/su /system/bin/su
/data/local/tmp/busybox cp /sdcard/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
Click to expand...
Click to collapse
That IS strange...I don't see anything wrong with what you've posted here...but I can say that I've seen some strange happenings lately. I'm getting rid of a samsung epic for the g2, and if I used the cable that came with it, nothing through adb would work properly, I had to use a better quality one I got off amazon.

InGeNeTiCs said:
That IS strange...I don't see anything wrong with what you've posted here...but I can say that I've seen some strange happenings lately. I'm getting rid of a samsung epic for the g2, and if I used the cable that came with it, nothing through adb would work properly, I had to use a better quality one I got off amazon.
Click to expand...
Click to collapse
I agree or try a different driver (pdanet one). It is showing under adb devices right? that cable that came with was giving me hell while trying to charge it last night. I'm not sure as using it to tether for adb because I used my old one for the pc.

sino8r said:
What the heck are you talking about? This phone hasn't even been released officially and you are already tired of waiting on root? why don't you learn some stuff and crotribute to helping us get root?
Click to expand...
Click to collapse
I didn't mean to sound ungrateful, it's just that every other phone I've ever
owned already had a root method when I got it. After reading that no previous
root methods work I worried it might be locked like the droid X.
I really don't know too much about rooting and I doubt that there's anything that
I could think of or do that someone more knowledgeable hasn't already done.

CM on G2
Cyanogen said he has already written the device config profile. So as soon as there is root ans the BBQ is over there will be CM!
hendusoone said:
Well, that's up to the rom developers. Will probably take time.
Note that currently, this is a TEMPORARY root. And things are starting to get a bit over my head... I just got lucky with figuring out the first few steps. For now, I'm going to leave it to the fantastic folks over in the thinktank thread to figure out how to make this permanent. I'm working to figure out what I can, but I fear my own usefulness is fading
(added that info to OP, since it's probably important)
Click to expand...
Click to collapse

Sweet
Sent from my T-Mobile G2 using Tapatalk

OgBrog said:
I didn't mean to sound ungrateful, it's just that every other phone I've ever
owned already had a root method when I got it. After reading that no previous
root methods work I worried it might be locked like the droid X.
I really don't know too much about rooting and I doubt that there's anything that
I could think of or do that someone more knowledgeable hasn't already done.
Click to expand...
Click to collapse
The reson none of the old methods have worked so far is because this is an entirely new device. With this device we have new hardware and stock software that has not been seen/hacked yet. We are getting there so just hold out a little while, this device will rock when rooted, and after the BBQ this weekend we should have a few more guys looking into this with us.
Back on topic now
Sent from my T-Mobile myTouch 3G Slide using XDA App

AWESOME!
hendusoone said:
Insert the usual disclaimers about "if this breaks your device, it's not my fault... do this at your own risk... voiding warranty... etc."
I used the rageagainstthecage binary from the download in this blog post: http://c-skills.blogspot.com/2010/08/droid2.html
On PC:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
exit
On G2:
Open terminal emulator
cd /data/local/tmp
./rageagainstthecage-arm5.bin
Wait a bit for it to say "Forked #### childs." Then hit enter. Should have a $ prompt.
Try running "ps" - should say Cannot fork.
Exit terminal emulator with back button, launch an app (I launched Twidroid, probably doesn't matter which app you pick)
Launch Terminal Emulator again - it will force close, hit Force Close
Launch Terminal Emulator a second time and you have a root shell
Additional info from gariak, from here:
Currently working on further instructions to make this a permanent root... will edit those in once ready. Others are doing a bunch of work on it, too... keep an eye on the root thinktank thread for further developments - the fun starts at this post!
Note that for now, this is a TEMPORARY root. And things are starting to get a bit over my head... I just got lucky with figuring out the first few steps. For now, I'm going to leave it to the fantastic folks over in the thinktank thread to figure out how to make this permanent. I'm working to figure out what I can, but I fear my own usefulness is fading
Click to expand...
Click to collapse
This is awesome! Will certainty be following this rather then all of the ghey fags in general complaining like a bunch of women.
Now we just need a root SPL or something to flash in the root shell right?

You can follow the happenings in the thinktank thread. Best to just follow or test what is suggested if you feel comfortable.
On a side note the other build posted makes for a good un-root so I would keep it named PC10IMG.ZIP on the root of your sdcard, should anything bad happen to your phone you should be able to flash that from bootloader
Sent from my T-Mobile myTouch 3G Slide using XDA App

What's the username and pwd to get the file?

The other build has radio 12.21.something. My g2 came with 12.22.something. So you would have to downgrade your radio. Should work though.
Everything else looked to be the same though.
edit: Nevermind, after reviewing the numbers I read them wrong. Everything does look to be the same. Apologies, with my first drill weekend with the army reserves and still moving into a new house I guess my head wasn't completely in the game.

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)
Edit: This does not works on anything newer than ICL53F (i.e., 4.0.2). It works fine on ITL41D (4.0.1), ITL41F (4.0.1) and ICL53F (4.0.2)
Once you have got root, you can now use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it (but I will take credit for the step-by step ). Thanks to kendong2 for pointing it out to me here.
So, it looks like zx2c4 has found a local privilege escalation exploit. See source here, and saurik has managed to package it together for Android. See here. Although this may be old news to some, I hadn't seen it before.
So what does this all mean:
If you are running a 2.6.39 kernel (or above), which all Galaxy Nexus' are, you can now root your device without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
2) This needs to be done over ADB, as a terminal emulator on-device does not have the appropriate access. If you do not have ADB, I've attached it in the zip. Unzip all files.
3) Some users indicate that, once finished the procedure, they needed to open the Superuser app.
Step-by-step:
1) Download the attached files to your computer and unzip them in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the files to your device:
adb push mempodroid /data/local/tmp/mempodroid
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Open a shell: adb shell
5) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
6) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
15) Done. You now should have root without having to unlock your bootloader.

Reserved

Reserved

This is the same as https://github.com/saurik/mempodroid
saurik ftw.

times_infinity said:
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
Click to expand...
Click to collapse
Not sure what you are getting at? I mentioned saurik in the first post, and the link you posted is in the first post. And I mentioned that this may be old news, but I haven't seen it anywhere before today in the GN forums.

Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!

Sleuth255 said:
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Click to expand...
Click to collapse
You need ics to have a vulnerable kernel version, so given the number of devices which currently have ics officially, I doubt it will be common. I'd also expect Google and vendors to correct this in next release.
Also many custom kernels don't have this flaw as they are at or over 3.0.18 or have patched it. This prevents gaining unnoticed root.
Sent from my Galaxy Nexus

Hmmm I thought 2.6.39 was found in GB builds. This exploit is almost a root fix for the Moto DX 4.5.621 fiasco. Unfortunately the kernel for that build is 2.6.32.9.
Sent from my Galaxy Nexus using xda premium

This was huge in the headlines a few weeks back. It's nice to see someone putting it to a good use!
Sent from my Galaxy Nexus using xda premium

Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.

Huxleysäl said:
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Click to expand...
Click to collapse
I think you are mistaken. In a terminal emulator type: cd /data/local/tmp
Edit: Fixed a mistake made by auto correct...
Sent from my Galaxy Nexus using Tapatalk

efrant said:
I think you are mistaken. In a terminal emulator type: cd /data/local/temp
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links

try /data/local/tmp

Huxleysäl said:
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
Click to expand...
Click to collapse
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb

Huxleysäl said:
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Click to expand...
Click to collapse
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk

OK, this is exactly what I did:
I downloaded the files, extracted them into the ./sdcard folder of my android. I opened the console, wrote exactly as stated. Reaction? Cannot create /data/local/tmp/mempodroid: Permission denied
So, what I'm thinking is this: I tried the cd ./sdcard/mempodroid, found it. So, logically, that should mean that since the permission is dennied, the problem lies not in where I put the mempodroid, but with my authority over my phone. So, here we are again. Could anybody smarter then me clarify?
efrant said:
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
****, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.

Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.

convolution said:
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
Click to expand...
Click to collapse
I hade my initial problems with that too. But as if this moment it doesn't really matter. Read above posts. Anyhow, to answer your question: you need to download a console emulator
Just search for it in the market. Also the commands go in this console
For example: cat /directory/filename > /newdirectory/samefilename means to copy or move from one place. To change permission you just write that line of code ending with 777 instead of cat and then the filename etc and etc.
I didn't know any of this 'till yesterday, so it is quite understandable.
cheers

Huxleysäl said:
F***, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Click to expand...
Click to collapse
I've updated the first post. Give that a go and let me know how it turns out. (The guide may need some minor tweaking, but I am here to help you through it.)
It seems that ADB has rw access to /data/local/tmp but a terminal emulator on-device does not. So for now, you need to be plugged into your computer.
It may be possible to do this with ADB-over-Wi-Fi, but I haven't gotten there yet.

Gordita Root: Optimus V exploit March 24th 2012

This is an exploit, I take NO RESPONSIBILITY if this does ANYTHING bad, your fault not mine, it was only tested on the firmware mentioned below. If you redistribute it, republish, work it into a all in one click, please link back and PROPERLY credit me.
Tested on the
ro.build.date=Mon Jan 30 10:42:53 KST 2012
ro.build.version.incremental=ZV9.479A6632
Update for the VirginMobile LG Optimus V
Your phone needs to be updated to the above build, and potentially needs a factory reset before this works, but it works fine. This will allow you to flash recovery without being root. After flashing recovery, flash this zip http://dl.dropbox.com/u/8699733/rootme.zip to install su, superuser and disable re-flashing of the stock re covery
LinuxMac Script + files:
https://github.com/CunningLogic/GorditaRoot
Flash_image:
https://github.com/CunningLogic/GorditaRoot/blob/master/flash_image
Recovery:
http://www.mediafire.com/?vzc5k8taj9smmll (Credit BobZhome)
Windows users run the commands manually
GNU nano 2.2.2 File: Gordita.sh
Code:
#!/bin/sh
echo "GorditaRoot 1.0 by jcase / TeamAndIRC"
echo "for the VM670 Optimus V"
echo "March 21st 2012"
echo "Follow me! http://www.twitter.com/TeamAndIRC"
echo "Donations are optional http://forum.xda-developers.com/donatetome.php?u=2376614"
echo "-"
echo "Recovery taken from http://forum.xda-developers.com/showthread.php?t=1197991"
echo "-"
echo "Pushing recovery to /data/local/"
adb push VM670NH_recovery.img /data/local/recovery.img
adb push flash_image /data/local/
adb shell "chmod 755 /data/local/flash_image"
echo "Removing old sensor config, setting up symlink attack"
adb shell "rm /data/amit/*"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
echo "Rebooting to execute symlink attack, to chmod 666 the recovery block device"
adb reboot
adb wait-for-device
sleep 10
adb shell "rm /data/amit/*"
adb shell "/data/local/flash_image recovery /data/local/recovery.img"
echo "Recovery flashed! Enjoy"
Having trouble identifying whether or not you completed the root process? Quickly test for root access with Root Checker Basic

Confirmed working on a phone donated just for this purpose!
Started with stock firmware, Android 2.2.1, baseband VM670ZV4_60401001, generic android recovery
Flashed the VirginMobile Security Update from their website, became VM670ZV9_60401001 ZV9.479A6632
Manually walked through above script by jcase via gtalk, and using the exploit, was able to flash BobZhome's CWM for the VM670, reboot into it and made a backup.
Flashed the su zip, and all is well in Optimus V land again.
HUGE THANKS TO JCASE FOR TAKING THE TIME TO RE-ROOT THE VM670!!!

I only wish I understood what it all meant--so I could be excited, too!

wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
Means ppl who couldnt root before, now can

wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
i was gonna ask the same thing LOL

Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!

jlear3 said:
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
Click to expand...
Click to collapse
The update is not being pushed, because the OTA mechanism doesn't work on the OV. You have to go to the VM website and download the update from the phone FAQ.
The only advantage is a new radio, which give slightly improved performance.

Thank you very much!
I installed the update to my (unmodded) backup phone without thinking about whether or not I'd be able to root the handset after applying it. DOH!
I have just been using this phone as a WiFi device so far. I have run the battery down and recharged it once and installed a few apps on it. So I will run it down, recharge it again and then do a factory reset before I try rooting it just to make sure that I don't hose it.

It's a good idea to check all the steps before you start ...
Finally ran my battery down for the second time. So, I recharged, ran a factory re-set and ran the shell script on my Linux box to root the phone.
Oops!
The file VM670NH_recovery.img downloaded as VM670NH_recovery.bin and the system can't find/stat it! Hit ^C and bailed!
Hoping, hoping, hoping ...
Good! It's not bricked!
Renamed the recovery file, re-ran the script. Success!!
Rebooted into recovery, flashed rootme.zip
==> Did a nandroid backup.
Downloaded root check basic app and confirmed that it has worked.
So, for other modders trying this out:
Check your files and file names before you start! When I looked at Gordita.sh the first time I found that what I had downloaded was an HTML file with the script embedded in it. Copied and pasted from the OP and then checked again to make sure I had the right content.
Of course if you are running the adb commands manually then this won't happen to you.
But, as I noted above, I didn't cross-check that the recovery file that the script would be looking for had the right file name extension (.img, not .bin), so don't be me.
That said, jcase: Thank You Very Much!! Not only for developing this root exploit but also for making one that is robust enough for someone like me to goober it up and still come out unburnt!

After all of this , can you make it a hotspot in quick settings?

The setting dialog is there ..
H0daddy said:
After all of this , can you make it a hotspot in quick settings?
Click to expand...
Click to collapse
Once I rooted my phone I installed a modified ROM. And then another one, and then ...
I saw your question a bit ago and since I no longer had the stock ROM installed (and had never used Quick Settings to enable the hotspot feature before) I didn't know. I still don't. Here is the story on that ...
I just restored the ZV9 ROM from backup today and then installed the Quick Settings app. I can say that the app still has the option to enable the hotspot available and that it tries to set it up. However the phone I am using hasn't been activated yet and the 3G network isn't provisioned on it. So all I get is a message saying the network isn't available.
So, it looks somewhat promising. Maybe someone who has an activated phone with the ZV9 ROM can test it out and let you know.
And if I activate this phone before you get a useful reply I'll test it to see if it works.

So happy to see this

Please assist
Got up to step adb shell "chmod 755 /data/local/flash_image"
But got back "no such file."

CWM
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?

knicks791 said:
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
Click to expand...
Click to collapse
so you have bobz recovery installed?... i assume youve tried rebooting to recovery form the powered off state via the key combo (HOLD home+vol down+power, RELEASE after the LG logo), and tried instal zip from sd again?...
try:
http://forums.projectopencannibal.net/beta-releases-11/lg-optimus-v-v2-1dev1-(10-09-2012)/
http://forums.projectopencannibal.n...1-universal-installer-for-lg-optimus-devices/

[FIX] Permissions Work Around for ICS

Script to flash via CWM to fix fix perms has been done by minotauri (sorry if miss spelled will fix when on a computer) he deserves credit for the edify:
To Run Fix Perms While in Recovery Flash this file each and every time you need it run [for now]:
http://goo.gl/hrL7E
The Next Script is one you can flash via CWM and it will replace the file ROM Manager uses so this will remain between restarts and you can use it via ROM Manager or Script Manager anytime you want!:
Thank Minotauri again for another beautiful Edify!
http://goo.gl/qPpC3
Flash via CWM and it well work for that flash just flash anytime you need to run it via recovery until I see about permanently copying it over existing script or still can run manually with this guide if you choose [scroll down below the additional update on how to fix the script to run using ROM Manager while in OS!].
I posted this in a couple ROM threads and was asked to throw it out here as folks from different ROMs are all affected. I can only speak for TMobile Galaxy S2 as that is what I own, drive and work on...
I will be cleaning up the post a bit when I get time just want it posted so others can use the information add it really seems to help clean up small issues (even some report fixing multiple FCs after running fix perms this way!)
NEWEST UPDATE 2012.04.19
OK FIX FOR RUNNING FIX PERMS INSIDE OS VIA ROM MANAGER
If you adjust first line in script to #!/system/xbin/sh viola ROM Manager does not freeze [finally]
I did this with Ghost Commander [don't forget settings> check auto root] and long press fix_permissions and choose edit tapping it will have GC try to execute it.
I also moved down to set variables piece and placed 1s instead of 0s next to mount system, mount data, and remove (as in REMOVE stale data ) [should be all caps in /data/data/com.koushidutta.rommanger/files/fix_permissions
I am still working on finding a way of making those changes permanent in /sbin under recovery boots
Fix Permissions Work Around ICS
Run Fix Permissions via ADB Shell with Phone in Recovery
I have taken the time to document what should be a complete guide to running fix permissions while the phone is in the Recovery menu using adb.
I am posting the quick steps right after this, but if you scroll below that this is an extended step-by-step guide.
Code:
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Supplies [Phone, USB Cable and Android SDK (http://developer.android.com/sdk/index.html)
Follow the link to install Android SDK [they have directions on site]
first time installing adb? [Skip otherwise]
To Add ADB to your computers path [to run it from any directory]
Windows:
Open Command Prompt [Click Start, Click Run, Type in cmd and hit Enter [XP]]
Open Command Prompt [Click Start, type cmd in whitebox and hit Enter [Vista and 7]]
type set PATH=%PATH%;C:\android-sdk\platform-tools [or wherever you put android sdk just add platform-tools to the end [it is a hidden folder]
Linux [OSX should be same]:
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved it]
export PATH
Now That You Have ADB and path set, time for good stuff
Opening a Command Processor
Open a Command Prompt [Windows] or Terminal [Linux or OSX]
Windows: Click Start, Click Run, Type cmd and hit enter [XP]
Click Start, type in to Whitebox cmd and hit Enter [Vista and 7]
Linux: Hold alt and hit F2 on keyboard [should see a run box now]
Type in xfce4-terminal and hit Enter [or substitute your terminal command this is xubuntus]
Once a Black and White Screen Opens...
Gaining Elevated [Admin or Root Privileges]
Ok, some further testing shows me you should have root or admin access to command processor before running ADB.
In Windows
Type The Following in to the command prompt window already open...
runas /user:%computername%\administrator cmd
hit enter when done
[yes just like that including %computername% windows will fill it in with proper info copy/paste if needed right clicking in command window should paste text for you [if not right click on the icon in left hand corner of title bar choose properties and place checks in the quick edit and insert mode boxes under Options tab]
now it will ask for a password if you have not set one you need to go to control panel users and set a password on admin account before this will work
Once you enter the password and hit enter a second command window will open and will have Administrator in the title
Now You can continue on
In Linux
With Terminal window open type:
gksudo xfce4-terminal& [sub your terminal command if not using xubuntu]
once you hit enter it may take a second but you will get a password prompt enter in your password and a new terminal will open and it will have [email protected] in the title
Now you can continue on...
Checking USB Connection
type in adb devices and hit enter
[if you get a command not found you will have to use cd to move to directory with adb [ie cd c:\android-sdk\platform-tools]
If it comes back with ?????? as serial number it is not connecting correctly follow the next steps otherwise skip the next bit if you didnt get all ?
I get ?????, what gives?
This seems due to not running command prompt or terminal as administrator or root user [Windows / Linux Respectively]
You will need to do the following in order
Disconnect USB from phone
On Phone: In Advanced menu choose restart recovery
On Computer: type in adb kill-server and hit enter
Reconnect USB cable
Be Sure To Follow Section above labeled: Gaining Elevated [Admin or Root Privileges] and then continue on
On Computer: type adb devices and you should see a mix of letters and numbers
and that means we are good to go on
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

Known Issues:
-------
Issue: My computer does not connect when I use adb shell [or I get ????? when I use adb devices]
Resolution:
I have found that i have to connect my phone 2x to computer to get it to work correctly most of the time, do the following
Disconnect USB from phone
In advanced menu on phone choose Restart Recovery
on computer: adb kill-server
Reconnect USB cable
on computer: adb devices
and you should now see a mix of numbers and letters and not ????? and now adb shell should connect
Issue when I try sh fix_permissions it says it can not find the file
Resolution: This is normally caused when you have not mounted /system [via phone]
or you did not use sh /sbin/fix_permissions [or be sure to do cd /sbin before sh fix_permissions
Issue: I get UID Read-only variable error and fix permissions does not run
Resolution: This is normally caused by either not mounting /system [via phone]
or not using sh fix_permissions.
Issue: Some of my apps are listed as /data/blah and it says it can not find the file
Resolution: This is normally caused by not mounting /data [via phone]
Issue: CWM will not mount /system or /data saying it can not find or read them
Resolution: I have found CWM does not like to load mounts once they are encrypted. If you have encrypted your device /system and /data are affected, try unencrypting your phone and trying again.
(this is a good thing it shows third parties tools trying to get around booting OS to read data will not be able to get at the information in your phone)
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

SEE This post for the current script
http://forum.xda-developers.com/showpost.php?p=25023284&postcount=22
Sent from my SAMSUNG-SGH-T989 using xda premium

Well judging by the title that you have there referred to running the script via recovery adb to begin with.
A lot of users don't realize if fix perms says complete in 2 secs it had a problem so I didn't know of that thread, but hope this will be a catch all for fix perms and not just for those who already tried via recovery and adb shell and got that specific error.
Thanks for looking out though
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

jangst123 said:
This is already and has been in the Q & A section.... Not development, but I wish the developers would look at it and figure out why we have issue on ICS
http://forum.xda-developers.com/showthread.php?t=1595806[Q] Problem with Fix Permissions (line 64: UID readonly variable) [WORK AROUND FOUND]
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I think posting this in Dev section is perfect sense. Also, thanks for the fix. This has stumped me for a while trying to figure out what to do.

When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?

Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem

would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?

Dougshell said:
would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?
Click to expand...
Click to collapse
+1 I'm completely stumped!

I can't get adb to even reconize the damn phone im on ravers remix to ics

peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
turn on debugging

RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
Raverx3x any idea why we are having this problem!?
Should we be running a different fix_permissions on ICS?
Also see..
http://forum.xda-developers.com/showthread.php?t=1595806
being that we seem to be determined to have this discussion in 2 different threads

l-levit said:
Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem
Click to expand...
Click to collapse
Or you could have devs talk here and keep users in QA so this doesn't get flooded with chatter.
Our should we delete all those ROM threads in Dev that exist in QA as well?
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

OGWisdom said:
When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?
Click to expand...
Click to collapse
Did you forget to mount /data in mounts and storage (on phone) before running?
Did you encrypt your device? I have CWM fail to load mounts after encryption
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

Oh and other thread just ganked my fix which is cool but I did this on my own not in response to anything so seeing as how I had to put in 2 hours of actual research, scratching my head, trying many different ways and seeing as how this is more of a process then simply loading a script I wanted to maintain it here until I can edit script or another Dev does making it cleaner and easier to manage and thus ready for more casual users found in QA threads.
Sheesh, sorry I figured this out maybe next time I won't pass on the info for fear of debating where it should be posted rather than the content and how to make it better going forward.
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]

u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information

peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
I have instructions on that issue on post.
Did you run adb devices and get ????? unknown device?
I had to run terminal as administrator, then I issued adb kill-server and reconnected phone and then did adb devices again and then it will say starting adb blah blah blah and then I got 6f7y88 [made up it should be a series of numbers and letters and no ?]
make sure adb devices gives you a valid response and not ????? I have found I almost always have to connect phone twice and at least do the above [with regular terminal I only used admin on first run but there in case it does make a difference].
So everytime I conect [or just about] I have to connect the phone
run adb devices get ????? and then
Disconnect USB
on phone in advanced menu choose restart recovery
on computer adb kill-server
Reconnect USB
Run adb devices and get a good serial number listed
I have to do actual work for a couple hours and then will be cleaning up main post on top and adding that bit in a place it get noticed more easily bear with me as I make my boss happy [he is wondering why things aren't getting done round here now ut-oh LoL] then I will clean up the information.

l-levit said:
u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information
Click to expand...
Click to collapse
Um, actually I just noted they used my solution and said it was cool to do so, it appears you have an axe to grind with me and are just nit picking anything I say. I am sorry if yoyu do not feel my work is not to the same level as other folks, but since I put in work and this is more of a manual fix you have to work at rather than an easy to use script [yet], I did not want to post it in QA and all until I have something better for general release.
Also, I am not mad, just wondering why you would rather start silly arguments over placement of usable useful information rather than helping to make said information better and more stable for release to others.
Are you mad I figured this out and posted it before you or something as I have never talked with you and given you no reason to troll my threads?
When I do have a stable script [well at least semi stable for release to dev then more stable for QA]. The way I view QA is for general users questions and answers and since I was going to work on DEVELOPING a script that does work I was holding off on a QA thread, once I do get a script together I will be releasing it. In the meantime I was hoping to have more advanced users and devs dissect my process here and give me feedback towards a full script.
ALSO, by using sh /sbin/fix_permission OR doing cd /sbin and then fix_permissions you negate any need to do any path variable adjustments BUT if you rather then here is how...
when in adb shell before anything
PATH=$PATH:/sbin
export PATH
will then make it so you can just fix_permissions regardless of where you are in directory tree [but so will sh /sbin/fix_permissions so either way is up to you]
or if you are reffereing to adb on the computer
in Windows with command prompt open
set path=%path%;C:\android-sdk\platform-tools [or adjust for where you saved adb]
so if setting a batch program you could use the following to copy/paste [just adjust directories if you saved files differently]
The following is off the cuff until I begin writing the full script and automate things but it is a very basic start
Code:
@Echo Off
Set Path=%PATH%;C:\android-sdk\platform-tools
adb devices
Echo If you see ????? then restart recovery and reconnect the phone
Echo and run adb kill-server and re-run this batch script
pause
Echo when you hit any key this will start adb and put you in the shell you
Echo Will have to run fix_permissions -l -r manually
Echo Be sure to mount /storage /data via phone first
adb shell
or in Linux [OSX should be similiar if not the same]:
from terminal
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved adb
export PATH

No it just bothers me when people ignore the rules and the Developers! Raver even told you were it belonged, and you chose to ignore Raver and the rules!
The fix will be to modify recovery for use with ICS on our devices or a modified fix-permishions script baked into the ROMS

RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
I did bro just having trouble getting the cmd to recognize adb I have it downloaded I changed it still nothing don't know what the hell is wrong with it but IM fixing to improve on my golf swing on this damn vista desk top !
Sent from my SAMSUNG-SGH-T989 using xda premium

[Q] need help rooting telus GS3

Trying to root it to get the hidden basebands so i can use it on wind mobile. I just switched to lnux and I found this video and instruction set on androidrootz "how to root galaxy s3 on max osx/linux/ubuntu [Jelly Bean] US/Canadian" (can't actually post the link because i'm apparently still new)
having some problems, the root isn't taking properly. I keep getting this readout from the console when I try to root the phone.
[email protected] ~ $ cd Desktop
[email protected] ~/Desktop $ cd motochopper
[email protected] ~/Desktop/motochopper $ chmod 755 *
[email protected] ~/Desktop/motochopper $ sudo sh run.sh
[sudo] password for apollo:
[*]
[*] Motochopper: Android root exploit (Linux/OS X version)
[*] v1.1
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well.
[*]
[*] Before continuing, ensure that USB debugging is enabled and that
[*] your phone is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
run.sh: 39: read: Illegal option -n
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
5985 KB/s (1283460 bytes in 0.209s)
[*] Pushing root tools...
6124 KB/s (366952 bytes in 0.058s)
5589 KB/s (1867568 bytes in 0.326s)
5915 KB/s (1578585 bytes in 0.260s)
pkg: /data/local/tmp/Superuser.apk
- waiting for device -
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
run.sh: 83: read: Illegal option -n
everything is fine until that part that I have highlighted in red. suddenly stops and just says failure for no apparent reason. When the phone reboots, I have the superuser app installed but because the phone isnt actually rooted, i can't do anything with the app, just keeps trying to get me to update the su binary (again can't actually do it because the phone is not actually rooted). Anybody know what i can do to make it work properly?
Running telus GS3 32gb with android 4.3
Baseband version
I747MVLUEMK5
Kernel version
3.0.31-2140838
[email protected] #1
Tue Nov 19 19:35:04 KST 2013

This might help: http://autoroot.chainfire.eu/

audit13 said:
This might help: LINK BLOCKED
Click to expand...
Click to collapse
I just read through that page you posted, I do have KNOX on my GS3, and it says that using the CF autoroot on a KNOX device will trip the KNOX void warranty.... is that going to cause a problem with actually rooting the phone or is it just going to void the warranty and they wont cover it if it goes sideways?

Loading any non-Samsung software is going trip the Knox counter so, if you have a warranty on your phone, it may be best that you not flash it.

audit13 said:
Loading any non-Samsung software is going trip the Knox counter so, if you have a warranty on your phone, it may be best that you not flash it.
Click to expand...
Click to collapse
what does that actually do then, tripping the knox counter? does it just disable knox completely? also i've had this phone for over a year now so the warranty is completely gone

capp apollo said:
what does that actually do then, tripping the knox counter? does it just disable knox completely? also i've had this phone for over a year now so the warranty is completely gone
Click to expand...
Click to collapse
Knox is security software that Samsung included with the 4.3 update. It's a method of separating work files from personal files on the phone.
Here's a link to pre-rooted stock ROMs: http://forum.xda-developers.com/showthread.php?t=1739426

audit13 said:
Knox is security software that Samsung included with the 4.3 update. It's a method of separating work files from personal files on the phone.
Here's a link to pre-rooted stock ROMs: http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
if i'm not worried about knox though.... will rooting the phone disable knox somehow (also could disabling knox affect the phone in some way)

capp apollo said:
if i'm not worried about knox though.... will rooting the phone disable knox somehow (also could disabling knox affect the phone in some way)
Click to expand...
Click to collapse
I assume you have no warranty because rooting will void it.
Routing will not disable Knox.
If you have access to a PC, you could load a custom recovery, root from recovery, disable Knox from recovery, and you're good.

just tried the same method from a different source with slightly different method of inputting the commands into the console, here's what it looks like this time
Prometheus apollo # cd Desktop
Prometheus Desktop # cd motochopper
Prometheus motochopper # ./run.sh
[*]
[*] Motochopper: Android root exploit (Linux/OS X version)
[*] v1.1
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well.
[*]
[*] Before continuing, ensure that USB debugging is enabled and that
[*] your phone is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
error: protocol fault (no status)
[*] Device found.
[*] Pushing exploit...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
error: device offline
[*] Pushing root tools...
error: device offline
error: device offline
error: device offline
- waiting for device -
rm failed for /data/local/tmp/Superuser.apk, No such file or directory
[*] Rooting phone...
/system/bin/sh: /data/local/tmp/pwn: not found
[*] Cleaning up...
rm failed for /data/local/tmp/pwn, No such file or directory
rm failed for /data/local/tmp/su, No such file or directory
rm failed for /data/local/tmp/busybox, No such file or directory
[*] Exploit complete. Press enter to reboot and exit.
as you can see, it didn't hang on anything, it actually went through what I'm assuming is the entire process, and it even rebooted my phone for me but when i went in to check titanium backup, it told me that I don't have the root privelages enabled.....