Root [Guide] How to flash the ZV9 update: Step by step

[tli]

Here's the ADB command output. ...

H:\>adb shell ls -l da*
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
opendir failed, Permission denied

...

This output is odd, while the rest are normal. Just one more ADB command; please post its output:

adb shell ls -l

Are you able to boot up the phone? What's its baseband version now? ZV9?

 

[zender]

Here's that output:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\>adb shell ls -l
dr-x------ root root 2012-10-16 12:15 config
lrwxrwxrwx root root 2012-10-16 12:15 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-16 12:15 acct
drwxrwxr-x root system 2012-10-16 12:15 mnt
lrwxrwxrwx root root 2012-10-16 12:15 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-16 12:15 etc -> /system/etc
drwxrwx--x system system 1969-12-31 17:59 persist
drwxrwx--- system cache 2012-10-16 12:10 cache
drwxr-xr-x root root 2012-05-02 12:39 system
drwxr-xr-x root root 1969-12-31 18:00 sys
drwxr-x--- root root 1969-12-31 18:00 sbin
dr-xr-xr-x root root 1969-12-31 18:00 proc
-rwxr-x--- root root 9459 1969-12-31 18:00 init.thunderc.rc
-rwxr-x--- root root 15967 1969-12-31 18:00 init.rc
-rwxr-x--- root root 4817 1969-12-31 18:00 init.qcom.rc
-rwxr-x--- root root 858 1969-12-31 18:00 init.qcom.post_boot.sh
-rwxr-x--- root root 1677 1969-12-31 18:00 init.goldfish.rc
-rwxr-x--- root root 0 1969-12-31 18:00 init.cappuccino.rc
-rwxr-x--- root root 111924 1969-12-31 18:00 init
-rw-r--r-- root root 568 1969-12-31 18:00 hpfwinit.rc
-rw-r--r-- root root 1039 1969-12-31 18:00 hpfsinit.rc
-rw-r--r-- root root 118 1969-12-31 18:00 default.prop
drwxrwx--x system system 2011-06-20 11:11 data
drwxr-xr-x root root 1969-12-31 18:00 chargerimages
drwxr-xr-x root root 1969-12-31 18:00 bootimages
drwx------ root root 2012-01-08 20:02 root
drwxr-xr-x root root 2012-10-16 12:16 dev
H:\>

Yes, the phone booted up on the step 12 previously and shows baseband version vm670zv9_60401001.

Thanks for all the continued help here.

This output is odd, while the rest are normal. Just one more ADB command; please post its output:

adb shell ls -l

Are you able to boot up the phone? What's its baseband version now? ZV9?

 

[tli]

Here's that output:

...

H:\>adb shell ls -l

...

drwxrwx--x system system 2011-06-20 11:11 data

...

Yes, the phone booted up on the step 12 previously and shows baseband version vm670zv9_60401001.

...

The /data directory seems fine along with it's permissions, but it's odd with that previous command error. Anyway, since the Baseband version is ZV9, then just proceed with Step 13, by using the following ADB command:

adb reboot recovery

The phone should reboot into the recovery screen which should indicate:

CWM-based Revcovery v4.0.1.5

​

If so, it is OK to proceed with the rest of the procedure, Step 13b onward. In spite of the permission errors, the BobZhome recovery was successfully flashed and it stucked, so it is OK to continue.

If not v4.0.1.5, reboot phone and do a factory reset as instructed in Step 13a. Then try again from Step 10 onward. The permission errors most probably prevented the necessary install of a custom recovery, so have to retry until it is successful. As noted in the procedure, it may take multiple attempts...

 

[zender]

Thanks for your help. It's still not coming up with the orange screen though after the adb reboot recovery command. I've done the steps four times and get the blue screen with this text each time:

android system recovery <3e>
android system recovery utility
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition

The /data directory seems fine along with it's permissions, but it's odd with that previous command error. Anyway, since the Baseband version is ZV9, then just proceed with Step 13, by using the following ADB command:

adb reboot recovery

The phone should reboot into the recovery screen which should indicate:

CWM-based Revcovery v4.0.1.5

If so, it is OK to proceed with the rest of the procedure, Step 13b onward. In spite of the permission errors, the BobZhome recovery was successfully flashed and it stucked, so it is OK to continue.

If not v4.0.1.5, reboot phone and do a factory reset as instructed in Step 13a. Then try again from Step 10 onward. The permission errors most probably prevented the necessary install of a custom recovery, so have to retry until it is successful. As noted in the procedure, it may take multiple attempts...

 

