I dont see a velocity toolkit.
Is the velocity toolkit something I install on the phone?
I tried tghis using the term emulator and I it prsented several options.
1) Cosmetic Chnages
2) Perfomance Changes (which is cool. I may try and overclock although i need to read this forum for guidance. Any links to where is this addresses would be appreciated but not nessesary)
3) ROM Utilities
4) Script Options
Which one would I choose to make this update notofication go away?
The velocity tool kit is in velocity 1.1, just starting the scripts and updating them will fix the notifications.
Device(s): LG Ally (Retired), HTC Droid Incredible 2
Thanks: 1
Thanked 0 Times in 0 Posts
I'm unable to make it past step 9. Once the software update reaches 30% completion, it stops to tell me that the USB cable and my phone are no longer connected even though they clearly are. This has happened 4 times, and it always stops at 30%..
Device(s): HTC Incredible,HTC Evo 4G,LG Ally,Huawei Ascend, HTC Incredible 2, Galaxy Tab, EVO Shift
Thanks: 247
Thanked 684 Times in 260 Posts
Quote:
Originally Posted by Broseph7
I'm unable to make it past step 9. Once the software update reaches 30% completion, it stops to tell me that the USB cable and my phone are no longer connected even though they clearly are. This has happened 4 times, and it always stops at 30%..
Nice handle.
I just made an automator for LGNPST, [GUIDE][LGNPST] Alternate V6 Restore Method [Updated 5-24-11] most people that have trouble with the beginning of this process have success starting with LGNPST to get to back to stock, after your phone is restored you can follow this guide starting at step 10
The ally irc channel, i THINK the url is webchat.freenode.net and someone please corfrect me if im wrong and join the ally channel. There pretty much always someone in there to help you out. just know they dont sit there and watch it so you may have to wait but iive always been able to get the help i need in there.
It would be c:\froyo\. . . . Since you didnt put the froyo folder on the root of your c drive, it would be c:\documents and setting\(yourusernamehere)\desktop\and the rest of the directory. Come on guy. This is simple stuff. Just gotta find adb.exe and use the directory after the cd command. Also if you didnt put the froyo folder on the root of your c drive, the batch scripts wont work.
ok i got everything to work its just now im having trouble with the bootloader it keeps saying device not found. so it looks like im gonna have to keep trying at that.
Last edited by Darkstar8101; July 20th, 2011 at 09:27 PM.
ok i got everything to work its just now im having trouble with the bootloader it keeps saying device not found. so it looks like im gonna have to keep trying at that.
The info is here. The fastboot driver is the only part of this guide that i ever had trouble with. Make sure youre using the sdk in this download
Still awaiting a response in that thread about flashing the stock recovery. Given what I've explained as far as my situation with my phone, would I only have to flash the zip of that stock recovery, or do I need to go through the process of flashing a stock nandroid first? Remember, I'm still using stock, as I never flashed a custom ROM or anything. I just downgraded from 2.2.2 to 2.2.1.
Then no you do not need to flash the nandroid. UNLESS you are rooted. If you're rooted and want to go back to unrooted stock you must. or use LGNPST to go to V6 and take the OTA updates
__________________
I'm special as hell!
Quote:
Originally Posted by Trident
You're so banned when I get back from breakfast...
LG VX8300>LG Decoy>LG Dare>LG Ally>Droid2>LG Ally>HTC Droid Incredible>HTC Thunderbolt>HTC Droid Incredible>Samsung Galaxy Nexus I'm located in: Computers&IT, LG Ally, HTC Droid Incredible; AllyIRCMy Blog
Please press button, and please consider donating to my energy drink fund.Thanks!
Quote:Originally Posted by LGAllyGirl Oops! It says underneath that #28 is #10 on this forum.
11. Expand "ADB Bootloader Device" (Might be listed as "Android!" Under Other Devices)
This is where I'm stuck now. I don't see either of these options appearing in my device manager.
Sorry for having a million questions, I'm not very technology savvy!
Originally Posted by LGAllyGirl Oops! It says underneath that #28 is #10 on this forum.
11. Expand "ADB Bootloader Device" (Might be listed as "Android!" Under Other Devices)
This is where I'm stuck now. I don't see either of these options appearing in my device manager.
Sorry for having a million questions, I'm not very technology savvy!
The phone has to be plugged in and in fastboot, blue screen
I'm having this same problem. I don't see ADB Bootloader or "other devices" in my device manager. My phone is plugged in and I have a blue screen on my phone. All I see in the device manager is:
"ADB Interface
Fastboot interface (Google USB ID)"
I'm having this same problem. I don't see ADB Bootloader or "other devices" in my device manager. My phone is plugged in and I have a blue screen on my phone. All I see in the device manager is:
"ADB Interface
Fastboot interface (Google USB ID)"
I don't understand what exactly "fastboot" means.
I'm using Windows 7. What do I need to do?
Fastboot is the phones bootloader. Low level interface between the pc and the phone for flashing (writing) file systems.
Now the drivers thing is tricky, ive hear of a few cases where windows 7 has actually been able to find and hook up the drivers automatically, i did it on a friends pc. This is just a matter of getting the pc to recognize the new device and finding the drivers. Sorry i cant be of much more help, ive had this set up for a while and dont remember the details.
My phone was originally a ZV6 phone which I have updated over OTA updates to 2.2.1 (Have not taken the latest OTA) and is currently rooted. My fastboot does appear to be disabled, as plugging it into a computer and running `fastboot devices` pulls up nothing.
I installed ROMmanager and flashed the amon ra recovery. When I reboot immediately after flashing it, and boot into the recovery, it boots into fastboot instead. In this fastboot mode, fastboot on my computer can see the phone, although `fastboot devices` comes back with:
so I'm not sure how if it's really fastboot or some broken version of it.
so.... I only have a linux machine, which means I can't really do the downgrade method. Could I just boot into this fastboot and flash Velocity 1.1 as if I had fully working fastboot?
My phone was originally a ZV6 phone which I have updated over OTA updates to 2.2.1 (Have not taken the latest OTA) and is currently rooted. My fastboot does appear to be disabled, as plugging it into a computer and running `fastboot devices` pulls up nothing.
I installed ROMmanager and flashed the amon ra recovery. When I reboot immediately after flashing it, and boot into the recovery, it boots into fastboot instead. In this fastboot mode, fastboot on my computer can see the phone, although `fastboot devices` comes back with:
so I'm not sure how if it's really fastboot or some broken version of it.
so.... I only have a linux machine, which means I can't really do the downgrade method. Could I just boot into this fastboot and flash Velocity 1.1 as if I had fully working fastboot?
Because you already have fastboot, there is no need to downgrade. All you need to do is use fastboot to flash the latest amon ra recovery and then boot into recovery and use that to wipe and flash Velocity 1.1
The Following User Says Thank You to Sora1995 For This Useful Post:
Once I reboot the phone normally, I have to reflash the recovery to get it back ... and I can only access it by using the 'reboot into recovery' option in ROMmanager.
Once I reboot the phone normally, I have to reflash the recovery to get it back ... and I can only access it by using the 'reboot into recovery' option in ROMmanager.
Fastboot is permanent. if its locked you can still get in it if you try to boot into recovery abd its messed up, but if you have a phone shipped with zv6 and never used lgmu to update you have fastboot. Your recovery isnt sticking. NOT fastboot, there is a file /system/ect/install-recovery.sh that overwrites the recovery with stock. This is why it isnt sticking. You can delete the file or flash velocity because it isnt in there. But ROM manager is far from the best way to flash your recovery
The Following User Says Thank You to KingOfGreen For This Useful Post:
alright. I moved the install-recovery.sh to disable that and wrote over the stock recovery with the flash_recovery tool. Rebooted the phone and it dumped me into fastboot, so I pushed the boot, recovery and system images from the automated linux zip file to the phone and rebooted. I now have a working Velocity 1.1 install.
alright. I moved the install-recovery.sh to disable that and wrote over the stock recovery with the flash_recovery tool. Rebooted the phone and it dumped me into fastboot, so I pushed the boot, recovery and system images from the automated linux zip file to the phone and rebooted. I now have a working Velocity 1.1 install.
Thanks
Yupp! If im not mistaken the files in that zip are 1.0 but they may have been updated. I really dont know.
I know this is an old post and I'm sorry to reopen it. However, I have recently acquired an LG ALLY with the 2.2.2 update on it. I'm not sure if this will work for me... I have Baseband Version: VS740MV3.6040.1001.....and SW Version: VS740ZVE.
If I follow the steps on the first page will I have a successful root?
Device(s): LG Ally running StormDroid/Velocity, Samsung Fascinate running ICS "CM9"
Thanks: 167
Thanked 194 Times in 116 Posts
Quote:
Originally Posted by Brandersnatcher
I know this is an old post and I'm sorry to reopen it. However, I have recently acquired an LG ALLY with the 2.2.2 update on it. I'm not sure if this will work for me... I have Baseband Version: VS740MV3.6040.1001.....and SW Version: VS740ZVE.
If I follow the steps on the first page will I have a successful root?
-Thanks.
Yes, your root will be successful. It will take you back to 2.1 eclair to get fastboot, and then will flash you to Velocity or stock, gaining root access as well. From there, you can upgrade to 1.2 or whatever you'd like.
for those whose update fails during the lg update.... reinstalled the androiddriver that was supplied in teh froyo root tools zip.... if you install the lg update software and let it install the android universal driver you will not be able to successfully update to vs740zv6_01
i had this same issue until i reinstalled the proper driver then it took off
also installing su required toggling signature verify to s-off before it would install
I would just like to add that I had to uninstall my LG driver manually in Control Panel before reinstalling the driver in the froyo.zip download. Simply reinstalling over what was already there did not work for me.
Yes, your root will be successful. It will take you back to 2.1 eclair to get fastboot, and then will flash you to Velocity or stock, gaining root access as well. From there, you can upgrade to 1.2 or whatever you'd like.
It was successful but now i'm running into some issues. I tried flashing clockwork mod, but when I do it reboots and brings me to fastboot. From there I have no control over anything so I have to pull the battery and I don't get clockwork. It brought me to Velocity btw.
What roms will work best for the Ally? or good ones at the very least.
Maybe someone else has ran into this. My wife's Ally has had a problem with the gallery app freezing the phone and causing a reboot. No big deal, I call Verizon and they send me a replacement. I made a current nandroid backup of her phone as it was. After I received the replacement yesterday, I powered down the old device and activated the replacement. Everything is working perfectly on the replacement up to this point.
I've rooted and installed Velocity 1.1 on both her Ally and mine, and a few days ago, upgraded both to Velocity 1.2. Both devices have fastboot, and had it from the beginning since both were originally shipped with ZV6. I was wanting to restore her nandroid backup so it would basically be a transparent change to the replacement. I fairly certain that the replacement would not have fastboot, so I followed the guide listed here.I noticed a few things changed since I used it before to root/flash/install Velocity, so I just followed this revised guide to make sure I didn't miss anything. Somewhere along the way here something happened. After reboot from the LGMU software flash back to ZV6-everything started force closing, and the touchscreen was totally dead-no response whatsoever. I went ahead and ran through the rest of the commands listed at #10, and it flashed Velocity 1.1 on the device. That rebooted fine, but no touchscreen at all. Nothing, nadda, zip. Thinking that something had gone wrong with it somehow, I repeated the process, but this time flashed it with stock 2.2.1. Same thing. No touchscreen. SO, I guess my question is this-is it possible that it's something with a hardware revision of the phone, and LGMU screwing up, or just a bad device? Both her old device and my device are HW Rev 1.1, and this replacement is HW Rev 1.0. Any ideas? Verizon is sending another replacement, I just wanna double check that it's not something I'm doing before the 2nd replacement gets here.
JL
Last edited by Johnny Langton; October 7th, 2011 at 08:26 AM.
Update, it was just that device. The replacement for it arrived today, and the whole process went smooth and without any errors or problems. The good thing-this new device REALLY likes Velocity 1.2. I've had it running overclocked to 864 running every app on the phone without issue. I've ran multiple rounds of quadrant tests, and the results have been in the 1100's. Linpack scores have been 10.5+ Mflops without a single hiccup.
JL
---earlier problem solved, just being tired---
OK followed steps everything went smooth, no problems. I thought I'd hit a snag, but that was just me being tired and not looking closely.
So to efficiently utilize the space I already opened, let me ask this.
What happens now if I'm running velocity and rooted and I accept the OTA update its nagging me about? (sorry if it's a silly question, I've never flashed or rooted a droid before, mostly used to palm and old school winmo)
Last edited by raithe; October 13th, 2011 at 03:00 PM.
Reason: I'm an idiot today.
I have froyo 2.2.2 and this would not work for me at all. I know a while back I used z4root to do this and it worked but no longer does. I just used the gingerbreak v1.20 on my ally and it worked and its a one click root/superuser program. Idk if itll work on anything under 2.2.2 tho.
Last night I followed all the instructions and got my phone rooted with velocity 1.0 on it. I have used it some last night and this morning and everything seemed to be working well. I only went into the terminal and typed su to see if I could actually get root access and it worked and I closed the terminal. Now, this morning I decided to run the velocity command in the terminal, but when I typed su, it gives me a
"[1] + Stopped (signal) su"
or
"[2] Illegal instruction su"
error, or both. I did some web searches to no avail and made sure that I uninstalled any updates to superuser or the terminal that got installed. Anyway, it is still not working and I have no idea how I broke it, but come someone help me?
Even if I just need to reset it back to the way it was RIGHT after I flashed it and then immediately run the velocity command in the terminal? Should I be letting the market update things that were installed with velocity?
Everything else seems to work just fin, I just don't seem to have root access anymore...
ok, so after fiddling with it all morning, I think I got it worked out by running the adb.bat again and letting it reinstall the rom.
I also THINK I figured out how I broke it. Now that I have SU again, the market is telling me that I need to install "Android Software Update (VS740ZVE)". Is that a no-no? If so, can I ignore that update somehow? It is also telling me that my SU binary is outdated. Not sure which one broke it first, but noe I'm scared to update either one... Thoughts?
Last edited by m_a_b; October 23rd, 2011 at 03:57 PM.
Device(s): LG Ally running StormDroid/Velocity, Samsung Fascinate running ICS "CM9"
Thanks: 167
Thanked 194 Times in 116 Posts
Quote:
Originally Posted by m_a_b
ok, so after fiddling with it all morning, I think I got it worked out by running the adb.bat again and letting it reinstall the rom.
I also THINK I figured out how I broke it. Now that I have SU again, the market is telling me that I need to install "Android Software Update (VS740ZVE)". Is that a no-no? If so, can I ignore that update somehow? It is also telling me that my SU binary is outdated. Not sure which one broke it first, but noe I'm scared to update either one... Thoughts?
Dont worry about the update. Just open Velocity scripts and let it handle that. Also, updating the su binary is highly recommended, as it is necessary for superuser to function properly.
Hi, I'm trying to get the Velocity 1.2 ROM on my phone. The original post of this thread is step one. After Step 9 of the original post, using LGMU to get 2.2.1 on the phone, the phone constantly reboots and spits out:
Sorry! The process android.process.media has stopped unexpectedly. Please try again. Force close
This makes the phone completely useless and I cannot continue with the steps. How can I get a working 2.2.1?
I had a rooted 2.2.2 stock image prior to this. By using the real LGMU utility, I can go back to something like 2.2.2 stock, but it's broke in a few places (home button doesn't work for example).
I really appreciate your help! Let me know what other info you need.
Thanks!
EDIT: I think the steps of the original article could be expanded after Step 9 to include:
STEP 9a: Once the phone is on, you will probably get a bunch of Force Close boxes. Unplug the phone, and pull the battery then re-insert.
STEP 9b: Do a factory reset by pressing and holding VOL UP+HOME+END
I found this at the LGNPST post and it's obviously what I was missing.
Last edited by tommyh; November 9th, 2011 at 09:55 PM.
Reason: possibly solution
ok so first i had a problem with lgmu crashing and i was stuck on the download do not unplug screen. somehow i managed to flash a clockwork restore from an old ally. i have fast boot and i have tried both ways shown here. both say specified file path not found then close out. i have even entered fastboot myself and ran both ways and still the same step. right now im stuck with velocity v0.3, i would like a rooted 2.2
edit: i took a step back and found the problem remember to follow the directions.... especially that one that tells yout to extract to c:\ once i moved the files from the second froyo folder to the first it worked... blah
Last edited by BAMARTIN03; December 5th, 2011 at 10:35 PM.
Reason: fixed but left the q and a so future people may see
Device(s): LG Ally (Velocity 1.1)
Oc'd @ 806 (Stable)
Thanks: 2
Thanked 2 Times in 2 Posts
i did this .. and it keeps saying that my USB isnt connected to the PC but it is connected, and everythin is showin up, like "usb connected" and "usb debugging enabled"
Is there a newer link to the zip file?...I keep getting a "404 File or directory Server not found error"
Thanks in advance.
There seems to be a new link to froyo.zip (savoxis dot com seems to have rearranged their domain structure but the file is still available) I'm a new user so I cannot post the link (if a mod could it would be appreciated). So if you cant find froyo.zip go to savoxis website(type savoxis into address bar and hit CTRL+ENTER or google: "savoxis") and click on LG ALLY folder/ROMS folder/Project Froyo folder/and finally froyo.zip.
Hope this helps (also hope its the same froyo.zip(215MB) since I haven't had the time to try this yet!)
Thanks everyone for their time in creating this wonderful guide!
Last edited by ajamesm12; March 2nd, 2012 at 02:29 PM.
Reason: added quote for clarity/cleanliness
well i know the ally is pretty much a dead project but i can foresee some renewed interest in rooting it. For one, many ally users are now upgrading to better phones and hence now are just getting the courage to attempt rooting. I have 3 ally's i get to tinker with now . another is many of these ally's will be sold or given away to new users who may want to root it or change roms. My niece actually switched to her first smart phone a few weeks ago, one of my old allies. The root guide hasn't been updated since last year. when i attempted to root mine i couldn't even get started in the process. first off like mentioned above the links are dead and have been moved. now the new folder seems to be labeled "project foyo", are we sure this is the same folder used in the instructions, or an updated/different version. the new folder size is larger for one, second i couldn't find a froyo/driver.bat file. it now goes into a google-usb_driver subfolder and still no .bat file. lastly the instructions don't seem to match a windows 7 64 bit set-up, which many people are using now adays. for instance my programs are stored normally in c:/ program files or c:/ program files (x86). i want to root my ally's but am unsure how to get started
well i know the ally is pretty much a dead project but i can foresee some renewed interest in rooting it. For one, many ally users are now upgrading to better phones and hence now are just getting the courage to attempt rooting. I have 3 ally's i get to tinker with now . another is many of these ally's will be sold or given away to new users who may want to root it or change roms. My niece actually switched to her first smart phone a few weeks ago, one of my old allies. The root guide hasn't been updated since last year. when i attempted to root mine i couldn't even get started in the process. first off like mentioned above the links are dead and have been moved. now the new folder seems to be labeled "project foyo", are we sure this is the same folder used in the instructions, or an updated/different version. the new folder size is larger for one, second i couldn't find a froyo/driver.bat file. it now goes into a google-usb_driver subfolder and still no .bat file. lastly the instructions don't seem to match a windows 7 64 bit set-up, which many people are using now adays. for instance my programs are stored normally in c:/ program files or c:/ program files (x86). i want to root my ally's but am unsure how to get started
I have windows 7 64bit too. I rooted my ally for the first time using this guide about 3 months ago with no problems.
I didn't find the froyo .bat file either with the new setup. i think i still have it at home on my box. I could send it to you later if no one has a link for it.
thanks jason80 but i think the project froyo folder has everything needed, it's just a matter of figuring out how to utilize the folders and programs. i tried doing the steps with the files i THOUGHT was the right ones but i don't think it went right. when i ran the KP500 utility i got like 3-4 "file error file not found" and when got to the end of process the utility window had a bunch of ??????? and entry window but no text displayed what was going on. i closed the program and i kept getting media, phone and other errors forced closing and rebooting non stop. i then followed tommyh instructions as he had the same issue it seems.
STEP 9a: Once the phone is on, you will probably get a bunch of Force Close boxes. Unplug the phone, and pull the battery then re-insert.-did nothing and rebooted the same thing over and over
STEP 9b: Do a factory reset by pressing and holding VOL UP+HOME+END
I found this at the LGNPST post and it's obviously what I was missing. this seemed to work and my phone rebooted with 2.1 but no root.
i then used the app universal androot to gain root and that worked.
and thats were im at but hardly feel comfortable.
the project froyo folder also has some folders i'm not sure what to do with. sdcard folder. seems im suppose to put these on my sd card but no instructions in the guide or in the file, there's tons of sub folders. workdir folder that contains fastboot and adb utilities and amonra and stock recoverydisc images, again no instructions or idea what to do with these. lastly in the lgvs740 folder is VS740ZV6_01 but it's zipped. this seems to be the back to stock version i was supose to go back to, it asks were to unzip it too. i haven't done anything with the mentioned folders/utilities it just seems i should be doing something with them...
basically i'm completely lost now lmao.
at this point i'm all ears. what i would LIKE to do is make sure i have a stock recovery and confident how to use it, make sure my phone is rooted correctly, and install a custom rom. i've tried going to IRC but im not sure where to go to get help. someone told me #android but when i tried to go there i get - you need to be identified with services.
Last edited by DruidXXX; March 20th, 2012 at 06:37 AM.
I have searched all files thru and thru and cannot find the ADB.bat. I even download another zip file and unzipped it to a different location to try and find it. I found adb.exe but it only pops up with a quick command window (not long enough for me to read). How do I get this .bat file?
Hello, I am attempting to root my phone for the first time. The phone is LG ally, all factory setting with 2.2.2. I downloaded froyo.zip from http://www.savoxis.com/LG%20Ally/Roms/Project%20Froyo/ because the posted link no longer works. I extraded it to C:\ (I am using windows 7 x64 btw.) The drivers.bat file wasn't present so I ran LG _USB _Drivers_All_4.9.7 and LGAndroidDriver_WHQL_ML_Ver_1.0_All_Win7 because it seemed like the closest thing. I then ran KP500-Utils-EN and put the supplied info in. AFter entering the verion a windows pops up and says C:\ProgramData\LGMOBILE\image\ehader_bg.gif was not found. I hit Ok and software update opens and reads the phones info. When its done an empty window titled server error pops up. The phone downloads and resets. The guide says to open adb.bat but there is no file in the download and the phone just displays the process adroid.process.media and android.process.acore has stoppped unexpectedly. and restarts over and over. Help would be appreciate. Sorry if this message is too long.
the link to the froyo zip file does not work. it takes me to a bunk site or another site that prompts for username and password, but no mtter what i put in it acts like it' wrong and will not take me to the designated URL. im hapy i found this guide but its not really useful if i can't even get past step 1. i'm sure i could find it on any random torrent site, but wanted to adhere to the instructions in the guide so if something went wrong i would at least know it wasn't my mistake. any helpful hints?
the link to the froyo zip file does not work. it takes me to a bunk site or another site that prompts for username and password, but no mtter what i put in it acts like it' wrong and will not take me to the designated URL. im hapy i found this guide but its not really useful if i can't even get past step 1. i'm sure i could find it on any random torrent site, but wanted to adhere to the instructions in the guide so if something went wrong i would at least know it wasn't my mistake. any helpful hints?
Its changed though a bit. It seems that you'll have to the run Froyo.bat file which contains what used to be separately the ADB.bat and Drivers.bat files.
just follow the prompts and you should be fine, but don't take my word for it.
So my HTC Thunderbolt got wet last week ( :'( ) so I'm using my Dad's old Ally now. After having root on my Bolt, I really can't go without it, so I set out to root this thing too. I downloaded the froyo.zip file from here and tried to follow the froyo.bat file's instructions myself (I'm too paranoid to let automated methods root my phone). Since I already had fastboot access (phone is 2 years old, shipped with VS740 -- verified with adb reboot bootloader into fastboot), I skipped the downgrading part. Here are the steps I took:
1) Pushed su zip file to phone with adb
2) adb reboot bootloader
3) fastboot flash recovery amonra_recovery.img
4) fastboot boot amonra_recovery.img
5) Made Nandroid (paranoia), flash su zip in recovery
6) adb mv /system/etc/install_recovery.sh /system/etc/install_recovery.sh.bak
7) Reboot from recovery
The problem I was having with following the batch file was that it calls for "fastboot reboot recovery" after flashing amon ra recovery, but fastboot doesn't recognize that as a valid command. As a workaround, I used the fastboot boot command to get into amon ra so I could rename install_recovery.sh and get amon ra to stick.
Hopefully this helps if anyone else is running into this issue with the froyo.bat file. Running Velocity 1.2.2 now, and the phone flies!
When the LG Phone Update window opens, I get an error that my phone is not connected to my laptop with USB... which it is. Anyone know how to fix that?
I guess this topic and the guide are a dead issue. I did go to the irc channel looking for help (since no one here offered any). Someone there made the generous offer of taking control of my computer via remote access so they could root my phone for me. Really? Like I would give remote access to a total stranger!
Just wanted to mention that in case anyone else considers going to that irc link for help. You will not find any.
The irc is meant for help. All channels are generally secure and if be the case of viral command, that user would be banned.
Just asked the wrong people
The LG Ally was one of the first Android handsets from the Korean manufacturer to see a US release. The QWERTY slider came to Verizon in the spring of 2010 as a mid-range smartphone geared towards those looking for a solid media and messaging... Read More