Develop Bugs

[Q]Help With Getting passed the adb loop step

Every since the root method came out, I've been trying to root my phone for hours and hours and I haven't been able to. Since this is a problem for quite a few other users, I figured we should have a thread just for this problem since the rooting thread is over 30 pages long at this point.
My problem is that I see the device in offline mode for a few seconds, and after that it displays an empty list again.
What I'd like to know from people who managed to root their phones, if they had to try something different from the instructions to get passed the adb loop step where you have to catch the device in offline mode? What OS are you running (Win, Mac, Linux and x86 or x64)? How many times did you try?

I got past the loop by hitting ctrl c as soon as it detected the device it worked for me. it seems if you let the loop continue and you get device not connected you have to try again. I was able to get this to work consistently twice.
Getting the adb portion of this is what took me the longest in the rooting process.

Had your same problem on Ubuntu
Had same problem on windows 7 64 bit
UNTIL:
installed pda net - then htc sync, then removed android device driver, then installed the (r3) driver from android sdk... the update you can download through their program.
After that it worked like a charm first time.
my best advice is to start running the loop just before you click recovery from the boot loader screen.
Once you got it, theres no need to be quick with control C - it stays there.
- Faylix / local

the PDANET program seems to mess with the offline loop thing.
Once I closed it, it goes through just fine..
The only problem im having is that im getting a E:Failid to verify whole-file signature when i push the update.zip
And also I've used both Windows 7 64bit and XP 32bit to no avail...

My guess is its all about the drivers. I must have mine all mixed up. I am stuck in loop with no device found either. I will try one more time with pdanet off but Ive tried on a pc without it too anyways.
Someone really needs to write an indepth guide like the G1 because drivers arent even meantioned in the guide and I know its a big part of it especially if you have had other android devices before with sdk plus adb. One thing I do notice is all of us with the loop issue have touble with the device showing in device manager. It displays android 1.0 instead of mts or adb whatever it supposed to be. If your device isnt recognized from hboot it wont make the proper jump into recovery. Hence the loop issue. Can anyone with root ellaborate this a bit more?

@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped

shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
You are a godsend. Spent the last two hours trying to time this just right by doing Step 2 and 3 over and over and over. 5 minutes after reading this post - Hello, Clockwork.

Lol
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
I was having some trouble to, I found something else that I was gonna add but it was only on my end... I didn't have the same problem rooting my wifes. I will watch this thread and if I see any more posts I will drop my piece. Im glad someone else could post this before I could.

shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
Thanks Man, I guess I was pressing the Enter button to fast...
Got past eveything except the "SU" it says "Permission Denied"
NM about this post for some reason it started working after I installed "Setcpu". Went in to Terminal emulator and it gives me the # just fine..
For some reason its just ADB that gives Permission Denied..

"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.

AngelsShadow said:
"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.
Click to expand...
Click to collapse
Thank you thank you....
I've been repeating myself over and over regarding this...
It's the Number 1 issue why people can't Root & Flash to the ENGINEER Build!!

Still a no go
Marvin,
I am still getting the two device OFFLINE showing after going into recovery from hboot. I deleted ALL of the HTC SYNC software and drivers and ONLY installed PDAnet. I now can see the MY TOUCH SLIDE device when connected in hboot, unfortunately I still am having the same stupid problem. So since it's not showing android 1.0 anymore and still having the same problems, we might have to explore some other avenues. FOR THE LOVE OF ROOT SOMEONE PLEASE HELP US!!!

If you run loop and go to recovery and only see the device offline a couple times then it goes away, I do not think it is a driver issue at that point. As someone in the root thread explained, the loop is simply trying to catch the device in ADB mode as it's going into recovery. And then, randomly, it will "stick" in ADB mode. Now, I am not sure if there is a difference between our devices for those of us having trouble getting the ADB mode to stick.