[tli]

... It's still not coming up with the orange screen though after the adb reboot recovery command. I've done the steps four times and get the blue screen with this text each time...

OK, I think the procedure may be missing one other step...

After rebooting and doing a factory reset, download and run an app that utilizes the phone's accelerometer, such as the Vibration Meter by Smart Tools co. I believe this is necessary to initialize some of the needed configuration files and possibly also setup and/or create the needed /data/amit/ directory as part of the Gordita exploit. Not sure if this is the issue but this step is currently missing from the procedure. Please try again with this extra inserted step... fingers crossed, as I'm out of ideas.

 

[AndyOpie150]

It didn't install the custom recovery. It's showing the stock recovery. It might not be rooted either.

Did you follow the ZV9 update portion exactly? You have to do the update twice then continue with rooting and installing the recovery.

Go back and run the update as per instructions. Then continue with the rooting and recovery portion.

 

[zender]

Thank you both for the continued assistance.

I Have done this and still having the exact same behavior with the permissions denied messages running gordita.bat and then boot only to the orange screen.

OK, I think the procedure may be missing one other step...

How can I confirm that it's the stock recovery? I've followed the procedures exactly several times now and again just now and am starting to think that I have an unrootable device. Is that possible?

It didn't install the custom recovery. It's showing the stock recovery. It might not be rooted either.

Did you follow the ZV9 update portion exactly? You have to do the update twice then continue with rooting and installing the recovery.

Go back and run the update as per instructions. Then continue with the rooting and recovery portion.

 

[tli]

Thank you both for the continued assistance.

I Have done this and still having the exact same behavior with the permissions denied messages running gordita.bat and then boot only to the orange screen.

How can I confirm that it's the stock recovery? I've followed the procedures exactly several times now and again just now and am starting to think that I have an unrootable device. Is that possible?

Hey, this would be good news if the phone is booting into the orange-colored recovery screen!!! That indicates that the custom recovery (BobZhome v4.0.1.5) was flashed successfully and it stucked. The blue-colored recovery screen you'd described previously is the stock recovery. The OV with the ZV9 update is rootable as many users have followed this rooting procedure and successfully rooted their phones. Thus, it's not likely your phone...

 

[AndyOpie150]

I think the problem lies in the way the android SDK and the path to the adb.exe where set up. Could be he needs to set the path to the java.exe as well.

If you have only 4-5 options in the recovery, it's the stock recovery. If you have 8-9 options in the recovery, then it's a custom recovery.

 

[tli]

I think the problem lies in the way the android SDK and the path to the adb.exe where set up. Could be he needs to set the path to the java.exe as well.

...

I don't believe so, as he is able to issue ADB commands with appropriate output responses from the phone. If it was a path issue, none of that exchange would have worked in the first place.

 

[AndyOpie150]

Good point.

I guess we are going to just have to pick his brain. It should work flawlessly.

Zender: Could you give us a rundown on exactly what you have installed to your phone and computer so far (as far as the tutorial is concerned), and how they are configured (just the stuff for this tutorial). Did you check the MD5 sum of the downloaded Gordita root exploit? If not download an MD5 sum checker to your computer and download another Gordita root exploit and check it. If it's good try it one more time.

Something else you can try is EManUL3XXX's Optimus V root.zip which has the Gordita Root zip plus the BobZohme VM670NH recovery.img. This is packaged as a 3click root guide and worked flawlessly for me when I flashed the ZV9 update 3 different times.

Note: It can be found in the All Things Root sticky under "Root Exploits". Use the "even more mirrors" link.

 

[tli]

... Did you check the MD5 sum of the downloaded Gordita root exploit? If not download an MD5 sum checker to your computer and download another Gordita root exploit and check it. If it's good try it one more time.

...

Corruption of the Gordita.bat file is highly unlikely either, since it was clearly demonstrated that the file ran through completion with all the proper echo outputs and script command responses back from the phone--even if they were permission errors. Again, if the file was corrupted in any way, none of that would've worked at all...

Anyway, you're right in that we need to understand the exact details as to what the OP did, step-by-step--or did not do--so to see where he strayed from the procedure. I would recommend the OP run the Gordita exploit commands manually (copy-n-paste) instead of using that bat file. This way he can be sure that the phone indeed have sufficient time to fully boot up before executing subsequent commands to flash the custom recovery.

