Device(s): Rooted GSM Galaxy Nexus with custom Android 4.2.2 AOKP ROM | Retired Optimus V
Carrier: T-Mobile USA
Thanks: 987
Thanked 1,066 Times in 696 Posts
[Guide] How to flash the ZV9 update: Step by step
Special shout-outs: Thanks Jcase and Jerryscript for cracking the security so it is possible to install the new radio and have root access. A very special shout-out to Brotherswing for putting together the original ZV9 update guide, for testing the Bobzhome, tvall and mgr666 kernels, and for also urging me to edit the guide, add more information, and to repost it. Thanks to tli for helping me fix inconsistencies in the guide. And to the Android Forums community members for making this place so awesome.
The usual warning: Only install this update if you have call quality issues (or if you wish to return completely to stock). The ZV9 radio is part of a security update from Virgin Mobile and it *will* remove root access. Be aware that this update has caused a few problems (such as random reboots while sending texts). If you intend to install a custom rom afterwards, you will need to make sure you run a ZV9 compatible kernel. The Bobzhome, tvall, and mrg666 kernels have all been tested by brotherswing, and those are the ones he recommends. Last but not least, I am not responsible if you bork your phone. As long as you follow this guide to the letter you should not have any problems.
What you will need before you begin:
Read this entire guide in full before you begin. Seriously, read it. This ensures you are making an informed decision before you proceed with this process.
Approximately 1 hour of undisturbed quality time where you won't be getting any phone calls.
Full battery (not required but highly recommended).
Get ADB for your PC/Laptop and follow the installation instructions: Download
Get Java and install like any other windows software: Download
Get the USB drivers so your PC can communicate with your phone: Download
Get CunningLogic-GorditaRoot-4win. Unzip all 4 files into the C:\SDK\platform-tools folder: Download Get the official VM USA ZV9 update and put this in the root directory of your SD card (do not unzip!): Download
Bobzhomes recovery: Download
Flash Image GUI app: Download
jcases modified SuperUser zip package: Download
Preparation:
Be sure you have ADB, Java, and the USB drivers already installed.
Test Java by going here.
Test the USB drivers by plugging in your phone to your PC via USB cable. You should see Windows detect the new drivers when it installs them and tells you that "Your new hardware is installed and ready to use."
Now we need to test ADB: On your phone go to Settings>Applications>Development and make sure there is a tick in the box for Android Debugging. Next is to open a command prompt on Windows; click Start>Accessories>Command Prompt. In the command prompt window type (or copy/paste) the following two commands:
Code:
cd c:\SDK\platform-tools
adb devices
You should see something that looks similar to this:
Code:
c:\SDK\platform-tools>adb devices
List of devices attached
A00000123EY678
Leave the command prompt open as we might need it later.
Are you ready? Here we go!!
Stage 1 -
1) Reboot into recovery. Check your current recovery version. If you have CWMT or MultiBoot you will need to change it, or this WILL brick your phone. Use Flash Image GUI (or the BACKside updater if you're running BACKside - thanks Jerry, you rock!) to flash Bobzhomes recovery.
2) Go to Backup and Restore, choose Backup.
3) Once done, click back to the main menu. Choose apply update from sd.
4) Once that is done, choose reboot system now.
5) Your phone may or may not boot at this point. Do not panic if it doesn't reboot. Just pull the battery and boot back into recovery. (Note: You should see the blue Android stock recovery here!)
6) Choose factory reset/wipe data.
7) Choose apply update from sd (yes, again.)
8) Once done, reboot to system.
9) The phone should boot up to the stock rom. You can verify the radio version now by Menu>Settings>About Phone>Baseband Version. It should end in ZV9. If not, stop. Return to step 3, and repeat.
STOP AT STEP 9 IF YOU WANT TO REMAIN UNROOTED WITH THE STOCK VM ROM! Steps 10 through 12 in Stage 2 flashes the Bobzhome recovery to replace the stock VM recovery that was reinstalled by the VM Update.
Stage 2 -
10) On the phone, go to Menu>Settings>Applications>Developement and make sure Android Debugging is enabled.
11) On the PC, navigate to C:\SDK\platform-tools. Double click Gordita.bat. If it doesn't work (or hits an error), open it with a text editor, then copy and paste each line individually into the command prompt window. You can skip the lines that begin with "echo."
11a) If you use the copy/paste method with ADB: When you paste the last line from the bat file and if it worked properly, you should see it mimic something about the recovery in green text in the GUI ADB log window.
12) Wait for it to finish. You'll know it's done when you see "Recovery flashed! Enjoy." (You won't see this notice if you use the copy/paste method.)
13) Reboot into recovery.
13a) If you still see the stock blue Android recovery: do a "reboot system now" and when the phone reboots, go into the settings and privacy menu, and do a factory reset. Once complete, go back up to Stage 1, and begin again. (I had to do this 3 times, so don't panic if it doesn't take the first few times!) 13b)This is important! Do not leave this recovery screen (the text should be orange) until you've successfully completed the following procedure through Step 16. Otherwise you lose this [Bobzhome] recovery and have to start over!
14) Now let's root the phone: choose install zip from sd card, and flash jcases modified SuperUser zip package.
15) Depending on your ROM preference, perform one of the following three options:
15a) If you want the ROM just prior to the VM Update, go to Backup and Restore, choose Restore. Pick your latest backup [that was created in Step 2].
15b) If you want the stock updated ROM with root access, just continue onto Step 16.
15c) If you want a clean start, choose install zip from sd card, and flash any ZV9 compatible ROM (and gapps if necessary.)
16) Reboot. Done!
If for any reason you wish to revert back to ZV5, Sammyz wrote an amazingly easy guide on how to do so here. Thanks Sammy!!
Please post here in this thread if I've forgotten something, need to fix something, need to add anything, something needs clarification, or if links have changed or are no longer working (forum guides/mods/admins can also edit to fix these if they see the need).
Most the IHO based roms are compatible with the update. This includes MiRaGe, Harmonia 2.x, Bobz, magpie, and I believe OM also is using the updated kernel. Add far as I know, the Froyo roms still need the picasticks remix kernel to work properly with the new screen and may not be compatible with the update.
The Following User Says Thank You to riggerman1 For This Useful Post:
Most the IHO based roms are compatible with the update. This includes MiRaGe, Harmonia 2.x, Bobz, magpie, and I believe OM also is using the updated kernel. Add far as I know, the Froyo roms still need the picasticks remix kernel to work properly with the new screen and may not be compatible with the update.
The update works for both screens.
__________________
Steve Rogers: Big man in a suit of armour. Take that off, what are you?
Tony Stark: Genius, billionaire, playboy, philanthropist.
So.. I followed it, and everything seemed fine. I did see ZV9 in step 9, and went all the way to and including step 14.
However, now, it shows ZV4 as the version (which is where I started from).
Is that expected (following the restore on step 14)? which version do I actually have?
(I've had insane reception problems for a little while, hence my desire to go to ZV9. Although, with all these custom ROMs out there, I plan to switch to one of them as well once I get a sense of how well ZV9 is working for me.)
Before you started this guide, what rom did you have? Did you miss the Notes section?
bah.. sigh. i read it, a few times, but clearly not enough! I guess that's what I get for doing this and a few other things at the same time. 14 could benefit from being merged with the notes for clarity.
Well, on the bright side, I can say the restore works just fine! ;-)
Hey Petrah. This Guide does indeed look better than brotherswing's guide. If you would like I can replace his with yours in the All Thing Root Guide sticky (I have already discussed it with brotherswing and he is all for it).
Device(s): Rooted GSM Galaxy Nexus with custom Android 4.2.2 AOKP ROM | Retired Optimus V
Carrier: T-Mobile USA
Thanks: 987
Thanked 1,066 Times in 696 Posts
Quote:
Originally Posted by AndyOpie150
Hey Petrah. This Guide does indeed look better than brotherswing's guide. If you would like I can replace his with yours in the All Thing Root Guide sticky (I have already discussed it with brotherswing and he is all for it).
I wouldn't say it looks better... just some added info to an already wonderful guide (his). But thanks!
Yes the ZV9 should be safe to flash with the xionia recovery. Just download it, use a file manager to move it to the root of your sd card, boot into your recovery, and select "install update.zip". If you want the radio to update to the new ZV9 baseband, you'll have to flash the update one more time from the stock recovery, the reboot. You should then see s message on your screen about flashing the new radio.
note: See edit at bottom. Issue resolved
OK, I followed these steps and flashing worked fine. But now Gingerbreak is gone. Do I need to reinstall to so I can use the unroot command there? Or am I unrooted now? For what it's worth, I still haven't done the factory reset because I'm totally chicken.
BTW, when I boot into recovery it is the stock one: Solid blue, says "Android system recovery <3e>"
and just has the four options:
reboot now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition.
I'm also missing Market/Play. Not sure what's up with that....any ideas how to get it back (or will it come back after the reset).
Sorry I'm such a pain guys. Maybe I should just go through the entire "How to Flash ZV9" procedure (including the gordita.bat steps and such. I'm already at Step 9, anyway.... what's 3 more?
Edit: Finally. It's unrooted, back to stock, and ready to roll. Amazing what happens when you follow ALL the directions and the wisdom of the fine folks here. Big shoutout to AndyOpie150 and Riggerman1 for all their help!!!
And note to myself: "next time you root, take NOTES. Because you're old, dang-it, and you're not going to remember what you did a year ago!"
Last edited by hereusethis; June 14th, 2012 at 10:29 PM.
Reason: resolved!
STOP AT STEP 12 IF YOU WANT TO REMAIN UNROOTED WITH THE STOCK VM ROM!
13) Reboot into recovery.
13a) This is important if you plan to stay rooted or install a custom rom!: Do not leave this recovery screen (the text should be orange) until you've completed one of the two steps listed below in the Notes. Otherwise you lose this recovery and have to start over!
13b) If you reboot into recovery and still see the stock blue Android recovery: do a "reboot system now" and when the phone reboots go into the settings and privacy menu and do a factory reset. Once complete, go back up to Phase 1 and begin again. (I had to do this 3 times, so don't panic if it doesn't take the first few times!)
14) Go to Backup and Restore, choose Restore. Pick your latest backup.
15) Reboot. Done!
Notes:
If you want the stock rom with root access, skip step 14. Instead, choose install zip from sd card, and flash jcase's modified SuperUser zip package. Reboot. Done!
If you want a clean start then skip step 14. Instead, choose install zip from sd card and flash any ZV9 compatible rom (and gapps if necessary.) Reboot. Done!
...
Thanks for the comprehensively detailed guide. I found the above section a bit confusing. Not sure if this edit might be clearer--or even correct--but for your consideration:
Code:
STOP AT STEP 9 IF YOU WANT TO REMAIN UNROOTED WITH THE STOCK VM ROM! [As Steps 10 to 12 in Stage 2 flashes the Bobzhome recovery to replace the stock VM recovery that was reinstalled by the VM Update.]
13) Reboot into recovery.
13a) If you still see the stock blue Android recovery: do a "reboot system now" and when the phone reboots, go into the settings and privacy menu, and do a factory reset. Once complete, go back up to Stage 1, and begin again. (I had to do this 3 times, so don't panic if it doesn't take the first few times!)
13b) This is important if you plan to stay rooted or install a custom rom!: Do not leave this recovery screen (the text should be orange) until you've successfully completed the following procedure through Step 16. Otherwise you lose this [Bobzhome] recovery and have to start over!
14) [To root?] choose install zip from sd card, and flash jcase's modified SuperUser zip package.
15) Depending on your ROM preference, perform one of the following three options:
15a) If you want the ROM just prior to the VM Update, go to Backup and Restore, choose Restore. Pick your latest backup [that was created in Step 2].
15b) If you want the stock updated ROM with root access, just continue onto Step 16.
15c) If you want a clean start, choose install zip from sd card, and flash any ZV9 compatible ROM (and gapps if necessary.)
16) Reboot. Done!
Device(s): Rooted GSM Galaxy Nexus with custom Android 4.2.2 AOKP ROM | Retired Optimus V
Carrier: T-Mobile USA
Thanks: 987
Thanked 1,066 Times in 696 Posts
tli,
After I read what you suggested and compared it to what I had, I noticed right away that your suggestions were spot on. I've added your name to the shout-outs.... thank you!!
This is a great walk through thank you for posting it. I am attempting to update my usb drivers so my phone can communicate with my computer. I downloaded the neccesary files and installed them successfully. Still whenever I connect my phone to my computer is says "Unrecognized device in usb....". Any help with this would be great as I am just learning how to do most of this. Thanks!
Last edited by Josh2903; June 20th, 2012 at 03:02 AM.
Just thought I'd say on stock rom about phone the baseband section is written from the rom alone so even if the radio didn't flash it'll say zv9. The SW version however seems to pull from the radio and will only say zv9 if the radio did indeed flash.
Edit: also backside rom is not zv9 compatible until you flash one of the compatible kernels over it
Last edited by Thewraith420; July 2nd, 2012 at 11:59 AM.
Device(s): Rooted GSM Galaxy Nexus with custom Android 4.2.2 AOKP ROM | Retired Optimus V
Carrier: T-Mobile USA
Thanks: 987
Thanked 1,066 Times in 696 Posts
Quote:
Originally Posted by Thewraith420
Just thought I'd say on stock rom about phone the baseband section is written from the rom alone so even if the radio didn't flash it'll say zv9. The SW version however seems to pull from the radio and will only say zv9 if the radio did indeed flash.
Edit: also backside rom is not zv9 compatible until you flash one of the compatible kernels over it
Thanks!
Quote:
Originally Posted by sammyz
I just wanted to say, you messed up the link, it goes to your comment instead of OP....
I know there's some argument in the other zv9 threads about whether the radio update helps. I internally debated at length about whether I wanted to take the risk of potentially making things worse (VM did pull the update after all), but after reading through all the threads I could find across all our OV forums, I figured I'd take the plunge and worst case I'd hope it wasn't too hard to get my old firmware back.
So I can't speak for anyone else, and obviously conditions will vary depending on your location, cell coverage, OV model, etc., but here's my experience:
My speedtest bandwidth results are 5-10 times faster than they were prior to the update. I get the same results on stock, CM7, and CM9. The following numbers are approximate, but I'll see if I can also get a speedtest with my new results posted.
Before: 200kbps down, 50kbps up - these are the fastest speeds I ever saw, in any location, under any conditions, even metropolitan areas blanketed in 3g coverage. To be fair though, I got those speeds relatively consistently.
After: My very first speedtest (on froyo stock) after flashing the new radio was 1000kbps down, 250kbps up. I've since seen 1750kbps down, 800kbps up in my best test - and I got several test results in a row in that spot ~1500/500kbps down/up.
Signal strength seems slightly better, but I don't have detailed records to compare with my current performance. Similarly, GPS lock seems quicker, but this could entirely be placebo effect. It has *not* helped my pings. The bandwidth though... not placebo. Those numbers don't lie. The radio update gave me a dramatic performance increase for relatively little hassle.
The Following User Says Thank You to ewichern For This Useful Post:
Device(s): LG Motion 4G----
LG Optimus M----------------
LG Optimus V on U Firmware
LG Optimus S
Carrier: MetroPCS
Thanks: 1,694
Thanked 1,645 Times in 1,140 Posts
Quote:
Originally Posted by ewichern
I know there's some argument in the other zv9 threads about whether the radio update helps. I internally debated at length about whether I wanted to take the risk of potentially making things worse (VM did pull the update after all), but after reading through all the threads I could find across all our OV forums, I figured I'd take the plunge and worst case I'd hope it wasn't too hard to get my old firmware back.
So I can't speak for anyone else, and obviously conditions will vary depending on your location, cell coverage, OV model, etc., but here's my experience:
My speedtest bandwidth results are 5-10 times faster than they were prior to the update. I get the same results on stock, CM7, and CM9. The following numbers are approximate, but I'll see if I can also get a speedtest with my new results posted.
Before: 200kbps down, 50kbps up - these are the fastest speeds I ever saw, in any location, under any conditions, even metropolitan areas blanketed in 3g coverage. To be fair though, I got those speeds relatively consistently.
After: My very first speedtest (on froyo stock) after flashing the new radio was 1000kbps down, 250kbps up. I've since seen 1750kbps down, 800kbps up in my best test - and I got several test results in a row in that spot ~1500/500kbps down/up.
Signal strength seems slightly better, but I don't have detailed records to compare with my current performance. Similarly, GPS lock seems quicker, but this could entirely be placebo effect. It has *not* helped my pings. The bandwidth though... not placebo. Those numbers don't lie. The radio update gave me a dramatic performance increase for relatively little hassle.
My max speed is always 200kbps with metropcs on my OM and OV, I'm gonna try the radio update with my OV (which is on metropcs) and I'll see what my new speeds are ^_^
Also there is a way to revert back to ZV5 now, just look in Petrah's last post or the end of the OP.
The Following User Says Thank You to sammyz For This Useful Post:
Sorry, but I am a complete noob. My phone has never been rooted. I have already installed the ZV9 update. I did so back when Virgin told me I needed it as a security update. Now I know I definitely want to root the phone. So my question is, should I follow the steps in this post (but just skip step no. 3)?
Device(s): Lg Op V runnin MiRaGe ROM with Zengarden Recovery
Carrier: Virgin Mobile
Thanks: 298
Thanked 109 Times in 93 Posts
I know nothing about data speeds,but i just did one.
results :
26 Kbps down
176 kbps up
410 ping
Is this good or bad?
I'm guessing bad!!! Thanks for a reply-_-
__________________ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
Failing to prepare ,is like preparing to fail.
…………………………………………………………………………
I know nothing about data speeds,but i just did one.
results :
26 Kbps down
176 kbps up
410 ping
Is this good or bad?
I'm guessing bad!!! Thanks for a reply-_-
I run at least five or six speed tests for a better comparison, but it doesn't look good from what I see.
Device(s): Lg Op V runnin MiRaGe ROM with Zengarden Recovery
Carrier: Virgin Mobile
Thanks: 298
Thanked 109 Times in 93 Posts
Just did 5 tests
ping. 303,266,203,207,150
up. 205,147,251,141,235
down. 40,75,56,70,71
I live on the 1st floor of a 3 story apt. Building.
Tomorrow i'll test at different times and different areas during work.
THANKS!
I apologize, feel free to delete my 2 posts in this thread!
Last edited by badblue1; August 5th, 2012 at 01:26 PM.
Reason: wrong thread!
Maybe you could start a new thread or find the one in the non-rooted side and post in there. After all, this thread is about the ZV9 update procedure, and it would appear as if we are getting close to derailing this thread.
Petrah: The link to the Root download is dead.
The ZV9 root.zip download link here: Rooting
is working.
You might have to refer members there for the rooting process.
I'm following the guide, and I flashed the Bobzhomes recovery and was told it flashed successfully. I'm starting with Backside IHO and the CWM recovery. But, when I went into recovery, it still said CWM - based Recovery v4.0.1.5.
Does this mean that Bobzhomes recovery didn't take? I'm scared to go further because of the warning "If you have CWMT or MultiBoot you will need to change it, or this WILL brick your phone."
You ain't got nothing on me. When I first came to this site last year in May I was the worst newb in the world. Just ask some of the members who where here when I first hit this place.
Didnt' know squat about Android Phones, and just enough about computers to be able to find this site.
I have several questions before I do this. Need answers before I do something that might turn my phone into a paper weight. lol
1. I'm on ZV4, what improvements can I expect from ZV9?
and
2. Will it remove my hotspot? I need it for when I'm away from home and I need the internet on my laptop. I heard there was a security patch from VM that unrooted your phone and removed the ability to use it as a hotspot, really don't want to loose my hotspot. I'm just too cheap to pay for a service that I can get on my phone. lol
Device(s): Personal = LG Optimus V (Virgin Mobile)
Work = Samsung Galaxy S III (Verizon)
Carrier: Not Provided
Thanks: 0
Thanked 0 Times in 0 Posts
I'm a noob, but ready to take the plunge I think. I've already got the zv9 update and am on 2.2.2 so think the Gordita method is for me, but whether I run the bat file or the individual commands they continue to fail with permission errors, i.e., 'rm failed for /data/amit/*, Permission denied'.
Can anybody provide guidance please? Thanks very much for any/all help.
Device(s): Personal = LG Optimus V (Virgin Mobile)
Work = Samsung Galaxy S III (Verizon)
Carrier: Not Provided
Thanks: 0
Thanked 0 Times in 0 Posts
Is it ok that I posted this in an existing thread? Should I have opened a new one instead? Really just looking for guidance as all attempts to root have failed so far.
Thanks.
Quote:
Originally Posted by zender
I'm a noob, but ready to take the plunge I think. I've already got the zv9 update and am on 2.2.2 so think the Gordita method is for me, but whether I run the bat file or the individual commands they continue to fail with permission errors, i.e., 'rm failed for /data/amit/*, Permission denied'.
Can anybody provide guidance please? Thanks very much for any/all help.
Device(s): Personal = LG Optimus V (Virgin Mobile)
Work = Samsung Galaxy S III (Verizon)
Carrier: Not Provided
Thanks: 0
Thanked 0 Times in 0 Posts
Thanks much for your help. Am re-posting here what I sent to you via pm relative to ADB questions.
ADW is installed in c:\sdk\platform-tools. After the initial setup when I typed adb devices after connecting my phone I saw the device and that's when I ran the commands previously and they failed as reported. Now when I type adb devices I don't get anything returned. I've tried reinstalling the drivers and the device still isn't recognized. Also - when I plug in the phone now I don't get the 'usb storage' notification.
Quote:
Originally Posted by AndyOpie150
You posted in the right place as you did use this guide.
let me know about those things asked for in my pm, here.
Delete everything from the SDK and the drivers you used.
Go here: http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip for the drivers. Install with the phone unpluged from computer. When install is finished re-boot the computer to allow the other two needed drivers to be installed. Once booted back up plug in phone to allow the install to finish.
Device(s): Personal = LG Optimus V (Virgin Mobile)
Work = Samsung Galaxy S III (Verizon)
Carrier: Not Provided
Thanks: 0
Thanked 0 Times in 0 Posts
Hi and thanks for the continued assistance. I did as you instructed and am still getting the permission denied messages, but did get the completion of step 12 in the opening post with the message: 'Recovoery flashed! Enjoy".
I'm really unsure what to do now as there are several permission denied messages and I'm unclear on what step 13 is asking me to do with the instruction 'reboot into recovery'. Here's my ADB output and I appreciate very much your continued help. I'm basically where I was when originally posting with the permission denied messages.
Thanks again,
zender
C:\>cd c:\sdk\platform-tools
C:\SDK\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
A0000028EB83A5 device
C:\SDK\platform-tools>gordita
C:\SDK\platform-tools>echo "GorditaRoot 1.0 by jcase / TeamAndIRC"
"GorditaRoot 1.0 by jcase / TeamAndIRC"
C:\SDK\platform-tools>echo "for the VM670 Optimus V"
"for the VM670 Optimus V"
C:\SDK\platform-tools>echo "Recovery taken from http://forum.xda-developers.com/
showthread.php?t=1197991"
"Recovery taken from http://forum.xda-developers.com/showthread.php?t=1197991"
C:\SDK\platform-tools>echo "flash_image stolen from joeykrim fair and square"
"flash_image stolen from joeykrim fair and square"
C:\SDK\platform-tools>echo "-"
"-"
C:\SDK\platform-tools>echo "Pushing recovery to /data/local/"
"Pushing recovery to /data/local/"
C:\SDK\platform-tools>adb push VM670NH_recovery.img /data/local/recovery.img
1234 KB/s (4200448 bytes in 3.321s)
C:\SDK\platform-tools>adb push flash_image /data/local/
150 KB/s (9640 bytes in 0.062s)
C:\SDK\platform-tools>echo "Removing old sensor config, setting up symlink attack"
"Removing old sensor config, setting up symlink attack"
C:\SDK\platform-tools>adb shell "rm /data/amit/*"
rm failed for /data/amit/*, Permission denied
C:\SDK\platform-tools>adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
link failed Permission denied
C:\SDK\platform-tools>adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
link failed Permission denied
C:\SDK\platform-tools>echo "Rebooting to execute symlink attack, to chmod 666 the recovery block device"
"Rebooting to execute symlink attack, to chmod 666 the recovery block device"
C:\SDK\platform-tools>adb reboot
C:\SDK\platform-tools>adb wait-for-device
C:\SDK\platform-tools>sleep 10
C:\SDK\platform-tools>adb shell "rm /data/amit/*"
rm failed for /data/amit/*, Permission denied
Device(s): Personal = LG Optimus V (Virgin Mobile)
Work = Samsung Galaxy S III (Verizon)
Carrier: Not Provided
Thanks: 0
Thanked 0 Times in 0 Posts
Here's the ADB command output. Thanks for your help. I couldn't get them to work until I went through the process of reinstalling the LG drivers and rebooting for the umpteenth time though. Is that how it is supposed to work?
2Likes
[Guide] How to flash the ZV9 update: Step by step
And thank you. 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
