the rom checks for the backup that you made prior to flashing. try reflashing the rom without trying the restore and see if that works
ok, so the way I understand this is after wiping data/caches/sd ext, then put the rom zip file and the backup file made from the backup script back onto the sd card then flash the rom and the backup will automatically restore during the flash?? I just want to make sure before i attempt reflashing.
Otherwise, so far no problems with the rom. really responsive and glad to have o/c built in with no need for setcpu. Great Job velocity devs!!!
I'm going to try it again as soon as my class 6 card arrives.
So, do I basically just flash to v0.4 and then flash the non OC kernel right on top of that?
So I tried it yet again (this makes like 6 times) and it was so bad that I couldn't even get it to the point where I could download and flash the non OC kernel. I then tried the Punisher ROM just for _____ and giggles and it works perfectly. I even OC'd it with set CPU and it is still fine. So...... I don't think my problem is that my phone can't handle an OC kernel. Any ideas.... anyone?
connect your phone to your computer > format phone > flash v.4 > mount usb storage and push your non-OC kernel through. that's what i had to do (i have a class 4 card so class 6 isn't the problem)
I'm also having some button issues. My Home, Search, and Send button aren't working with Velocity 0.4. Send I really couldn't care much about, but not having Search and Home is starting to get on my nerves (especially since not having a Home button really kills multitasking.). Everything else about the rom seems to be working great though. Eagerly awaiting a fix for this, since it seems I'm not the only one in this boat.
i have no slide to unlock screen and my home/ send buttons dont work and no notification sounds either.. lol solution? everything else is amazing btw. lol
Ok. I fixed it. I originally flashed this over punisher. in order to fix this i had to clear caches, dalvik and flash velocity .3 then .4 then reboot. now everything works. great rom.
I cant seem to get it to go past the little red eye thing, does anyone have any ideas? it does the eye thing, then after like 30 seconds or a minute goes back and says droid again. i let it do it for a min or 2, but don't know what else to do, i even tried going back to v.3 and all it does is get stuck at the velocity screen. Help please
edit: it did say that the install was successful by the way...i don't really know what to do :/
Last edited by johnson90512; December 29th, 2010 at 02:46 AM.
Device(s): T-Mobile G1, LG Ally, Motorola Atrix 4G
Carrier: Not Provided
Thanks: 7
Thanked 0 Times in 0 Posts
so after much trial and error i got from V0.3 to V0.4 but for whatever reason i cant even get into recovery anymore without it hanging on the LG logo...
between this and the lack of the send/home/camera keys and the same bugs everyone else is having idk what to do.
And for the record Great ROM and thank you Trident!
so after much trial and error i got from V0.3 to V0.4 but for whatever reason i cant even get into recovery anymore without it hanging on the LG logo...
between this and the lack of the send/home/camera keys and the same bugs everyone else is having idk what to do.
And for the record Great ROM and thank you Trident!
like what were your problems
Last edited by johnson90512; December 29th, 2010 at 04:24 AM.
Ok so I think I may have found a solution to the youtube problem I had. Using astro I copied the youtube apk from system/app and put in on my sd card, just right there in the main directory. then I long pressed the app that was still in the system/app folder and chose edit-delete. Then I opened the Think Free office app, installed the youtube.apk file that I copied onto my sd card and it seems to have worked. If it force closes again, I'll try something else, but at least now it opens and is stored on my sd card.
Device(s): T-Mobile G1, LG Ally, Motorola Atrix 4G
Carrier: Not Provided
Thanks: 7
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by johnson90512
like what were your problems
First time i flashed the ROM and Kernel i lost Root. I went into CWmod to make a new backup but my phone wasnt having it. Next up i tried wiping my cache / dalvik and i was getting a weird "E:Can't mount /dev/block/mmcblk0p2
(File exists)" error,
and after wiping data and reinstalling Z4Root i got root back and everything was fine, then my buttons stopped working after i restored my apps and data in Titanium, it was at this point that the phone stopped going into recovery either via the 3 button press on startup or through CWMod.
So nowIt just hangs at the LG logo, but it boot fine regularly except for the missing button syndrome. Also my auto-landscape seems to have died with the buttons, it only rotates when the keyboard is open.
EDIT: i ended up flashing the AmonRa Recovery tool instead and managed to wipe everything and reflashed V0.4 and everything is groovy now, all the keys and orientation and everything.
Last edited by CommodoreOfChaos; December 29th, 2010 at 06:15 PM.
For what it's worth.....I see lots of issues here others are having with the new release. Perhaps I am the exception. Except for a few lost settings, everything went smooth as silk with my upgrade from v0.3 to v0.4. All my backups were intact when I restored them....absolutely NO problems like the ones described. The new ROM appears to be as solid as a rock. Way to go Trident. Seems you hit this one out of the park.
Device(s): Nexus 4, Nexus 7 (Retired: Galaxy Nexus, DX2, DInc 2, DInc, LG Ally)
Carrier: T-Mobile
Thanks: 6,249
Thanked 2,405 Times in 1,447 Posts
Quote:
Originally Posted by CommodoreOfChaos
First time i flashed the ROM and Kernel i lost Root. I went into CWmod to make a new backup but my phone wasnt having it. Next up i tried wiping my cache / dalvik and i was getting a weird "E:Can't mount /dev/block/mmcblk0p2
(File exists)" error,
and after wiping data and reinstalling Z4Root i got root back and everything was fine, then my buttons stopped working after i restored my apps and data in Titanium, it was at this point that the phone stopped going into recovery either via the 3 button press on startup or through CWMod.
So nowIt just hangs at the LG logo, but it boot fine regularly except for the missing button syndrome. Also my auto-landscape seems to have died with the buttons, it only rotates when the keyboard is open.
EDIT: i ended up flashing the AmonRa Recovery tool instead and managed to wipe everything and reflashed V0.4 and everything is groovy now, all the keys and orientation and everything.
First and foremost, I want to thank Trident (and all of the testers and other devs who made this version possible) for yet another amazing rom. When I got my Ally, I tinkered until I happened upon this forum and the rest is history. I've been waiting for this release and am pleased to report not one single problem. Trident, expect a donation by my next paycheck or two. Thank you for all of your hard work.
The reason I quoted the above is quite simple. When I first rooted and flashed I used ClockWork...but I began to have problems even when proper wipes were executed. ROM Manager was also just problematic as an app. When I changed to Amon-RA RECOVERY, my problems went away. It contains more options and gives me peace of mind because I CONTROL every aspect of the recovery process. I have also found that the partitioning that occurs through the Amon-RA RECOVERY is stable and has no mounting issues. I suggest all users to Flash or Zip Amon-RA RECOVERY. I feel as if this is why I've had no issues flashing Velocity 0.4, having the Velocity Backup work without a hitch, flashing the updated radio, and OCing (which I'm still working on figuring out what Frequency works best for my device since not all Ally's were created equally).
Again, Trident, thank you for the countless hours you and your team put in to make my smart phone experience amazing. Who needs a F#%@!(^ iPhone! DROOOOOOOOOOOOOOOOOOOOOOOOOOOID!
Thank you,
JMAR
btw...I love the droid sound package. Plus quadrant scores put us ahead of the DROID ONE
EDIT: 806 OC is working great for my device...is anyone having success with 864?
EDIT2: Had some issues recently at 806 OC. 787 works fine with no kernel panics, but the OC seems to set back to 600 with out a reboot. I open Terminal and su, then cpu to find that I'm back to 600. Anyone dealing with this?
Last edited by jmar; January 11th, 2011 at 02:37 AM.
Reason: Overclock number
The Following 2 Users Say Thank You to jmar For This Useful Post:
First off, Bryan... I would like to say I love Velocity. Keep up the good work!
But after formatting my SD, my phone, reflashing my recovery, clearing my DATA, my CACHE, my Delvik... everything. Over and over. Flashing your ROM over other ROM's like the lightweight one and such, this phone will not boot using Velocity 0.4.
It gets stuck at the droid boot up animation and restarts it periodically but never actually boots.
This doesn't happen with any of the other ROM's out there and does the same thing with all of Velocity ROM's.
Would you care to help out? I would really love to use this new release of yours. I even follow you on Twitter :P
First time i flashed the ROM and Kernel i lost Root. I went into CWmod to make a new backup but my phone wasnt having it. Next up i tried wiping my cache / dalvik and i was getting a weird "E:Can't mount /dev/block/mmcblk0p2
(File exists)" error,
and after wiping data and reinstalling Z4Root i got root back and everything was fine, then my buttons stopped working after i restored my apps and data in Titanium, it was at this point that the phone stopped going into recovery either via the 3 button press on startup or through CWMod.
So nowIt just hangs at the LG logo, but it boot fine regularly except for the missing button syndrome. Also my auto-landscape seems to have died with the buttons, it only rotates when the keyboard is open.
EDIT: i ended up flashing the AmonRa Recovery tool instead and managed to wipe everything and reflashed V0.4 and everything is groovy now, all the keys and orientation and everything.
I ended up fixing mine at 6 am this morning, after the problem being that I guess I didn't format that ext partition on my sd. so, I sacrificed a little memory on my card by just deleting the partition, and remaking it.
First off, Bryan... I would like to say I love Velocity. Keep up the good work!
But after formatting my SD, my phone, reflashing my recovery, clearing my DATA, my CACHE, my Delvik... everything. Over and over. Flashing your ROM over other ROM's like the lightweight one and such, this phone will not boot using Velocity 0.4.
It gets stuck at the droid boot up animation and restarts it periodically but never actually boots.
This doesn't happen with any of the other ROM's out there and does the same thing with all of Velocity ROM's.
Would you care to help out? I would really love to use this new release of yours. I even follow you on Twitter :P
this was basically the problem that I was having, and I know that I cleared everything that way I normally do when I flash. Do what I did, and just pop it into your computer, using maybe an adapter, or if you can another phone, then right click on my computer and click manage. Go to disk management, and the locate your card, and delete the smaller partition. worked like a charm
Alright, judging by the positive responses I will assume I am one of the few people having this problem. When flashing this ROM everything goes smoothly, the first time it boots up, everything goes smoothly. When I try to change the wallpaper it will take me back to the homescreen and nothing changes. When I reboot my phone the home, phone, and search button don't work. Also, all of the widgets have switched screens. If anyone is experiencing similar issues please let me know.
Ok so I think I may have found a solution to the youtube problem I had. Using astro I copied the youtube apk from system/app and put in on my sd card, just right there in the main directory. then I long pressed the app that was still in the system/app folder and chose edit-delete. Then I opened the Think Free office app, installed the youtube.apk file that I copied onto my sd card and it seems to have worked. If it force closes again, I'll try something else, but at least now it opens and is stored on my sd card.
after copying to my SD folder in Astro I received an "error while deleting" when trying to delete the file
To everyone that is having problems. What kind of microSD card are you trying to use? I'm telling you, I literally installed Velocity 4 about 6 times when I had my stock microSD. I just could not get it to work. I absolutely, positively do know how to properly install a new ROM, so it wasn't something I was doing. I got a class 6 and tried it again. BAMMMM... 1st try... no problems at all.
To everyone that is having problems. What kind of microSD card are you trying to use? I'm telling you, I literally installed Velocity 4 about 6 times when I had my stock microSD. I just could not get it to work. I absolutely, positively do know how to properly install a new ROM, so it wasn't something I was doing. I got a class 6 and tried it again. BAMMMM... 1st try... no problems at all.
It works fine with MT stock class 4 card.
The Following User Says Thank You to Valkerie For This Useful Post:
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Color changer
I have updated the:
Color Changer
Now it is menu driven. Executes faster, easier to add new colors to, and what all of you are concerned with: More colors. I added Android Green, Baby Blue, Cyan, Gold and Royal Purple.
If you have more colors that you think should be on the list please let me know.
The zip is recovery flashable. I HAVE ONLY TESTED THIS ON VELOCITY 4, thats what I wrote it for, if you flash this to another rom and FUBAR your install - dont be surprised.
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Recovery
Ok guys, I know this is a reiteration but it is very important to wipe your EXT partition.
ClockworkMOD recovery DOES NOT have the ability to successfully wipe the partition, so if you have had a2sd in the past with Raptor, V3, or Punisher you WILL need to either clear out the EXT Partition (/dev/block/mmcblk0p2) through a terminal in recovery (which will require mounting the partition manually then performing a rm -R on it) or flashing Amon-RA recovery!
The easiest way to get Amon-RA on is to flash alternate recovery though the Rom Manager, however as many of you are most likely stuck in a boot loop having this problem I WILL try and make a recovery flashable package to reflash your recovery to Amon-RA from clockwork as soon as I get a minute.
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Clockwork - AmonRA FlashPACK
THis is an older version of AMON-RA
but it will work for wiping ext, I dont have time to repack the 1.2.5 this is 1.2.4 mayhap someone can do that for me. This is a zip that you flash in recovery, to change your recovery to amon-ra which will wipe your sd:ext much better.
This is from drellisdee's recovery post Get it now
This version of amon-ra doesnt support directory browsing, so zips will need to be in the "root" of your sdcard (just on the sd not in a subdirectory)
Now it is menu driven. Executes faster, easier to add new colors to, and what all of you are concerned with: More colors. I added Android Green, Baby Blue, Cyan, Gold and Royal Purple.
If you have more colors that you think should be on the list please let me know.
The zip is recovery flashable. I HAVE ONLY TESTED THIS ON VELOCITY 4, thats what I wrote it for, if you flash this to another rom and FUBAR your install - dont be surprised.
i was trying to boot into recovery to flash a theme & when i did i received a blue screen with a message that reads "Fastboot mode started udc_start()" any ideas with this is?
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 bnitty
i was trying to boot into recovery to flash a theme & when i did i received a blue screen with a message that reads "Fastboot mode started udc_start()" any ideas with this is?
This means that your recovery did not sucessfully flash, or was lost in some other way. You will need to reflash recovery, the easiest way to do this is by downloading rom manager from the market. I would recommend flashing the alternate recovery (available towards the bottom)
PS. That blue screen is called fastboot, if you have the drivers you can flash recovery directly from there, I believe drellisdee has instructions in his "custom recovery is here" thread
This means that your recovery did not sucessfully flash, or was lost in some other way. You will need to reflash recovery, the easiest way to do this is by downloading rom manager from the market. I would recommend flashing the alternate recovery (available towards the bottom)
PS. That blue screen is called fastboot, if you have the drivers you can flash recovery directly from there, I believe drellisdee has instructions in his "custom recovery is here" thread
anyway to turn Fastboot off because it comes on every time i power up my phone
Device(s): Galaxy Nexus (CM10 Nightlies) and too many old devices to list
Carrier: Not Provided
Thanks: 259
Thanked 706 Times in 265 Posts
Thats no good, even if you power on the device without holding down any keys it goes to fastboot? You may need to pull the battery for a second, then try booting again.
Okay, i've only had two problems with velocity so far and i need some help. First, i went to watch a clip and it asked me which video player i wanted to use, i clicked droid video player and checked dont ask again. i went to watch the video and it is in black and white, and so is every video i try to watch now. how do i get it back to android video player? also, my nfl mobile won't load past the load screen.
I was so afraid it was looping because I had the red eye going like it was v.2 and v.3 had the metal velocity name so I figured v.4 would have something completely new. SO glad that this is running on my phone right now.