Chance of file corruption is greater for the ZV9 update.zip file than the bat file since it's a much larger download. Thus, verify the MD5 for that zip file, start over fresh from the beginning, and reflash that zip update in accordance to the procedure--TWICE, followed with factory reset each time. Re-read and follow the procedure precisely... or hopefully, the OP might have better success with that other 3-click procedure you've suggested.

 

[brotherswing]

Permission denied running the bat? Right click on it and choose run as administrator.

 

[tli]

Permission denied running the bat? Right click on it and choose run as administrator.

Matters only if the errors were Windows permission errors... The OP's errors are from his phone--Android permission errors as a result of the ADB shell commands issued via running the bat file.

 

[zender]

I've installed the LG Optimus V USB drivers on my PC (WIN XP) as well as Java and ADB. The default paths are employed and I am successfully able to communicate with the phone using the ADB commands. I've also installed the ZV9 update to my phone and that was done previously, which is why I'm attempting to make the gordita solutino work. I've tried running the one-step gordita.bat process as well as the individual commands and I get the same results from both efforts time and time again. Is this helpful? Thanks again for your help.

Zender: Could you give us a rundown on exactly what you have installed to your phone and computer so far (as far as the tutorial is concerned), and how they are configured (just the stuff for this tutorial). Did you check the MD5 sum of the downloaded Gordita root exploit? If not download an MD5 sum checker to your computer and download another Gordita root exploit and check it. If it's good try it one more time.

 

[AndyOpie150]

Try this version found here: http://androidforums.com/optimus-v-all-things-root/531810-rooting-2.html#post4226913
Use the Even more mirrors link.

 

[zender]

Will do, but think I have a problem now from the multiple attempts. When I go to my sound settings now only 'silent' shows up as an avaialble ring tone. I've somehow lost all the stock ringtones. Anybody know how to get them back or if this is possibly related to all these failed attempts?

Thanks,
zender

Try this version found here: http://androidforums.com/optimus-v-all-things-root/531810-rooting-2.html#post4226913
Use the Even more mirrors link.

 

[tli]

Will do, but think I have a problem now from the multiple attempts. When I go to my sound settings now only 'silent' shows up as an avaialble ring tone. I've somehow lost all the stock ringtones. Anybody know how to get them back or if this is possibly related to all these failed attempts?

...

Chance of file corruption is greater for the ZV9 update.zip file than the bat file since it's a much larger download. Thus, verify the MD5 for that zip file, start over fresh from the beginning, and reflash that zip update in accordance to the procedure--TWICE, followed with factory reset each time. Re-read and follow the procedure precisely ...

I suspect there's a problem with your /data directory which would explain the quirks you're seeing now... The following error had bugged me before and it still does...

Here's the ADB command output. ...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\>adb shell ls -l da*
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
opendir failed, Permission denied
...

 

[AndyOpie150]

Have you tried going to a point before you started doing all this using a restore point in the recovery option on your computer?

 

[zender]

Thanks AndyOpie150 for your continued help. I'm sorry for the delay in respondign here, but have been without a computer for almost two weeks and am finally back to attempting to root.

Have you tried going to a point before you started doing all this using a restore point in the recovery option on your computer?

I have and got the sound thing worked out now.

Try this version found here: http://androidforums.com/optimus-v-all-things-root/531810-rooting-2.html#post4226913
Use the Even more mirrors link.

Tried this other thread and issues are the same with the permissions denied messages and doesn't boot to the right screen.

 

[AndyOpie150]

Sorry for the delay in my response. Just moved. Mouse is wireless and rechargeable batteries died. Can't remember what box charger/freshly charged batteries are in?

Using phone.

If neither of the methods worked (both use the Gordita root exploit), and your having permission problems. Try right clicking on the second method and selecting properties, then permissions. Select to allow as exacutable. Then try it again.

 

[Ucardmaster]

Was gonna try this but the ADB link no longer works, got the rest though

 

[tli]

Was gonna try this but the ADB link no longer works, got the rest though

Try this instead:

http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081

 

[AndyOpie150]

I'm glad this was mentioned.
I personally need to change to Mediafire. The SDK I added instructions to is on Box. Their saying I have run out of bandwith.

I'm going to upload one with the fastboot exe in the platform-tools folder where It should be, along with instructions on how to set path manually.

 

[tli]

I'm glad this was mentioned.
...

I'm going to upload one with the fastboot exe in the platform-tools folder where It should be, along with instructions on how to set path manually.

Might not be needed... as the Minimal-SDK Installer might do it all automatically:

[TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers

FYI.

[Edit] Just got a chance to check, it's a nice all-in-one easy install, but the path must still be manually set. [/Edit]