Ok, I'm giving up. I have tried this hundreds and hundreds of times. I know I've followed the instructions the correct way (I've seen the video and read countless forum posts). This simply cannot be done on my phone. I am going to take it to the store and try to exchange it, perhaps for a black one.
Does anyone else have any suggestions?

as i posted in the other thread i was having problems trying to get adb "stick" open when i went from the bootloader into recovery so i went into the file explorer and right clicked on my computer then went to manage devices then went to the driver tab then clicked on update driver right before i went into recovery and this is what finally worked for me. the purpose wasnt to change the driver the purpose was to trick my computer into keeping adb open

Re: Getting passed the adb loop step
I had to hit power on phone and enter on pc at almost the same time to get it working. Then I realized that after you reboot, it boots back to your normal phone not recovery and then adb devices it shows up.
-------------------------------------
Sent via the XDA Tapatalk App

Re: Getting passed the adb loop step
Ugh none of these tricks have worked for me.. Still Stuck .. Maybe it's a computer issue.. Guess ill try a friends computer..
-------------------------------------
Sent via the XDA Tapatalk App

Maybe/hopefully someone will find a different/easier way to root these for those of us stuck here. I've also tried, exhausting many many things, everything from timing of hitting loop/recovery, all the way to almost completely breaking the ADB driver on my PC. This is thoroughly frustrating the hell out of me.

By the way, add "ECHO OFF" (without the quotes) to the top of the batch file. It makes it easier to see when it reads out the offline devices.

Re: Getting passed the adb loop step
If you go to settings then pc connection . What seeting should it be? Drive , sync, or charge?
-------------------------------------
Sent via the XDA Tapatalk App

[HOWTO] Complete Linux rooting guide (from stock to custom and back)

This post will no longer be updated and is pretty much for the archives at this point. It detailed the rooting process for Linux users right after the Slide was first rooted. Since then, newer, more foolproof methods have been devised. For those rooting their phones today (or any point since T-Mobile's OTA update), please see this link: http://forum.xda-developers.com/showthread.php?t=780213. It says it's Ubuntu-specific, but the instructions there should apply to any GNOME desktop and any other desktop with slight modification. Thanks for the comments on this thread. I hope it helped.
Most of this is not new information, but it's all in one post for the first time. I post it in case Linux (and probably MacOS) users need clarification on the process. It should keep people from having to dig in deep threads to find all the info needed. I only added the loop.sh for Linux and the partitioning information.
For all the following, I assume that the reader knows how his computer works, but not necessarily Android rooting.
Preliminary Information
1. As always, make backups and take notes. You might want to make a list of installed apps you want to reinstall later, for example.
2. Install adb. Download it here: http://developer.android.com/sdk/index.html. adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
3. Start adb as root. In more traditional Linux distros, this can be done by typing "adb devices" in a root terminal ("su" then "adb devices"). In Ubuntu-based distros, "sudo adb devices" followed by your password should do the trick. You'll get a message about the adb daemon being started. If not, sometimes typing "adb root" or "adb start-server" as root will do the trick.
4. Make sure your phone has "USB Debugging" checked off in Settings > Application > Development
5. It may not make any difference, but I turn off the "disk drive" option, so that my SD card doesn't mount when the phone is plugged in via USB (unless I need it to).
Partitioning the SD Card (Optional)
This is an optional step, as ROMs are coming out now that allow swapsace (virtual memory) and apps2sd (installing applications to the SD-card rather than on the phone's internal memory). Right now, most Slide ROMs support apps2fat32, so the whole card can be left as is (one, big, fat32 partition). If your desired ROM supports apps2sd using an ext2 or ext3 partition, you can save some headache later by doing this step first. If you don't want it, just skip to the next section.
1. Using the package manager for your Linux distro, install parted. GNOME users have a great, graphical frontend to this utility called gparted. KDE users have the KDE Partition Manager available to them. I only have gparted, but the instructions should be similar for all variants. The graphical frontends take a lot of the pain away from using parted (automatically formatting for ext4, for example). For the braver souls, there is a much more detailed tutorial for using vanilla parted from the command line here: http://forum.xda-developers.com/showpost.php?p=4098568&postcount=1.
2. Mount your sd-card, either using the "disk drive" function of the phone, or in an external card reader.
3. Make a backup of your sd-card by simply copying and pasting to a new folder.
4. Start up the partition manager of your choice with root permissions (using gksu or kdesu).
5. Make sure your desktop environment (KDE or GNOME) or a terminal doesn't have a file manager window open to the sd-card partition. You can't unmount a partition that's being accessed.
6. Find out which device node is assigned to the partition by typing "dmesg" in a terminal. The last few lines should tell you how it's assigned. Mine was /dev/sdg1, for example.
7. Using the dropdown menu, select your sd-card partition in parted.
8. Right-click on the partition in the bottom pane of the window and select "unmount".
9. Delete the partition using the same, right-click menu.
10. Now you're left with free space to configure as you see fit. You use the same right-click menu to create partitions.
11. When done, click "apply" and the partition manager will create and format the partitions you've selected.
12. When done, the computer should mount two partitions from the card, one for apps, the other for user data. Copy your backed-up files to the larger partition.
NB: Android phones can work with a smallish ext* partition at the beginning of the card for apps (around 512MB should be more than enough for almost anyone), a super-small swapspace in the middle (no more than 32MB, if any at all--it's up for debate whether the Slide benefits from swapspace at all), and the rest of the card formatted as FAT32 for the "normal" partiton. I'll leave those decisions to those who have the need and desire. Also, whether to use ext2,3, or 4 for the apps partition is a matter for debate, and some kernels for other phones didn't support the newer versions at all. All that is beyond the scope of this howto, mainly because I won't be trying it out.
NB2: Eugene has released Koushik Dutta's recovery scripts that can help automate the partitioning process. It can be done directly from recovery, rather than on the computer. I much prefer the old way, as it gives more flexibility. For reference, the post with instructions is found here: http://forum.xda-developers.com/showpost.php?p=6993132&postcount=1.
Getting root (original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1)
The following instructions are "the old way" to gain root. There is a new method found at: http://forum.xda-developers.com/showpost.php?p=7658764&postcount=1 that seems to be a saner process, but I have not tested it as of yet.
1. Download the Slide Root package: http://outboundlink.us/anxo/dr_ta_1...ttp://www.4shared.com/file/IfrPbWG7/Root.html
2. Extract it somewhere convenient (I'm using the Desktop folder here. I'm also renaming the folder "slideroot" to keep things simple).
3. Open a terminal and cd to the slideroot folder you just created.
4. The "loop.bat" file here is of no use to you. Use a text editor to make your own loop.sh file, or edit loop.bat and rename it when you're done. It should contain the following:
Code:
#!/bin/sh
watch -n .50 adb devices;
done
5. Power on the slide while holding down the Volume-down button. This will bring you to the bootloader screen (three droids on skateboards). Plug the Slide in via USB.
6. Just to make sure everything is working correctly, type "adb devices" in the terminal to make sure the system is seeing your phone properly. If so, run your loop.sh by typing "sh loop.sh".
7. Use the Volume-down button on the phone to select "recovery" and press the power button to enter. The terminal will flash a few messages like "offline" and "recovery". When the phone's screen shows an icon of a phone with a red triangle, you know it worked.
8. Press Volume-up and Power together to enter the recovery menu on the phone.
9. Now, back in your terminal, hit "ctrl-C" to cancel the loop.sh script.
10. Type "adb push ota.zip /sdcard/update.zip" and hit enter.
11. Type "adb push update.zip /sdcard" but DO NOT hit enter yet.
12. This step requires some coordination and timing. On the phone, select "run update.zip" and press the power button. When you see a little greenish progress bar at the bottom in the background, hit enter in your terminal.
13. If it worked as planned, the phone will see the keys from the first file you pushed, and then use the file you're pushing now to run clockwork recovery. If not, don't worry. Just repeat. I haven't had to do it more than once yet.
14. Once this is done, reboot the phone from the menu system and wait. You can use "adb devices" in the terminal to see if the phone is detected.
15. Type "adb shell" and look for the "$" prompt. If you type "su" you should get a "#" (root) prompt. Give yourself a pat on the back.
Installing the Engineering ROM (original HOWTO at http://forum.xda-developers.com/showpost.php?p=6821968&postcount=1)
A. Now that your phone is rooted, you can "downgrade" it to the Engineering ROM. This gives a better recovery environment that allows other ROMs to be installed (custom ROMs are signed with the test keys; the original recovery will not install them since it looks for your carrier's keys.)
B. Download two files: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/OsmF_ZD7/ESPRIMG.html and http://www.4shared.com/file/sz0VO2TL/SlideEng-package.html.
C. I extracted the SlideEng-package.zip, copied the contents inside loose to the Desktop, and copied the ESPRIMG file to my sd card.
1. cd to the Desktop and type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
3. Start an adb root shell as above ("adb shell" then "su")
4. Type "cd /data/local"
5. Type "chmod 04755 mtd0.img" and "chmod 04755 flash_image". I didn't change any permissions on the other files in that folder, just in case.
6. Type "./flash_image misc ./mtd0.img" and hit enter.
7. Power off the phone.
8. Holding Volume-down, power the phone back up. The recovery will scan the sd card and automatically detect the update file (from step "C" above) and prompt to install it. Hit Volume-up to install.
9. You're done. Just reboot the phone after the update and you're good to go. The boot process will be a little longer this time around.
Updating the Radio (May be optional) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6856313&postcount=1)
I leave this section here for archive purposes. Since switching the ROM to ChiefzReloaded's OTA in the "Installing a custom ROM" section below, this step is no longer necessary, as it contains the newest radio. Unless you're installing a custom ROM released before the last T-Mobile over-the-air update, feel free to skip this section.
When we downgraded the system to the Engineering ROM, we downgraded our radio as well. The following instructions will bring us back to the stock radio version.
1. Download the following file: http://files.androidspin.com/downloads.php?dir=chiefzreloaded/ROM/&file=Newest_Slide_Radio.zip and copy it to your sd-card.
2. Remember that update.zip way back in the rooting section? The one found in the slideroot package? Copy it to your sd-card as well, if it's not already there. I deleted the one on my sd-card and re-copied it, just in case. It contains the clockwork recovery and can be left on your sd-card for future upgrades.
3. Reboot the phone into recovery (should be easy now.)
4. Select "apply update.zip from sd card" to start clockwork recovery. No looping necessary anymore!
5. From the clockwork menu system, apply the Newest_Slide_Radio.zip file you just copied over.
6. Once that's done, just reboot. The boot process will take longer and you'll see a few crazy icons before the system finally loads up. When all is finished and you're back to the home screen, the phone will pop up a dialog telling you the update was successful.
Installing a Custom ROM (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6827968&postcount=1)
For this install, I'm using the new OTA update rooted by ChiefzReloaded. Complete information on this ROM is here: http://forum.xda-developers.com/showpost.php?p=7534163&postcount=1. Like the older SLIDEMEROOT2 I had here before, I picked it because it's mainly the same, stock ROM the phone shipped with, but with root. I had way too many "fast, stable, feature-packed" custom ROMs on other phones that really weren't that fast or stable. I don't want to lose the use of my camera/camcorder to have live wallpapers, for example. These instructions will work for any custom ROM (adjusting for the new ROM in step 1 and 4.)
1. Download the following file: http://db.androidspin.com/androidspin_filedownload.asp?release=330&type=1 and copy it to your sd card.
2. Boot the phone into recovery mode.
3. From the recovery menu, select "apply update.zip from sd card". As stated earlier, this update.zip file contains the clockwork recovery. Applying it like an update will always load clockwork from now on.
4. In the clockwork menu, select "apply any zip from sd card" and select CR_Mod_1.35.531_OTA.zip.
5. Let the update take its course, reboot, wait, and enjoy.
Going Back to Stock (Just in case) (Original HOWTO at: http://forum.xda-developers.com/showpost.php?p=6994424&postcount=1)
There may come a time when you might need your phone just the way it came from the store. It could be that you're tired of custom ROMs, a feature you find you can't live without is broken, or you need to return the phone for warranty purposes. If it gets to that point, here's how:
1. Download the following file: http://outboundlink.net/anxo/dr_ta_1/goto.php?DR_id=1359&linkout=http%3A//www.4shared.com/file/x7HRRsbM/ESPRIMG_2_.html and copy it to your sd-card.
2. Reboot the phone into recovery (just the regular one, not clockwork). The file will be automatically detected.
3. After checking the file, you'll have to hit Volume-Up to confirm the flash.
4. Once done, reboot and the Slide will be good as new.

Very nice!
I kind of wish I would have seen this before I rooted this morning!

I just rooted mine this afternoon. Figured I'd put it up while I still had it in my head.

Excellent summary!
I also wish I'd seen this before muddling through the other guides myself. Thanks for posting it!

Quick question. I plan on rooting my MyTouch Slide within the next couple days. I was just reading over your list and thought I'd try to move the adb file first. After I moved it to /usr/local/bin, and then opened a root terminal. I typed "adb", but nothing came up about a dameon being started. It looked like I had asked for the man page. Any idea why? Or if it started it anyway?

The first time you run adb, do so as root "sudo adb devices", "sudo adb root" or the equivalent. It will start the daemon. A normal user (ie, not superuser) will not have the permissions to start a daemon.
When you run just "adb" without any options, it shows you the command-line options you can use with adb. Most Linux command-line apps work the same way when run without options.

beartard,
huge props to you. this is, by far, the best guide for rooting anything that i have ever used, and certainly for the slide.
as mac osx is a *nix system, this worked great. none of the steps were missing, everything was a normal sized font, and left justified, and took me from the stock to a custom rom flawlessly.
thanks a bunch.
really.

I'm very glad it worked for you. Thanks! Did you have to do anything differently under MacOS? I used to use it before OS X came out. I know the newer versions are based on *nix, but I didn't know how similar they were underneath.

I didn't do very much differently.
I started with "How to get Root" section, as I didn't want to partition my sdcard and already had the SDK installed (obviously, though I really need to look into working with it more, as right now it scares the bejesus out of me).
I used a "do while [1]" style (I love accidentally rhyming) loop.sh file though, mostly because my terminal couldn't understand "watch" for some silly reason.
Your guide was just the one that felt the least like a tween myspace page (no offense to the other guides).

Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.

sultan.of.swing said:
Ok, I am re-rooting my slide after having to get a replacement. I am trying to get it done using the newest ubuntu. I am a newb to ubuntu but I was able to get adb setup. When the device is booted up normally I can adb devices and recognize the device.
When I boot the phone into fast boot and adb it does not find anything. I went ahead and ran the loop.sh file and started recovery And saw the device pop up for a split second so I CTRL-C.
It does the same thing that it did when I rooted my old slide With XP. It saw the device but as soon as I CTRL-C its gone. I can do a battery pull, rerun the loop and boot into recovery and it wont find it.
Is this crap gonna be the same as on windows where you just gotta get lucky and get it to recognize? Sit here for hours on end every day until it gets recognized?????
By the way I am running everything as Root by typing sudo su in terminal before I start.
Click to expand...
Click to collapse
I'm not sure what the problem is, man. I've never had to try more than once using the process above. You're using a new install of ubuntu. Do you have adb from the latest sdk?

Just added the link to a new method for rooting and updated a few minor points.

Updated partitioning info to reflect what's actually going on in the MT3GS world.
Changed custom ROM to ChiefzReloaded's OTA, eliminating the need for the "updating the radio" section.

Beartard, I want to say thank you for taking the time for typing this all out. It worked like a charm with not one problem. I have spread your link to others so they can get the same satisfaction I got from this thread. Thanks again

Getting Started [Update 12/23 - OTA Update Install fix for root]

[Update 12/23] For those of you unable to install the new system update, I've found a solution -- scroll down to the update! I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR!
So I figured I'd at least get things started - Credit goes to whomever first tried z4root on their Droid Pro - and to mahst687 for the deodexing.
Lets Begin!
Resources:
Motorola ADB Driver
Android SDK
xUltimate V2.2.2
(Can't post links apparently, sorry -- googles your friend!)
#1 Root:
As seen on numerous android sites already, root is obtainable via z4root in the market. It may not work the first, second, or even third time -- just keep trying, it works I promise.
#2 Bootstrap and Clockwork Recovery
Download and install 'Rom Manager' from the Market. Once installed flash the Droid2 Clockwork Recovery. After flashing, obtain the Droid2 Bootstrapper and install it. Confirm Clockwork Recovery works by booting to recovery via Bootstrap.
#2 Deodex:
Download Android SDK for ADB, as well as the Motorola ADB Drivers posted above. Second, download xUltimate - also posted above. Once everything is downloaded and installed we're ready to begin.
1. Run Main in the xUltimate package - if the ADB drivers installed successfully you should be greeted with a menu containing several options - great!
2. Next run option 1.
3. Run option 2.
3. Run option 3 - sit back and relax for a bit
4. Once option 3 is done doing its thing, navigate to the xUltimate folder, more specifically the "origi_frame", and delete guava.odex
5. Run option 4 - it'll be a short wait
6. Exit the xUltimate
7. Enable USB Mass Storage on the phone and transfer both "done_app", and "done_frame" to the ROOT of the SD card.
8. Once both folders have transferred disable USB Storage, but keep the phone plugged in via USB.
9. Open up a command prompt and browse to the android SDK Tools folder (or where ever your ADB executable is located).
10. Enter the following commands:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
11. If all went well your phone should reboot - which may take a few minutes. Enjoy!
[Update]12/23/2010
For those of you unable to get the new Droid Pro OTA working I have found a solution! You will need:
1)Root
2)Clockwork Recovery
3)System.img from update
4)Current Nandroid backup of your phone
5)ADB drivers and ASDK
So lets begin.
1)Boot into Clockwork recovery and create a backup of your phone.
2)Once complete, mount the phone as USB storage and pull the system.img file from the nandroid backup folder, as well as the nandroid.md5 (KEEP THESE FILES SAFE!!!!!)
3)Obtain the system.img file from here (Compliments of whoopsiedaisy).
4)Replace the system.img file in the Nandroid backup folder on your PHONE.
5)ADB into your phone (preferably still in recovery) and do the following:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-xx-xx.xx.xx.xx
# rm nandroid.md5
# md5sum *img > nandroid.md5
6)If all goes will it should create a new MD5 checksum file utilizing the new system.img
7)Go to the 'backup and restore' menu in Clockwork, and select 'Advanced Restore'
8)Select the correct nandroid backup folder where the new system.img file is located, and then select 'Restore System'
9)Assuming all goes well, go to Settings, About and check your new system version!

