Made a donation. Thank you for all of your hard work on this. This is my first time loading a custom ROM on my wife's Android, although I have gone through countless hybrids on my BlackBerry. Still exploring, but I wanted to say thanks to you and all the other helpful members here
So I'm still pretty happy with V0.3. I really can't find anything to report. Stable, simple, fast - even faster now that I finally got a C6 sd card! Never had an issue with my calculator, A2SD, LED Flashlight, nothing. Very impressed. So now I just look forward to the release of V0.4. I saw a post a while back ago that asked for a "More Functional" (COOLER) unlock screen, I have no idea if that's included in V0.4, but I kinda hope so.
For some reason i can no longer install velocity. One day velocity crashed (everything would just force close, and nothing would load). So i flashed back to stock and when i attempt to reflash the rom with anything except a stock based ROM i get boot loops. HALP MEH!! lol
HELP!!! AND QUESTION...
SO WITH THIS KERNNEL. I DON'T HAVE TO INSTALL GNM TURBO4 W/O KERNNEL????
I ROOTED W/ UNI ANDROID, THEN TRIED TO INSTALL GNMTURBO4 BEFORE INSTALLING LG Ally Kernel 2.6.29.6_GNM_OC ... IN ROM PRE-INSTALL, I CHECK BACPUP EXISTING ROM AND WIPE DATA AND CACHE... MY PHONE HAS BEEN STUCK IN VELOCITY B00T LOOP SINCE. 1. WHAT DID I DO WRONG? 2. HOW CAN I FIX IT AND ADD YOUR KERNNEL???
THANKS FOR ANY HELP,
EZ
To get that kernel to work right, I had to flash the TurboIV w/o kernel first. Cleared the caches, then flashed the new kernel. Cleared the caches again.
Hopefully you ran a nand backup before flashing, you can just recover back to the working state of your phone and try again.
Try reflashing the TurboIV w/out kernel rom, then clear the caches, and reboot back to recovery. Then flash the kernel and clear the caches again. When your phones boots to android it shouldn't get stuck in the loop.
Good luck. If you have any more trouble, highly recommend the IRC channel. the guys there are very helpful and knowledgeable and willing to help out with major issues.
The Following User Says Thank You to k.c.cole For This Useful Post:
Device(s): - HTC EVO 4G rooted Azrael X v5.0 BETA works nicely, LG ALLY(dead)
Carrier: Not Provided
Thanks: 0
Thanked 1 Time in 1 Post
wanted to say thank you so much for making velocity. now i use my android all day and i only have to charge it half as often. running oc at 728 748 and 787 showed no signs of trouble.
So the OTA update we should not install? How do I get the notification screen to stop popping up to install the update? Thanks for all the hard work on Velocity.
I just installed 0.3 over 0.2 and it seems to have a little lag over 0.2. For instance, as I type this, I'm get 3 or 4 letters ahead of myself and have to wait for it to catch up. 0.2 was instant.
Also, when was the baseband released? I went to update it but noticed the version in the file name is the same as what I have already. Does that sound right?
I'm also getting a syntax error from the velocityboot script. Looks like one of the lines has an unescaped or unclosed quote mark.
For some reason i can no longer install velocity. One day velocity crashed (everything would just force close, and nothing would load). So i flashed back to stock and when i attempt to reflash the rom with anything except a stock based ROM i get boot loops. HALP MEH!! lol
Something similar happened to me today. I went to put on GNM Turbo after using .3 since its release, I ended up with boot loops. I then restored back to .2 which worked fine but have tried flashing to .3 twice now and still getting stuck in boot loops. Thinking it may have something to do with OTA update which btw I ignored everytime it popped up.
anybody get an OTA update? i didnt pay attention and hit install now... now its stuck with a exclamation mark :/
Well if you ever get rooted again, I have erased a file inside the rom called SystemUpdater.apk is roughly 74.1 kb then resigned the rom and reflash it, it hasent had it ask me to update again.
oooor....
Type
Code:
ota -d
in terminal emulator and press enter.
Last edited by insanedrunk; November 26th, 2010 at 09:33 PM.
I had 0.3 up and running for a few days, then suddenly my vibration stopped working. I called verizon and they authorized a warranty return, but after I reflashed the stock ROM, vibration came back. I reflashed to velocity 0.2 and all seems to be well again.
Do you think this is velocity related or should I go ahead and convince them to warranty out my phone?
Well if you ever get rooted again, I have erased a file inside the rom called SystemUpdater.apk is roughly 74.1 kb then resigned the rom and reflash it, it hasent had it ask me to update again.
oooor....
Type
Code:
ota -d
in terminal emulator and press enter.
i know there was something about why he left ota updates on... i forget but its all fixed now. i removed the battery and the phone restarted fine, it says its up to date now
Quote:
Originally Posted by vortmax
has anyone had an issue with their vibration?
I had 0.3 up and running for a few days, then suddenly my vibration stopped working. I called verizon and they authorized a warranty return, but after I reflashed the stock ROM, vibration came back. I reflashed to velocity 0.2 and all seems to be well again.
Do you think this is velocity related or should I go ahead and convince them to warranty out my phone?
i ran into this issue with 0.2 actually lol when i flashed to 0.3 i got it back.... its a velocity related issue but odd to see it happen the other way around
Device(s): T-Mobile G1, LG Ally, Motorola Atrix 4G
Carrier: Not Provided
Thanks: 7
Thanked 0 Times in 0 Posts
home button has gone awol
so after a bit of help from the fellows who populate the Ally Help IRC chat, i got velocity up and running, only thing is that my home button and send button dont respond to anything. (EDIT: they still wake the phone from a sleep state, but for some reason do nothing else)
has anyone else encountered this and if so, has a fix for it been made apparent, thanks!
Last edited by CommodoreOfChaos; November 28th, 2010 at 04:02 PM.
CommodoreOfChaos i have the same problem , my home button does not work and when i hold down the power button it does not give me the airplane mode or the others options it just give me the power off option.
To get that kernel to work right, I had to flash the TurboIV w/o kernel first. Cleared the caches, then flashed the new kernel. Cleared the caches again.
Hopefully you ran a nand backup before flashing, you can just recover back to the working state of your phone and try again.
Try reflashing the TurboIV w/out kernel rom, then clear the caches, and reboot back to recovery. Then flash the kernel and clear the caches again. When your phones boots to android it shouldn't get stuck in the loop.
Good luck. If you have any more trouble, highly recommend the IRC channel. the guys there are very helpful and knowledgeable and willing to help out with major issues.
IS THERE A GUIDE ON HOW TO USE the IRC channel. ican not figure out how to interact with the folks on IRC... thanks,
ez
Does 0.3 include the tun.ko module? I'm currently running 0.2 (0.3 was giving me issues), but I want to get openVPN up and running. I see that the 2.6.29.6_GNM_OC kernel has it included. Is there an issue flashing this kernel to velocity?
I installed this on my ally and i couldnt get some things off the rom like the background ect...I dont remember what i did but i eventually got everything. I am trying to install this rom on my moms phone and it doesnt install the background and some other things. Any suggestions?? Thanks
Nvm...found out I didnt wipe data and dalvik catch
Last edited by jrock204657; December 1st, 2010 at 12:09 AM.
It's best to have a class 6, but it will work with lower class cards as well.
Sorry to bug u but need help...
I installed this on my ally and i couldnt get some things off the rom like the background ect...I dont remember what i did but i eventually got everything. I am trying to install this rom on my moms phone and it doesnt install the background and some other things. Any suggestions?? Thanks
nevermind...found out i didnt wipe data and dalvik catch
Last edited by jrock204657; December 1st, 2010 at 12:09 AM.
one of the recent releases included an update for the radio to improve signal strength or something. If the stock ROM you replaced with velocity was before that update, you don't have the new broadband version....so trident stripped out the broadband update and posted it. So now you can update the radio without having to flash the entire verizon update.
The Following User Says Thank You to vortmax For This Useful Post:
I'd like to try Velocity 0.3 on my new Ally, but I'm a clueless newbie. I've looked around a bit but didn't see a clear thread on how exactly to do this. Is there an idiot's guide from start to finish about how to flash etc? And I do mean start to finish! I'm new to all of this, sorry for the noob questions.
Is there an idiot's guide from start to finish about how to flash etc? And I do mean start to finish! I'm new to all of this, sorry for the noob questions.
Excited about flashing to Velocity 0.3, but have run into a slight problem. I have rooted the phone, I'm using ROM manager/clockwork recovery and have done a current ROM backup. I go to "install from SD" and when I get to the velocity...zip file and try to select it, ROM Manager tells me "unable to open this file..." So what am I doing wrong? I'm assuming I can install directly from recovery mode, but I haven't tried that yet. I'm new to this and don't want to mess something up. Thanks in advance.
Excited about flashing to Velocity 0.3, but have run into a slight problem. I have rooted the phone, I'm using ROM manager/clockwork recovery and have done a current ROM backup. I go to "install from SD" and when I get to the velocity...zip file and try to select it, ROM Manager tells me "unable to open this file..." So what am I doing wrong? I'm assuming I can install directly from recovery mode, but I haven't tried that yet. I'm new to this and don't want to mess something up. Thanks in advance.
Sounds like the file didn't completely download. Try to redownload the file and do it again, make sure you flash clockwork mod recovery before you install the rom. always wipe cache and data when it asks you to during the install.
Either that or you don't have unkown sources checked to install unknown apks and zips.
Excited about flashing to Velocity 0.3, but have run into a slight problem. I have rooted the phone, I'm using ROM manager/clockwork recovery and have done a current ROM backup. I go to "install from SD" and when I get to the velocity...zip file and try to select it, ROM Manager tells me "unable to open this file..." So what am I doing wrong? I'm assuming I can install directly from recovery mode, but I haven't tried that yet. I'm new to this and don't want to mess something up. Thanks in advance.
OK, I didn't realize that the ROM had to be in the root of the SD card. I originally had the velocity .zip file in a folder on the SD card. Moved it to the root and installed no problem.
I've flashed Velocity 0.3 and am loving it. I have a few questions:
1. I was unable to flash the stock Android theme as described in the first post. Not a big deal but just want to know if this has worked for others? I followed the same procedure for flashing a kernel, no go.
2. What happens with OTA updates in Velocity? Will OTA updates affect anything? Still hoping to get Froyo and wondering if I'll be notified of Froyo if it ever become available.
I've flashed Velocity 0.3 and am loving it. I have a few questions:
1. I was unable to flash the stock Android theme as described in the first post. Not a big deal but just want to know if this has worked for others? I followed the same procedure for flashing a kernel, no go.
2. What happens with OTA updates in Velocity? Will OTA updates affect anything? Still hoping to get Froyo and wondering if I'll be notified of Froyo if it ever become available.
thanks in advance.
Haven't tried the stock theme yet...like the velocity theme, but as far as updates...it may notify you there's an update, but it will fail upon trying to install. To get the factory updates, you'll have to reflash to v6, and then flash the stock recovery image, then it will do all verizon updates. Just had to do that last night because I was stupid and deleted google talk before researching.
Installed the radio update. VS740MVB.5210.1015 this afternoon and right after noticed unable to download from the market. Can connect ok to browse it, and with other apps, but apps wont download from the market. Im not sure if the two is connected.
I have a quick question for anyone who knows...if I get a class 6 card instead of the class 4 my phone came with, how do I get the dalvik cache to store on the card instead of the phone? just to free up some more memory.
Trident is working on implementing that function in Velocity 0.4, as far as I know. Other than that, I'm not entirely sure you can, without flashing a complete ROM.
i think using apps2sd it does this if you set it, but its only for velocity .2, raptor, and vzb roms...i just want to free up even more space on the phone to help speed it up.
Here's another dumb question...I read somewhere that it's best to format your sd card before flashing velocity. If I get a class 6 8gb card, do I have to recover to factory, format the card, then reinstall velocity? Or do I format the card, then just reflash velocity? Or do I have to do nothing but format the card? Obviously, I know I'd have to reinstall all apps, just wondering the proper method of upgrading my card.
Device(s): Thunderbolt - Lost to the pits of Magic Mountain
Galaxy Nexus - So sweet
Carrier: Not Provided
Thanks: 6
Thanked 11 Times in 9 Posts
Ok guys I'm trying to figure out this OTA update thing. I'm flashed to Velocity 0.3 and it keeps popping up asking to update. It gets blocked everytime and the popup is annoying. I don't understand this flash to V6 thing and how it works. Do I flash to 6, then let it update to 9 then reflash Velocity? That doesn't make much sense to me =-/
Ok guys I'm trying to figure out this OTA update thing. I'm flashed to Velocity 0.3 and it keeps popping up asking to update. It gets blocked everytime and the popup is annoying. I don't understand this flash to V6 thing and how it works. Do I flash to 6, then let it update to 9 then reflash Velocity? That doesn't make much sense to me =-/
you have to flash to v6, then flash the stock recovery. keep doing the *#*#checkin#*#* thing, it will update to v8, then vzb, then vzc. it won't update to v9 because that update was pulled. after you get vzc, then find z4root to reroot, then reflash velocity.
Device(s): Thunderbolt - Lost to the pits of Magic Mountain
Galaxy Nexus - So sweet
Carrier: Not Provided
Thanks: 6
Thanked 11 Times in 9 Posts
I just tried to install the GNM4 Turbo with kernel for Velocity, but when I use setcpu it tells me the process has stopped and it FCs. Anyone else have this issue?
i had an issue with launcher pro, couldnt get into any apps on my phone. I decided to reinstall velocity through recovery menu. Im using clockworkmod recovery. Im using debian linux, and i mount USB storage inside clockworkmod. It looks like the velocity0.3 zip file is moved over to the sdcard, but in clockwork it cant find any files on the sdcard. I tried factory reset, and when i hit a brick wall, i formatted, system, sdcard, everything (except boot) and now cant get past the verizon logo. Anyone know what I can do. I can still boot into recovery.
I'm running Velocity and I would like to know what happens when you do a "factory data reset" (under setting/privacy) with a custom ROM like this? I know it will erase all data, but what if anything will happen to the ROM? Thanks in advance.
I've had the same problem on the Ally with getting the update message from Verizon even though in settings it says i have the update. I'm not sure what to do. i've read the explanation above talking about flash to v6 then v9 or whatever but i'm NOT sure what that mean. i a lso tweeted you with the same inquiry(@bnitty). any suggestions?
rocessing commands?? What should I do
I thought it might be the ota script so I tried ota -e but that didn't work... any ideas
