Now the only problem is that I've worn my battery down, so I'm going to have to wait until tomorrow to try the actual flashing. It would probably be unfortunate if the battery died in mid-flash.
Now the only problem is that I've worn my battery down, so I'm going to have to wait until tomorrow to try the actual flashing. It would probably be unfortunate if the battery died in mid-flash.
Plug your phone into your computer via usb, and flash that way. That's what I did my first time
Thanks, skater. I ended up just going to sleep and letting it charge up. Applying the ROM from the SDCard worked just fine this morning. Thanks again for all the help, everyone! And, drelisdee, thank you for the recovery image.
I'm glad I got it working, but more importantly, I'm pretty sure I understand why I did everything I did.
Just an FYI and notice to Drellisdee, I've been using the v1.2.3.img recovery and I had made 3 different nandroid backups. Whenever I went to restore to any of the backups, even the first which was very different from the last, it always seemed to restore the last, or whatever the case, didn't seem to restore the first one. I removed the last two backups off of the sdcard and left only the first one, and the restore worked just fine. so i'm not sure what is going on, something to fix though.
drelisdee, will we be prompted for the OTA update if we are running your recovery? I am running Velocity 0.2, which I know doesn't block it itself. I'm trying to decide whether I should go ahead and flash back to stock and apply the update by hand. I'd rather not if it can be avoided, but if I'm going to get prompted to apply the update every half hour then I figure I might as well just do it now. There are a lot of conflicting reports on the forum.
I did a little peruzing in drellisdee's media sharing folder and found the signed_VZB_rooted_deodex_radio_1015.zip file in there. I flashed that and then flashed his Turbo4 without kernel on top. With just the rom flash, linpack got 3.9 or so average. With the turbo4 and no kernel, it got 7 or so average. So far, i haven't gotten any update notifications, even though my system info still says VZ8. Is that supposed to change? Anyways, everyone is sure talking up velocity 3.
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
Quote:
Originally Posted by jetblack
drelisdee, will we be prompted for the OTA update if we are running your recovery? I am running Velocity 0.2, which I know doesn't block it itself. I'm trying to decide whether I should go ahead and flash back to stock and apply the update by hand. I'd rather not if it can be avoided, but if I'm going to get prompted to apply the update every half hour then I figure I might as well just do it now. There are a lot of conflicting reports on the forum.
You will get prompted. Recovery doesn't stop the OTA from downloading.
However, accept and it'll reboot and attempt to install and fail, then you'll be free of the nag.
The Following User Says Thank You to darkxsun For This Useful Post:
Ok quirk with nandroid restore with 1.23 it restores the lastest backup no matter which is selected. Work around for now change the backup you want into latest or run from adb in recovery nandroid-mobile.sh -r and you can then select correct backup. Im currently puzzled as to whats causing this.
The Following User Says Thank You to getitnowmarketing For This Useful Post:
Okay I'm a noob and I just rooted my phone, but can someone please explain to me or link me so that I can understand what is a nandroid backup, why I would want one and also why I would want a custom ROM.. Do I need to do this is terminal? I wanna have an awesome super cool phone too!!
Ok quirk with nandroid restore with 1.23 it restores the lastest backup no matter which is selected. Work around for now change the backup you want into latest or run from adb in recovery nandroid-mobile.sh -r and you can then select correct backup. Im currently puzzled as to whats causing this.
Noticed this also, thanks for confirming. Have you seen this in 1.2.2? I feel like it this issue was happening on that recovery as-well?
Noticed this also, thanks for confirming. Have you seen this in 1.2.2? I feel like it this issue was happening on that recovery as-well?
yes it happened on the 1.2x plus ones.
Also if you get error stating to run nandroid-mobile.sh from adb like this error its because your battery level is too low there is a check in it that it has to be 30% plus to run.
Last edited by getitnowmarketing; September 25th, 2010 at 09:37 AM.
Okay I'm a noob and I just rooted my phone, but can someone please explain to me or link me so that I can understand what is a nandroid backup, why I would want one and also why I would want a custom ROM.. Do I need to do this is terminal? I wanna have an awesome super cool phone too!!
-nandroid backup is a full backup of your phone... it is nice to have if you mess up your files or if you want an easy way to get the next verizon update (custom recoveries needed to flash a rom cause OTA updates to fail. If this is the case you have to Re-flash your recovery via pc) -custom roms make your ally look cooler and modifies what apps are install to conserve space, most roms are rooted which means you can run any application.
flashing a new kernel can make the entire system run more efficiently being that it is the base on which the system runs on. i recomend flashing velocity .2 by trident then drellisdee's oc kernel
-you apply these with either with rom manager(root needed) which is found in the market or with allyRR which is found on the fourm
When you tell the update to install and you have custom recovery, on my phone the recovery says it can't be verified and aborts the install, but when I get back to my phone, the home button no longer works and when I hold down the power button instead of 3 options, sound airplane and power, it just gives power so something is detail not right about that.
Lets keep this thread on topic. Myfishbear the instructions to install my recovery are in the first post. AllyRR installs a very very outdated recovery of mine please everyone follow my instructions in the 1st post and use the latest.
-nandroid backup is a full backup of your phone... it is nice to have if you mess up your files or if you want an easy way to get the next verizon update (custom recoveries needed to flash a rom cause OTA updates to fail. If this is the case you have to Re-flash your recovery via pc) -custom roms make your ally look cooler and modifies what apps are install to conserve space, most roms are rooted which means you can run any application.
flashing a new kernel can make the entire system run more efficiently being that it is the base on which the system runs on. i recomend flashing velocity .2 by trident then drellisdee's oc kernel
-you apply these with either with rom manager(root needed) which is found in the market or with allyRR which is found on the fourm
Okay so I got the nandroid backup by following along with this forum and with the very much so appreciated help from dots on the ally channel. I was warned not to use ROM manager because it has glitches, plus it was fun playing around in CMD. Then I installed velocity. I think it updated to 2.1, but not sure. It says so on the firmware, but when it prompted me, I was taken to recovery and it says installation failed. So what do you mean oc kernel? Would like to take my phone to the next level
Only sad part is ... I lost my paid version of easy tether I can't remember which email it was sent to but I sent the company a copy of my bank statement with the program on it to try and see if they'll let me download it again without having to pay a second 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
Quote:
Originally Posted by drellisdee
now in rom manager please read notes at top of post.
AWESOME! This will definately help quite a bit. I see its under alternate recoveries. To resolve the issues with having to go into ADB and move the install-recovery file can we package this as the update.zip you provided earlier? Might be easier than getting people to remember to move the file. Allot of people have a hard time reading directions
AWESOME! This will definately help quite a bit. I see its under alternate recoveries. To resolve the issues with having to go into ADB and move the install-recovery file can we package this as the update.zip you provided earlier? Might be easier than getting people to remember to move the file. Allot of people have a hard time reading directions
simply flash this zip. This will fix the install-recovery.sh issue with both clockwork and my recovery in lieu of doing it in adb or terminal.
Last edited by getitnowmarketing; October 8th, 2010 at 11:47 AM.
Device(s): Samsung Galaxy Nexus, Asus Nexus 7, Motorola Droid 2 (previous: HTC Thunderbolt, Motorola Droid, LG
Carrier: Not Provided
Thanks: 158
Thanked 117 Times in 69 Posts
Regarding the terminal method, it's unnecessary to 'cd' into /system/app if you're going to specify the full path for the file (/system/etc/install-recovery.sh).
I know this is quite old but, I think I am overlooking something simple....When I changed my flash recovery FROM Clockwork to RA-aloha... I went from having A LOT of "viewable" ZIP files THROUGH Clockwork BUT, now through Aloha...when i choose to Install a ZIP..it shows. "E: no ZIP files"
So, Im back to Clockwork. I would like to use the Aloha recovery but, I can not access my ZIP files from it.
I know this is quite old but, I think I am overlooking something simple....When I changed my flash recovery FROM Clockwork to RA-aloha... I went from having A LOT of "viewable" ZIP files THROUGH Clockwork BUT, now through Aloha...when i choose to Install a ZIP..it shows. "E: no ZIP files"
So, Im back to Clockwork. I would like to use the Aloha recovery but, I can not access my ZIP files from it.
Please help.
Thanks in Advance.
For now zips must be in root of sdcard not in a folder. Thats something Koush, who makes clockwork added to be able to browse folders.
So, in other words....for your recovery to show all important. .ZIP files...I can just "move" them to my "root" file?? If not..where in "root" do my. ZIP files need to be placed??
So, in other words....for your recovery to show all important. .ZIP files...I can just "move" them to my "root" file?? If not..where in "root" do my. ZIP files need to be placed??
Correct in sd card not in any folder. I'm testing an update to recovery that allows zips in any folder currently.
The Following User Says Thank You to getitnowmarketing For This Useful Post:
Correct in sd card not in any folder. I'm testing an update to recovery that allows zips in any folder currently.
I tossed you a, "thanks" just because you are working on an update that would save me some frustration and making my life (and lots of other users lives ) easier.
I know you hear (read) this a lot....but, thank you very much for all you've done AND STILL doing for this lil, "somewhat~smart phone"
Your work is VERY appreciated.
Thx again!
P.S. Could u either reply or PM me 'your' suggested instructions on -how to get my files "onto root", as I am man enough to admit. ..I have just a slight idear as to how to go about this. Thx. ...3x's now...lol
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 244
Thanked 178 Times in 155 Posts
Backup Google proprietary system files?
In the RA-Aloha 1.2.4 Backup/Restore submenu there are listings for backing up and restoring "Google proprietary system files". I am guessing these files do NOT get backed up when using the NAND +* options above those listings in that menu. What kinds of files are these and are they essential if restoring a backup?
Also, where are the Google proprietary system files backed up to? I have 2 Nandroid+EXT backups in the SD/nandroid/mem=233 folder, and then ran the Backup Google proprietary system files command. Back in Velocity I viewed the files on the SD card and do not see any change to the contents of the nandroid backup folder.
I would like to learn how to decode those nandroid backup file names. I thought it was just the YR-MO-DAY and a time code, but I made 2 backups on Jan 2nd, and the 2nd one has 20110103 in it instead of 0102?
Thanks!
__________________ - Zoandroid -
liberum enim electronic fabrica
Last edited by Zoandroid; January 3rd, 2011 at 12:04 AM.
I am rooted with super one click on my ally which gave me no fast boot can I just follow the instructions for rooted users or do I have to go though getting fastboot I want to run the Velocity 1.0 Rom. Thanks for all the hard work! Elwin
Ok I feel like an idiot, but I need help and some of the stuff mentioned just goes over my head. I have a rooted lg ally 2.2.1. I used the rommanager to flash and when it rebooted and i did the flash with turbo4 I got an error and it locked up. I had to reboot but now it gets stuck on the verizon wireless logo. I tried the send/menu/power and it shows the android guy with an exclamation point then jsut skips that and goes back to the verizon wireless logo. Not sure where to go. Any help would be greatly appreciated. I am more than willing to send a donation to get this fixed.
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 244
Thanked 178 Times in 155 Posts
i suggest you try going to the Ally IRC chat room and seeking help there. Your problem sounds beyond my abilities, but I am sure some of the people who hang there will offer help and likely a solution, and it is in real time. They have been tremendously helpful to me as well as to countless others. One of the most helpful people will have some variant of his "Dots" member name logged in there when he is available (which seems to be almost all the time!).
If you are not familiar with Ally IRC, go here for access and a brief description:
i suggest you try going to the Ally IRC chat room and seeking help there. Your problem sounds beyond my abilities, but I am sure some of the people who hang there will offer help and likely a solution, and it is in real time. They have been tremendously helpful to me as well as to countless others. One of the most helpful people will have some variant of his "Dots" member name logged in there when he is available (which seems to be almost all the time!).
If you are not familiar with Ally IRC, go here for access and a brief description:
Ya it sounds like I bricked it and trying another way, but probably going to have to call and state it messed up while doing an OTA update. Thanks for the reply.
In the RA-Aloha 1.2.4 Backup/Restore submenu there are listings for backing up and restoring "Google proprietary system files". I am guessing these files do NOT get backed up when using the NAND +* options above those listings in that menu. What kinds of files are these and are they essential if restoring a backup?
Also, where are the Google proprietary system files backed up to? I have 2 Nandroid+EXT backups in the SD/nandroid/mem=233 folder, and then ran the Backup Google proprietary system files command. Back in Velocity I viewed the files on the SD card and do not see any change to the contents of the nandroid backup folder.
I would like to learn how to decode those nandroid backup file names. I thought it was just the YR-MO-DAY and a time code, but I made 2 backups on Jan 2nd, and the 2nd one has 20110103 in it instead of 0102?
Thanks!
Thats an option to backup google stuff for cyanogen mod roms that I never fully implemented. Nandroid fully backs-up them.
Noobinfo
I can't remember which email it was sent to but I sent the company a copy of my bank statement with the program on it to try and see if they'll let me download it again without having to pay a second time.
The mAndroid Connection