Nice, can't wait to try this on my wifes phone after work.
Sent from my ADR6300 using XDA App

Is the second step necessary if you just want root access so you can install Wireless tether, etc?

jayhammy said:
Is the second step necessary if you just want root access so you can install Wireless tether, etc?
Click to expand...
Click to collapse
Not at all. Simply run z4 if all you require is root access (and a host of apps like Wireless Tether, DroCap, Titanium Backup ...)

Can you please post the quickoffice apk from the Dpro so I can put on an DX? Same would go for the software that allows me to Invite attendees to meetings using GAL. It be copasetic if you can.

Thanks a ton! Freaking worked flawlessly on my Droid X.
Nate

Cool. Cant wait to try this on my wife's phone.

I downloaded everything you said and i started my deodex but when i select option 3 in main it tells me "error no odex file" have i done something wrong please advise

Is it really that simple?
I feel like I must be missing something. I just download an app from the market and reboot and I'm rooted?
Also, what is the deodex for? I want to root my phone to install the apps I want and I want wifi tether. Do I need it?
Also, I really want to understand what is going on under the hood, but I don't know where to start. Is there a 'for dummies' tutorial somewhere that I can go to to start understanding what all of this stuff is, so I can make informed decisions for myself about what I want instead of begging for help on internet forums? Thanks in advance for any suggestions.

