Device(s): Motorola Droid Bionic 2.3.4
LG Ally 2.2.1- Velocity v1.2
Carrier: Not Provided
Thanks: 20
Thanked 11 Times in 10 Posts
When I go into terminal emulator and type su then velocity it is this when it is looking for updated script:
/cache/velocity/intro.txt: No such file or directory
Why is it saying that?
__________________
Motorola Droid Bionic- 2.3.4 rooted and debloated
LG Ally- 2.2.1 rooted with Velocity v1.2 OC at 768
Retired
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Quote:
Originally Posted by tigersfan1
When I go into terminal emulator and type su then velocity it is this when it is looking for updated script:
/cache/velocity/intro.txt: No such file or directory
Why is it saying that?
Update.
If that doesnt fix it make sure you have at least a 3g connection
heyi have an lg ally with verizon and im trying to flash it over to metro but im not good with computers and i dont know how.could someone help me step by step without charging me plz.
well the black sms mod messed with my phone so i wiped and reflashed V1.0 back on and now the scripts will not work. I tried to do the force update as posted in here Update script not working for me
but it didn't help either. Any ideas Sav? I redownloaded velocity and still nothing. Tried reflashing and still nothing. Thanks
well the black sms mod messed with my phone so i wiped and reflashed V1.0 back on and now the scripts will not work. I tried to do the force update as posted in here Update script not working for me
but it didn't help either. Any ideas Sav? I redownloaded velocity and still nothing. Tried reflashing and still nothing. Thanks
im having a similar problem to yours. i reflashed velocity and since the reflash i can get the script to update again. doesnt show what version its on but im assuming v1 since it was a fresh reflash. it says its connecting to the ip of the server but tells me i already have the current version installed. ive tried the force update listed in the first post but that hasnt worked either.
Device(s): Lg Velocity(ALLY)/Retired
Samsung Fascinate, TeamHacksung CM9-ICS, Glitch V14beta2 kernel
Carrier: Not Provided
Thanks: 133
Thanked 25 Times in 23 Posts
I had to reflash Velocity and now I can't get update script to work. Says connecting to and some numbers. Can't get option for zip align or resolution. How do I force newest updates?
__________________
Samsung Fascinate, TeamHacksung's CM9 ICS, Glitch V14 beta3 kernel
Get your own personal Dropbox now!!!! Sync your files online and across computers with Dropbox. 2GB account is free! And get extra free space from referrals http://db.tt/3IsIYJB
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Quote:
Originally Posted by azuma73
I had to reflash Velocity and now I can't get update script to work. Says connecting to and some numbers. Can't get option for zip align or resolution. How do I force newest updates?
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
I've been "out of the loop" for awhile attending to other things here, so I just today read this entire thread. I can't say I have noticed any problems with Velocity Scripts, and updating them. Currently, Terminal shows I have Velocity Script v25. Does that mean I am up to date, and do not need to be concerned with all the above reported issues?
If so, does v25 include the automatic Dalvik-Cache cleaning script update I saw mentioned in the thread?
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
Howdy. I am having issues updating the scripts. How do I manually change it to update from the new server? It keeps trying to update from the original one and I didn't see anything in these pages about manually changing the path. Thanks!
EDIT* I somehow missed the last page. My problem was wget -0 instead of a capital o. Thanks for all the hard work you did on this Sav!
Last edited by Desertbum; April 8th, 2011 at 12:59 PM.
I've been "out of the loop" for awhile attending to other things here, so I just today read this entire thread. I can't say I have noticed any problems with Velocity Scripts, and updating them. Currently, Terminal shows I have Velocity Script v25. Does that mean I am up to date, and do not need to be concerned with all the above reported issues?
If so, does v25 include the automatic Dalvik-Cache cleaning script update I saw mentioned in the thread?
V25 is the most recent. All of these problems are people who have reflashed, the server changed from the initial one in 1.0
The Following User Says Thank You to GRZLA For This Useful Post:
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
Quote:
Originally Posted by GRZLA
V25 is the most recent. All of these problems are people who have reflashed, the server changed from the initial one in 1.0
Thanks GRZLA. So in a nutshell what would I need to do if I had to re-flash the original release of Velocity 1, in order to update the IP address to the new one? Several people seem to be asking this over on the Velocity ROM thread. Is one of the procedures mentioned back toward the middle of this thread all that is needed to fix it? I'd like to know so I can write it down for safe keeping when I need it someday.
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
I just got v. 26 Script OTA, and having also just created a Nandroid I decided to take the plunge and try toggling the Dalvik-cache over to the SD card. Wow!!
The Ally's internal memory leapt from he high 20's MB to 105MB! And at the same 748 MHz overclock I have been using all along it seems even peppier! Hopefully none of my apps will decide not to like this and head for the boot-loop threat warned in the script page for this step.
This ROM just keeps getting better and better! Can't say this enough, so
Please help...
The other day I formatted my SD card and very stupidly did not backup any of my nandroids before doing so, when I booted my phone everthing appeared to work fine, I put my phone on the charger and left it overnight. The next morning when I unplugged my phone it immediately rebooted, I thought this was odd but did not see any real problem. When my phone turned on, the menu ket, the home key, the send key, and all of my physical keyboard did not work. I tried clearing all of my data and reflashing velocity but the problem persists. Due to my arrow keys not working I can not navigate through recovery, I can only access what is possible through ROM manager. If anyone has an idea, please let me know, I am fairly good at troubleshooting and am not too worried about bricking my phone. Thank you
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
You weren't by chance trying out the way to disable keys on the Ally keyboard we had discussed in another thread, were you ? That could have an effect on keys not working.
I suppose one route to take would be to go back and re-flash Velocity again and then work forward from there.
Not complaining by any stretch of the term but i would like to make a possible bug report which originated after flashing to script v26. When applying the splash screen the phone now boots to a blue screen then to the traditional velocity grey then to the boot animation of my choice. This is no big deal to me but just wanted to inform the powers that be that its accuring on my device.
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Flashing the splashes is far from perfect, the images corrupt easilly and flashes fail, but a failed flash just causes a blue screen, to fix this just reflash, clear your downloaded cache if it fails again.
EDIT: I think I found a fix Im gunna test some more probably release a v27 later
EDIT: Updated to v27, fixed the splashes I believe (I just have it flash it 2 times, could still mess up if the download gets corrupted) and among a few other things, I implemented a help system, press h in any menu for a simple, brief desc.
Last edited by savoxis; April 12th, 2011 at 11:44 AM.
The Following User Says Thank You to savoxis For This Useful Post:
Flashing the splashes is far from perfect, the images corrupt easilly and flashes fail, but a failed flash just causes a blue screen, to fix this just reflash, clear your downloaded cache if it fails again.
EDIT: I think I found a fix Im gunna test some more probably release a v27 later
EDIT: Updated to v27, fixed the splashes I believe (I just have it flash it 2 times, could still mess up if the download gets corrupted) and among a few other things, I implemented a help system, press h in any menu for a simple, brief desc.
I can attest to that. I did the Android Burst (#3) and first time, blue screen, second time, AMAZING ANDROID BURST!!! It doesn't seem like a whole lot, what with the new splash screen and boot animation (I have the Scribbles animation set as well) but everything and anything that distinguishes my BAD ASS ALLY from the almost pathetic stock phone. Thank you guys so much for the love!!
You weren't by chance trying out the way to disable keys on the Ally keyboard we had discussed in another thread, were you ? That could have an effect on keys not working.
I suppose one route to take would be to go back and re-flash Velocity again and then work forward from there.
Nope, I did not try to disable any keys. My phone just rebooted and it wasn't working.
I tried reflashing Velocity multiple times to no avail.
Flashing the splashes is far from perfect, the images corrupt easilly and flashes fail, but a failed flash just causes a blue screen, to fix this just reflash, clear your downloaded cache if it fails again.
EDIT: I think I found a fix Im gunna test some more probably release a v27 later
EDIT: Updated to v27, fixed the splashes I believe (I just have it flash it 2 times, could still mess up if the download gets corrupted) and among a few other things, I implemented a help system, press h in any menu for a simple, brief desc.
Version 27+ clearing of download caches again worked first time
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Script V28
Ok, so I know the server can be slow sometimes, and I know it can be frustrating so with you guys in mind I spent all day today making a MIRROR system with 3 separate servers, one will be selected randomly when the script launches....
I am going to make it a little smarter, and have an option to set a mirror in the script menu, but for now its random for load balancing!
The mirrors all sync to each other.
This was all really made possible because of Delocated's wget binary, that allows me to wget from a server based on host name rather than IP.
THANKS DELOCATED YOU ROCK
But seriously, thank him, he is the SH Wizard!
Let me know if this new system has any quirks (im sure there may be a few)
Last edited by savoxis; April 20th, 2011 at 05:58 PM.
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
** UPDATED**
I updated to 28 (or tried) and any time I open Terminal Emulator and type su, velocity it says connecting 184.106.76.138 (184.106.76.138:80) and starts flashing can't open cache Velocity/wget.tar "no such file or directory" or something like that. I can't tell you the exact error because the screen rapidly flashes on and off till I shut Terminal Emulator down.
Last edited by dautley; April 20th, 2011 at 09:44 PM.
Reason: updated info
Device(s): Lg Velocity(ALLY)/Retired
Samsung Fascinate, TeamHacksung CM9-ICS, Glitch V14beta2 kernel
Carrier: Not Provided
Thanks: 133
Thanked 25 Times in 23 Posts
Weird happenings??
Just tried to update to 28. says fetching and installing now but keeps flashing "connecting to 184.106.76.138" repeatedly and doesn't seem to be connecting. I can't even get to the scripts? Anyone else having a similar deal with this update?
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
+1
Version 28 installed just fine. But when I tried to type velocity into the terminal prompt, I get the same problem as above. Cannot connect to that IP address, but it keeps trying. Script 28 has a flaw. How do I 'downgrade' back to version 27?
Device(s): Samsung DROID Charge TW3@K3D 2.2 ; Samsung Fascinate; LG Ally running on bacon
Carrier: Not Provided
Thanks: 53
Thanked 42 Times in 31 Posts
V28 works fine for me. don't see what you mean by it cannot connect to ip, I just exited terminal and went back in 4 times or so. loaded velocity scripts menu with no problem.
__________________
Need help? Want to chat?
Come visit #ally on freenode
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
Still no joy. What it keeps rapidly flashing between lines of the IP address is "cannot open cache/velocity/wget.tar".
I would try a reboot, but then I would be stuck with out the 768 MHz OC until a fix is offered, so I would rather not reboot until I know I can OC again. Is there a way to go back to script 27?
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
Actually I have several Nandroid backups. I make them periodically, and also make complete SD card backups to my PC weekly since having my SD card die on me twice with this phone.
What I didn't know is that restoring a Nandroid also restores Velocity Scripts. Thanks! I'll go that route later tonight.
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
Quote:
Originally Posted by Zoandroid
Actually I have several Nandroid backups. I make them periodically, and also make complete SD card backups to my PC weekly since having my SD card die on me twice with this phone.
What I didn't know is that restoring a Nandroid also restores Velocity Scripts. Thanks! I'll go that route later tonight.
I'm not 100% sure it will restore the scripts but would think so
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
I hadn't thought of this option, so either way it's worth a shot. The worst that will happen is putting me back a week or so in time. And possibly getting stuck at 600 MHz if it doesn't work. Let's hope it does.
Edit - I am restoring my most recent Nandroid, which I made on 4/11/2011 prior to implementing the "move Dalvik Cache to SD" which was recently provided in (I think) script 26. That function gained me tons of internal memory (like increased from 27 to 207 MB). I did not encounter any problems with the several apps I have installed after moving the Dalvik Cache. Not sure if that would have any bearing on this issue with Script 28 though.
After restoring the Nandroid just now, I rebooted and opened Terminal. I had previously added the Terminal option to run SU and Velocity when Terminal starts. I removed that option today when Script 28 malfunctioned, to see if entering it manually would help (it did not).
So, I am now in Velocity Script and seeing the question asking me if I want to download Script 28 again. It appears restoring the Nandroid does in fact restore back to the previous script as well. I replied "N" to the update. The screen then revealed I am in Script number 26. So I will have to stay here until I get word that Script 28 or newer is safe to use.
I am re-running the move of Dalvik Cache to the SD card (after it told me to clear my Download Cache to make room for the operation). One thing that I find a bit unsettling is that during this move of the Dalvik Cache, the Terminal screen says it is moving the cache and then "phone will reboot to complete the operation", but then it just sits there appearing to do nothing for several seconds. If it said "will reboot shortly" or something that would help me know it has not frozen in mid-operation, which I usually suspect when I don't see anything happening.
OK, I am back with 180MB free internal memory and running OC'd at 768 MHz.
Thanks for suggesting the Nandroid restoration. I'll continue to monitor this thread for news that Script 28 has been fixed.
Last edited by Zoandroid; April 20th, 2011 at 08:38 PM.
The Following User Says Thank You to Zoandroid For This Useful Post:
I hadn't thought of this option, so either way it's worth a shot. The worst that will happen is putting me back a week or so in time. And possibly getting stuck at 600 MHz if it doesn't work. Let's hope it does.
Edit - I am restoring my most recent Nandroid, which I made on 4/11/2011 prior to implementing the "move Dalvik Cache to SD" which was recently provided in (I think) script 26. That function gained me tons of internal memory (like increased from 27 to 207 MB). I did not encounter any problems with the several apps I have installed after moving the Dalvik Cache. Not sure if that would have any bearing on this issue with Script 28 though.
After restoring the Nandroid just now, I rebooted and opened Terminal. I had previously added the Terminal option to run SU and Velocity when Terminal starts. I removed that option today when Script 28 malfunctioned, to see if entering it manually would help (it did not).
So, I am now in Velocity Script and seeing the question asking me if I want to download Script 28 again. It appears restoring the Nandroid does in fact restore back to the previous script as well. I replied "N" to the update. The screen then revealed I am in Script number 26. So I will have to stay here until I get word that Script 28 or newer is safe to use.
I am re-running the move of Dalvik Cache to the SD card (after it told me to clear my Download Cache to make room for the operation). One thing that I find a bit unsettling is that during this move of the Dalvik Cache, the Terminal screen says it is moving the cache and then "phone will reboot to complete the operation", but then it just sits there appearing to do nothing for several seconds. If it said "will reboot shortly" or something that would help me know it has not frozen in mid-operation, which I usually suspect when I don't see anything happening.
OK, I am back with 180MB free internal memory and running OC'd at 768 MHz.
Thanks for suggesting the Nandroid restoration. I'll continue to monitor this thread for news that Script 28 has been fixed.
I am getting the same result as you, however no nandroid backup to restore to. Hopefully savoxis will provide us with a way to manually update to the next script update...or needless to say the Velocity 1.1 release!!
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
Sorry to read you don't have a Nandroid to restore. My history of this sort of bad news has taught me (the hard way) to back things up, although perhaps not as often as some people recommend. But it did save my bacon tonight.
I am far from knowledgeable on this issue, but perhaps he could make available a zip file one could flash using recovery, which would revert back to Script 27, or forward to Script 29 once he works out the kinks. Since restoring a Nandroid does restore the Script files, it should be doable that way.
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Sorry guys, my brain hurts, I have been hard at this for about 4 hours now.
And the results are in, fix is up with v29 but if the v28 messed up your wget you will need to flash this script patcher i made in recovery, which will fix your wget and update you to v29.
The new v29 uses awesome md5 checksum technology to ensure you are not screwed by evil corruption demons, after mastering this new technology I can now incorporate it into everything making for no more hasstles.
Also in v29 I have recoded the first bit of it, hopefully debugging the connection checker, I thoughly tested myself, but crazy things happen.
Ok, uploading now
Ok, its up, gnight
Last edited by savoxis; April 20th, 2011 at 11:00 PM.
The Following 4 Users Say Thank You to savoxis For This Useful Post:
Device(s): BIONIC XT875 JB .22/Rooted, Nexus 7 (16GB with CM10), Nexus 7 (32GB stock) Kindle Fire, LG Ally
Carrier: Not Provided
Thanks: 292
Thanked 440 Times in 289 Posts
**updated**
The downloadable patch works fine, thanks! But just for fun (and FYI) I went ahead and restored a nandroid backup and tried to update the normal OTA way again and am still not able to. Although the screen doesn't flash when it fails now I'm still not able to access the script menu after trying to update via OTA.
Last edited by dautley; April 21st, 2011 at 07:51 AM.
Sorry guys, my brain hurts, I have been hard at this for about 4 hours now.
And the results are in, fix is up with v29 but if the v28 messed up your wget you will need to flash this script patcher i made in recovery, which will fix your wget and update you to v29.
The new v29 uses awesome md5 checksum technology to ensure you are not screwed by evil corruption demons, after mastering this new technology I can now incorporate it into everything making for no more hasstles.
Also in v29 I have recoded the first bit of it, hopefully debugging the connection checker, I thoughly tested myself, but crazy things happen.
Ok, uploading now
Ok, its up, gnight
Woot! Thanks for the SUPER fast response and superior work as always!
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 246
Thanked 178 Times in 155 Posts
I got "29" to update, but it starts out saying it is script 28, then it displays a SWEET new screen which shows the progress of downloading the next update (29).