Is there a way to unroot? I am not rooted but just curious.

rllong1 said:
Is there a way to unroot? I am not rooted but just curious.
Click to expand...
Click to collapse
Yes, Z4Root app allows you to root, re-root, and UNroot.

I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App

I had version 1.1 of z4. I now have the. 3 version and it has the unroot button
Sent from my DROID PRO using XDA App

rllong1 said:
I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App
Click to expand...
Click to collapse
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.

jayhammy said:
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.
Click to expand...
Click to collapse
I was rooted. I had titanium installed and superuser. Z4 ran fine but I had an old version of it. I dont know if that matters but thats all I did. I downloaded the 1.3 version and I now have the unroot button. On the old version there was no option for temp root either. Just root. On the version I have now there is a temp root and perm root button.

Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.

darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Is there a way to uninstall the CWM recovery?

darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?

mynameismolotov said:
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?
Click to expand...
Click to collapse
No need to un-root. This update is for the system portion only and does not touch the userdata. I simply went ahead on the rooted phone, let the OTA update download and install. In doing so lost root, but had no trouble gaining root access again via z4root. Did not have to re-remove any of the bloatware, at least if I remember correctly. Root apps will not need to be reinstalled but you may need to re-give them permission for root access. No danger that I have noticed or can think of.

For anyone doing the update the android method....
For it to work
You must do the adb "new" md5 creation portion with your phone in clockwork recovery for it to work and to not receive the mismatch error...
To do this, reboot recovery... then plug in usb from your computer... during the phone boot into recovery you should hear the alert from your computer that something from usb was plugged in. Finally, use the mount option in recovery to mount sd card to be able to transfer the .img file over to the correct directory then unmount sd card and do the adb commands in terminal window...
I had the same mismatch errors using my windows 7 machine and creating the md5 with android booted
Hope this helps

Rooting 1st time, please advise?

Hi there.
I have a unbranded DHD on 2.3- 2.36.405.8. It's the official leaked version.
I'd like to root & install leeDroids new Rom based upon the official leaked one.
Could you guys possibly help me out?
I don't want to do anything major, but would like to make my phone better now as I can't see much happening after the gingerbread update. Thanks people.
Sent from my Desire HD using XDA App

Had you rooted previously before you installed the update?

Suggest you google gingerbreak to root your phone, then downgrade your phone to an earlier version so you can S-Off and you can then install custom ROMs.
Guide to downgrade http://forum.xda-developers.com/showthread.php?t=905003

Hi guys. Thanks for your response. It means a lot.
I've never actually rooted any device before, never really had the b*lls lol.
I'll check these threads out & give it a shot.
Thank you very much.

There's not much to get your berries shaking, it's just the radio replacement you should be careful with.
First thing you should do is backup your device with either Titanium or ClockworkMod, though you probably need to root in order to do this, and then anything you might do, you can always revert back to what you had.
When you get to replacing the radio version, read instructions extra careful and be sure to do everything by the book (guide) and to check the checksum on the downloaded files. This could brick your device so no extra precaution is unnecessary..
Happy flashing

Hi guys. Cheers for getting back to me.
Before I start could you tell me whether the following procedures that im going to take will or will not be the right ones please?
1st obtain gingerbreak apk and install on my phone using the downgrade guide on xda
once ive done that use file (http://xdafil.es/DesireHD/RUU/RUU_Ac...032_signed.zip) and put on my sd card..... do I rename this file?
2. Once ive downgraded to this, must i perform a ROOT again to be able to flash a new rom?
3. I want to use this ROM - [ROM&KERNEL] LeeDrOiD HD V3.0.2 GB >EPIC!< |5th May | Official GB Sense 2.1 | TV Anim
4. on the 1.32xxx version do I root and use cwm 2 or 3 and just flash the above rom?
5. When exactly do i use the easy radio off tool please? EasyS-OFF_05.zip (747.4 KB, 20804 views)
Sorry for all the questions, but would be very grateful if someone could help
Edit* also after I write this in cmd
adb push misc_version /data/local/tmp adb shell chmod 777 /data/local/tmp/misc_versi adb shell su
Do I write it exactly as it is? Or does misc_version get replaced with the name of the file?
Cheers.

ok.........
so installed and did gingerbreak, it said didnt work, but asked if i would allow super user permissions to which i said yes.
I opened up a cmd and went to downgrade folder ie; c:\users\ajay\desktop\downgrade
this is where the .zip for 1.36.405.6 is kept.
typed in that code adb etc.... and it said unrecognised command batch etc...
Could someone help us out alittle?
Im pretty dumb at this sort of stuff so my apologies guys.
Hope I manage to install a custom rom, but if i cant then thats cool too.
cheers

Here is my guide i have made and compiled together, follow that and you are done.
---------------------------------------------------------------------------------
HOWTO FLASH CUSTOM ROM ONTO GB DEVICE
Downgrade First!
You might need to format your SD card first before installing Gingerbreak, make a backup of your SD card by copying the files to a safe
place on your PC and then goto Settings - SD and Phone Storage - Click Umount SD card - Click Erase SD card - Click Mount SD card after erasing and formating the card has been
completed.
Gingerbreak help thread for problems:
http://forum.xda-developers.com/showthread.php?t=1044765
1. Download Gingerbreak from http://forum.xda-developers.com/attachment.php?attachmentid=578771&d=1303829207 and install it. Then tap root button.
2. You might get force close errors, just click the force close button and let Gingerbreak do it's job
3. Gingerbreak will in the end, usually say that something went wrong that you need to reboot etc, don't reboot! Just leave it open in your phone, and connect your phone to a PC. Charge only, USB Debugging enabled!
4. Download Android Terminal from the Market and after you installed it you can check if you are rooted, by typing su in the terminal, accept the Superuser request if it shows up and Press "Allow", if you get a "#" you are rooted and the Gingerbreak hack worked.
5. Now open up a terminal window(cmd) on your PC and go to the Downgrade folder on your PC where you downloaded the ADB files from at http://forum.xda-developers.com/attachment.php?attachmentid=483902&d=1294492245 , execute the following commands:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
!Now allow SuperUser in phone when dialog comes up!
If you got "#" in the result, you have temporary root! Proceed with commands:
Now type in terminal:
cd /data/local/tmp
./misc_version -s 1.31.405.6
1. Close the terminal window on your PC and set USB connection to disk drive in your phone and download PD98IMG.zip from http://www.multiupload.com/BTJ8KY0KH9 and place it on your SD card, don't extract the zip file!! Do not put the file into a folder of any kind on your SD card.
PLEASE NOTE!! If you can't set USB connection to disk drive you have to reboot the DHD, now you will be able to set USB connection to disk drive and transfer PD98IMG.zip file to SD from your PC.
2. Reboot while holding volume down, it will go to the Bootloader
3. Follow the instructions and Press "Yes" when it asks you if you want to flash PD98IMG.zip (start the update)
4. Done and reboot.
5. Proceed below with the two S-OFF methods and remove the PD98IMG.zip from your SD.
RADIO S-OFF
1. Install and download latest Visionary r14 from http://www.mediafire.com/?xhwc5m7f273l7b2
2. Open Visionary and tap temproot, then attempt permroot now. Your device will reboot.
3. Connect your phone to a computer (make sure you have USB Debugging enabled, Connect charge only!
4. Extract the Radio S-OFF zip file you dowloaded into a folder on your computer from http://forum.xda-developers.com/showthread.php?t=857537
5. Open my "Desire HD easy radio tool.exe" (Windows 7, right click & run as Administrator).
Choose the first option (RADIO S-OFF, Super-CID and Sim Unlock)
Click "Do it". There may be a SuperUser request on your phone, allow it.
6. Done.
ENG S-OFF(You need this enabled to be able to flash RADIO.IMG later)
1. Download and Extract the eng s-off zip file into a folder on your computer from http://forum.xda-developers.com/showthread.php?t=855403
2. Connect the phone to your computer in "Charge only" mode
3. Run "Desire HD easy s-off.exe" from the extracted folder
4. Click "I have RADIO S-OFF" (as you already done RADIO S-OFF earlier), IMPORTANT!
5. Click in "S-OFF" it
6. Your phone is now ENG S-OFF
7. Done
Flashing your ROM
1. Connect your phone using "Disk drive" to the computer.
2. Copy both your full-wipe-1-3.zip from http://dl.dropbox.com/u/15057375/mero01-xda/Wipe/FULL-WIPE-1.3.zip and your CUSTOM ROM zip file to your SD Card
3. Check again that both files are on your SD card because once you full wipe, you won't have a ROM anymore.
4. Disconnect your phone from your computer
5. Install and open Rom Manager from the market
6. Tap on Flash ClockworkMod Recovery and download version 3.0.2.6
7. Wait for it to download (You need a wi-fi or data connection)
8. After it is done press "Reboot into recovery"
9. If you get an icon with a phone and an exclamation mark in a triangle, remove the battery from your phone, reboot and then flash the clockworkmod recovery again
10. Once you are in the clockwork mod recovery, you may use the volume keys as directional keys (up and down) and the power button may be used as Enter.
11. I recommend you do a nandroid back-up. You must have at least 1 gb of free space.
12. Goto Backup and Restore and make a backup of current ROM if something would fail during flash.
13. Select "Install Zip from sdcard"
14. Select "Choose zip from sdcard"
15. Select full-wipe-1-3.zip (It's right under those folders)
16. Confirm by selecting the Yes option in between those "NO"s
17. Wait for it to finish
18. DO NOT REBOOT!!! In case you were not aware, you now have no rom installed
19. Once again select "Install Zip from sdcard"
20. Select "Choose zip from sdcard"
21. Select your rom zip file
22. Confirm your selection (just like with the wipe)
23. Wait for it to finish
24. Please reboot from the recovery menu and flash nothing else before you have rebooted.
Flash recommended Radio for your custom ROM:
1. Download "Radio Flash.zip" from http://www.mediafire.com/?b172o4ftj1mcpn1 and extract it contents on your PC.
2. Put the radio.img file you downloaded for your custom ROM and put it in the same folder as you extracted the "Radio flash.zip" file to.
3. Make sure USB debugging is enabled in your Desire HD before proceeding.
4. Connect your DHD to your PC with the USB cable and make sure you select USB Charge Only!
5. Now goto the Radio flash folder on your PC and execute "Start here.exe"
6. In the terminal window that comes up you will type:
adb reboot bootloader
Your DHD now goes into Bootloader state, when it is in bootloader state you will type:
fastboot flash radio radio.img
When the terminal says that the process is done you will type:
fastboot reboot
7. Now the DHD reboots and everything is done.
!!GOOD TO KNOW!!
TESTING BEFORE FLASHING ANYTHING
Testing Root
1. Download Android Terminal Emulator from the Market
2. Run it and type in "su"
3. Accept the Superuser request if it comes
4. A "#" should appear if nothing is wrong with your root!
Testing Eng S-off and Radio S-OFF
1. Power Down Your Device
2. Go to Bootloader
3. If it says Ace PVT ENG S-OFF your phone is ENG S-OFF.
4. use Volume down to get to system info and tap power button to select
5. check CID for CID-11111111 (if you have this all is done 100%)
6. Reboot
Checking the device state:
1. Go to the bootloader (turn fastboot off, turn off phone, hold vol- and power)
2. If it says ACE PVT SHIP S-OFF in the first line, your device is Radio S-OFF
3. If it says ACE PVT ENG S-OFF, you have ENG S-OFF, go to System info
4. If system info CID is 11111111, your device is SuperCID5.
5. And if you can verify either Radio S-OFF or SuperCID (and you did both), it worked fine and you have both of them
6. You can check your original CID by going to radio tool folder with cmd and typing: "adb shell getprop ro.cid"
To go back to RADIO S-ON:(If you want to go back to RUU stock ROM again)
1. Flash stock ROM (RUU)
2. Temproot using Visionary
3. Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
4. Enjoy your factory-state phone

Prodelin said:
Here is my guide i have made and compiled together, follow that and you are done.
---------------------------------------------------------------------------------
HOWTO FLASH CUSTOM ROM ONTO GB DEVICE
Downgrade First!
Install Gingerbreak v1.2 apk which is latest, you might need to format your SD card first before installing Gingerbreak, make a backup of your SD card by copying the files to a safe
place on your PC and then goto Settings - SD and Phone Storage - Click Umount SD card - Click Erase SD card - Click Mount SD card after erasing and formating the card has been
completed.
http://forum.xda-developers.com/show....php?t=1044765
Click to expand...
Click to collapse
THIS LINK IS BROKEN.. can you check it please?

Hi thanks very much
Ill follow this guide now, and hopefully be sorted.
just quickly, where do i get recommended radio? and during...
4. Open up a cmd and go to Downgrade folder, execute commands:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
do i press enter after each line of text?

ajay83 said:
Hi thanks very much
Ill follow this guide now, and hopefully be sorted.
just quickly, where do i get recommended radio? and during...
4. Open up a cmd and go to Downgrade folder, execute commands:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
do i press enter after each line of text?
Click to expand...
Click to collapse
Yes enter after each line
For recommended Radio look into the thread of the custom ROM you will flash, it will say what radio they recommend to their ROM

Hi there.
1st thank you for being so patient with me mate, I appeciate it.
after i typed the 1st line of those commands it wouldnt have any of it. It said....
'adb' is not recognised as an internal or external command, operable program or batch file.
I think I should just leave it. Ill have all the guys on here pulling their hair out coz i cant do the simplest thing lol.
Thanks for your time anyway bud.

Revised my guide to make it easier to read and understand.

ajay83 said:
Hi there.
'adb' is not recognised as an internal or external command, operable program or batch file.
Thanks for your time anyway bud.
Click to expand...
Click to collapse
You need to type adb in the folder you have adb.
If you have adb.exe in folder c:\Downgrade you must go to that folder first and the type adb.

ahh ok.
Thank you very much bud. Legend =)
and where could i get Radio_12.54.60.25_26.09.04.11_M2 please? I read the forum and it seems to be a good recommended one.
I'll give it ago tonight or tomorrow morning and let you know how i got on.
Thanks for all your help and for being patient bud.

ajay83 said:
and where could i get Radio_12.54.60.25_26.09.04.11_M2 please? I read the forum and it seems to be a good recommended one.
Click to expand...
Click to collapse
From the Radio's thread in the development forum.
[EDIT] @Andy: Sorry, not today.

ajay83 said:
ahh ok.
Thank you very much bud. Legend =)
and where could i get Radio_12.54.60.25_26.09.04.11_M2 please? I read the forum and it seems to be a good recommended one.
I'll give it ago tonight or tomorrow morning and let you know how i got on.
Thanks for all your help and for being patient bud.
Click to expand...
Click to collapse
You can get that particular radio from:
http://tinyurl.com/6ynbecn

Mr_JMM said:
From the Radio's thread in the development forum.
[EDIT] @Andy: Sorry, not today.
Click to expand...
Click to collapse
Don't worry you have to be nice all the time. Sometimes It hurts my head being nice. I would of answered the same TBH. Its not like it isn't in a sticky.

Hi there.
gingerbreak worked!
Followed the codes and got superuser access.
I had formatted my sd card prior to doing this btw
I closed the terminal and went to change usb from charge to disk drive and the option had gone. took it out and reinserted and still it wouldnt find it for me to put .zip file on???
It would not show my sd card was there until i re booted?
Its a shame we cant just temproot it with gingerbreak and flash the rooted GB 2.3 leedroid, but then i guess this is where all this -s off stuff comes in right?
I havent got a clue now let alone to begin with lol.
Lads I think i give up =( . Thanks for all the help and advise and patience but your dealing with abit of a numpty here and we could be here a very very long time.
I appreciate all the help & Ill keep my eyes open if a way comes out to permroot 2.3 without downgrading etc...

ajay83 said:
Hi there.
I closed the terminal and went to change usb from charge to disk drive and the option had gone. took it out and reinserted and still it wouldnt find it for me to put .zip file on???
It would not show my sd card was there until i re booted?
Click to expand...
Click to collapse
Same thing happened me, i had to reboot to make SD card show up again, but that is no problem as you have already changed misc_version with adb, you can now just put the PD98 file to the SD card and reboot and flash from bootloader.
Easy.
You have come along way now, just do as i said earlier, the rest is easy, don't give up now

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/