Database Info

[A510][RECOVERY][2012-12-15] CWM-based Recovery 6.0.1.9 (JB compatible)

CWM-based recovery 6.0.1.9 for the Acer Iconia TAB A510​
Another recovery build? Yes... But I can say this recovery is pretty safe. Having said that, however:
*** I am not responsible for anything that happens to your device ***
There is still a risk in bricking your tablet​
I've been testing various different ways to get custom ROMs going on this tablet, for over 6 months now. Developing for this tablet seems kinda dangerous (compared to my private building on HTC devices), and I already had to send my device back to Acer because of a brick once. At this point, I guess this recovery seems pretty safe, and hence I'm willing to release it in public. This recovery is inspired by the CWM-based recovery 6.0.1.1 for the Icona TAB A700 by pawitp. So first of all, I want to say thanks for his work and the talks we had.
The recovery itself is built by me so all partitions on the A510 are propely initialized, sized, and mounted: Including access to both internal storage (the 'fake' sdcard) and external MicroSD cards, as well as the flexrom partition. As an additional (see below) precaution, i've supressed 'EMMC wipe' commands in the recovery.
The kernel for this recovery has been compiled by me, disabling all the MMC_CAP_ERASE functions to prevent the 'Samsung EMMC brick' from happening. This does not give you a 100% guarantee, but it comes pretty close.
As explained in this post, the new CWM recovery does not really format your /data partition. It simply removes all files with the 'rm' command, leaving your 'fake' sdcard intact. The recovery in this post does format your other partitions, but it should show this message: 'warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware'. Don't worry, that's a good thing!
Things to note:
I have mounted every partition with this recovery without problems
I have formatted/wiped every partition with this recovery without problems
I have backed up and restored (nandroid) every partition with this recovery without problems
I have installed custom .ZIP files with this recovery without problems
I still won't give you any warranties - This recovery can brick your tablet
How to install:
Step 0:
Check this thread to see if you can help the community before you let us help you!
Step 1:
Copy the file attached to this post (remove_recovery_from_rom.zip, (MD5: 73aea1147f571a83caeb8743cd5972b4)) to your tablets internal memory or SD Card. Download the CWM-Based Recovery by NoThrills for A510 tablets and save it somewhere on your computer.
Step 2:
If your device is already bootloader unlocked, skip step 3. Your boot screen (the one with the Acer logo when you turn the device on) should read Bootloader Version x.xx.xx-ICS (Unlock Mode). If your device is not yet unlocked, continue to the next step:
Step 3:
Connect your tablet to your computer via USB. Make sure you have the Android SDK installed, and perform the following command:
adb reboot-bootloader
When the tablet reboots to the Acer logo, perform the next command:
fastboot oem unlock
Then, quickly press the Volume down (**) button on your tablet, followed by the Volume up (*) button to confirm the unlock. When done:
fastboot reboot
Step 4:
Connect your tablet to your computer via USB. Make sure you have the Android SDK installed, and perform the following command:
adb reboot-bootloader
When the tablet reboots to the Acer logo, perform the next command:
fastboot flash recovery recovery_nothrills.img
This assumes you have put the nothrills_recovery.img in the same folder as the ADB utility.
Step 5:
Reboot your tablet with the following command, but you have to keep the Volume down (**) button pressed when the tablet boots:
fastboot reboot
Step 6:
Install the remove_recovery_from_rom.zip file from the Recovery, then reboot your device.
Your tablet now has this new recovery installed. You can enter the recovery by typing the command adb reboot recovery, or by booting your tablet with the Volume down (**) button pressed.
​
Downloads:
CWM-Based Recovery 6.0.1.9 (mirror) (mirror)
(MD5 for .img: 950b877a8d10d7de80ec7055b6367893)
CWM-Based Recovery 6.0.1.4 (mirror) (mirror)
(MD5 for .img: b0f9d33342943b44b998bd8f127800a8)
CWM-Based Recovery 6.0.1.3 (mirror) (mirror)
(MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Stock Acer 1.044.00 recovery (mirror) (mirror)(note: you only need this to return to a stock Acer recovery)
(MD5 for .img: 7b58b9b76c4e39cafa9d926b57fe08fd)
Anything else?
That's what this thread is for, so post away...

Reserved

Great news! I'll have a try after i get my tab back.
btw, is there any Custom Rom available for A510?

finally we have CWM! Can´t wait to get CM10 on my A510!
Seems to work quite well, so far no probs - thank you

Great news just wish I new how to use adb.I have read so many ways on how to use it but can never get it to work.Now we need to get roms built.Is there anyway to get it to work with the Acer toolbox.

Great, thanks !

Great piece of news!

jessejames44 said:
Great news just wish I new how to use adb.I have read so many ways on how to use it but can never get it to work.Now we need to get roms built.Is there anyway to get it to work with the Acer toolbox.
Click to expand...
Click to collapse
Make sure to have the required DLLs in the same directory you are executing adb from (or in a specified PATH).
Sent from my A510 using xda app-developers app

Well I flashed this and even though it says the recovery is successfully written, when I reboot into recovery all I get is the android with the red exclamation mark and it never boots into the recovery at all??? weird.

Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope

Omnius001 said:
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Click to expand...
Click to collapse
I have tried both of the files from the regular and the mirror sites and it says it completed ok, but I still do not have the custom recovery. I have done this many times on different devices and this is the first time it does not work, I am following the instructions by the letter too. LOL!!!

Anyone with A511 tested it ?

Omnius001 said:
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Click to expand...
Click to collapse
Does anyone know if this could be flashed using terminal emulator. Using ADB I get confirmation that it sent and wrote the files ok to the tablet, but I still just get the dead android with the red exclamation when I try booting into recovery, regardless of wheather I use adb or the button holding methods.

Jesse6749 said:
Does anyone know if this could be flashed using terminal emulator. Using ADB I get confirmation that it sent and wrote the files ok to the tablet, but I still just get the dead android with the red exclamation when I try booting into recovery, regardless of wheather I use adb or the button holding methods.
Click to expand...
Click to collapse
Have u checked the MD5? (MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Maybe u should download the file again and make sure the MD5 correct.

jokerzlh said:
Have u checked the MD5? (MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Maybe u should download the file again and make sure the MD5 correct.
Click to expand...
Click to collapse
I did check the MD5 and it matches the MD5 on the OP and on your post as well, so the file is good. I have re downloaded the file 4 times already too.

Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.

Mechkilla said:
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Click to expand...
Click to collapse
This is what I'm thinking as well. I should probably edit the instructions on the first post, as I didn't think about the fact that people might not have the recovery_from_boot files removed.

Mechkilla said:
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Click to expand...
Click to collapse
I just followed the instructions and rebooted into ICS then ran the adb reboot recovery command. So you are saying to run the adb reboot recovery command immediately after it finishes flashing. I may just try this later today. I got it to boot into recovery once and then went back to the dead android, then I followed the updated instructions on the op and now it works every time and it boots into the CWM recovery every time.
Sent from my Transformer Prime TF201 xda premium

Jesse6749 said:
I just followed the instructions and rebooted into ICS then ran the adb reboot recovery command. So you are saying to run the adb reboot recovery command immediately after it finishes flashing. I may just try this later today.
Sent from my Transformer Prime TF201 xda premium
Click to expand...
Click to collapse
I've updated the first post with a 'remove recovery' .ZIP file. Follow the new instructions and you should be set.

Super cool to see the development for the A510 finally with some results!!!! I love tyo get some custom stuff for our A510's...is there anything I can help you with? If there's something I could do to speed up the custom ROM process, just ask

[Q] [HELP] device booting directly into fastboot

ok, i guess i screwed up, didnt make nandroid etc, but lets put that aside.
i installed xenonhd the other day, and then the matr1x kernel. since i was not satisfied with matr1x, i wanted to change the kernel. i downloaded franco and flashed it.
not my device instantly boots into recovery without me even pushing volume+ button. on the top of the screen there is a red message: "fastboot mode - no boot or recovery img". i dont think this message was there before.
anyway, i wanted to just reflash the system again with xenonhd rom, but its not on the sd memory. now i tried to push it on the device with adb, but when i do "adb device", my device doesnt appear in the list. the list is empty. however, "fastboot device" does show the device.
ok, the big question: how do i get the rom (zip file) on the device so i can reflash it from recovery? recovery is working.

Try to reflash an entire boot IMG. It might work, but you'd lose everything.
This happened to me once, I got that message too.. But I couldn't do anything at all.. I think my sdcard was dead. I had to send mine into Sammy repair.
Sent from my Nexus S using xda app-developers app

what do you mean by boot img? you mean a complete rom?
the rom i have is xenonhd, it does come in a zip file, not as am img file.

murfi said:
ok, i guess i screwed up, didnt make nandroid etc, but lets put that aside.
i installed xenonhd the other day, and then the matr1x kernel. since i was not satisfied with matr1x, i wanted to change the kernel. i downloaded franco and flashed it.
not my device instantly boots into recovery without me even pushing volume+ button. on the top of the screen there is a red message: "fastboot mode - no boot or recovery img". i dont think this message was there before.
anyway, i wanted to just reflash the system again with xenonhd rom, but its not on the sd memory. now i tried to push it on the device with adb, but when i do "adb device", my device doesnt appear in the list. the list is empty. however, "fastboot device" does show the device.
ok, the big question: how do i get the rom (zip file) on the device so i can reflash it from recovery? recovery is working.
Click to expand...
Click to collapse
Recovery is working?
Then you boot into recovery, and mount USB storage in Mount and storage section in CWM. Once you mounted it, unplug and replug your cable for the drive to show up.
It's important your recovery be v6.0.1.0 or older because the newer versions have a USB mounting bug with the Nexus S.

yeah that doesnt work, i have a newer version.
anyway, i figured that the rom zip had a boot.img inside, so i just flashed that file alone. voila, the phone boots again.
thank you guys for your help!!!

murfi said:
yeah that doesnt work, i have a newer version.
anyway, i figured that the rom zip had a boot.img inside, so i just flashed that file alone. voila, the phone boots again.
thank you guys for your help!!!
Click to expand...
Click to collapse
Good job!
That's what FirePoncho meant. Might be a good idea to switch your recovery either to an older version of CWM (6.0.1.0 doesn't have the bug) or to TWRP in case you need it one of these days.

polobunny said:
Good job!
That's what FirePoncho meant. Might be a good idea to switch your recovery either to an older version of CWM (6.0.1.0 doesn't have the bug) or to TWRP in case you need it one of these days.
Click to expand...
Click to collapse
I agree! I've been sticking with CW v 5.0.2.3, cause there are no bugs, and I like using the volume buttons
Sent from my Nexus S using xda app-developers app

Re-root after Kitkat update?

Hi,
I finally managed to update my Moto G to 4.4.2 by flashing stock rom. However, before I did that, my phone was rooted and I used Titanium Backup to back up some files. I then copied that folder to my PC. Now, I have tried to root the phone again using superboot, but my screen goes purple literally 2 seconds after I load superboot and then I have to switch it off and back on again. It hasn't installed SuperSU so I'm assuming my phone isn't rooted any more. I am a total noob in these matters and I really do appreciate all the help given on this site.
I would greatly appreciate if you can help me by getting my files from Titanium backup back up again, and how to re-root my phone. I have searched the forum but I didnt find anything too similar to my situation and I don't understand a lot of the terminology. It took me a really long time to even learn how to flash the stock rom!
So I would appreciate any help. Thank you

Root option 2 doesn't work either. It just says "waiting for device" at the first stage. When I click on recovery, it says no command. USB debugging has been enabled. Im confused!

Put latest superSU zip on /sdcard on phone. Copy across to phone using USB or use airdroid app. Search internet for superSU zip by chainfire developer.
Flash custom recovery CWM (search forum for it). Be sure to get the one for 4.4.2 bootloader.
Boot into CWM recovery (boot to bootloader and choose recovery option using UP volume button) and choose to flash a zip file and then pick the superSU zip.
You are now rooted and have a custom recovery.
For titanium backup, either copy to phone using USB or use airdroid app.
If you still have probs then let me know and I can give more detailed instructions tomorrow when I am at my laptop along with links to files needed.

scott_doyland said:
Put latest superSU zip on /sdcard on phone. Copy across to phone using USB or use airdroid app. Search internet for superSU zip by chainfire developer.
Flash custom recovery CWM (search forum for it). Be sure to get the one for 4.4.2 bootloader.
Boot into CWM recovery (boot to bootloader and choose recovery option using UP volume button) and choose to flash a zip file and then pick the superSU zip.
You are now rooted and have a custom recovery.
For titanium backup, either copy to phone using USB or use airdroid app.
If you still have probs then let me know and I can give more detailed instructions tomorrow when I am at my laptop along with links to files needed.
Click to expand...
Click to collapse
Thank you very much for your help. Just a few questions if you dont mind. How do I put the SuperSU zip on the /sdcard part of the phone? When I access my phone via the pc, i cant find that folder.
Also, how do I go about flashing the custom recovery CWM. I don't know how to do this. The rest I should be OK with.
Thanks again pal

Go to android development section and follow the cwm 6.0.4.6 guide you can get the latest supersu from chainfire website just DL the zip plug your phone in and open your device and place the zip there. Then when you flash cwm don't reboot just move on to updating SD card and flash the super Su zip
Sent from my XT1034 using xda app-developers app

tiger123uk said:
Thank you very much for your help. Just a few questions if you dont mind. How do I put the SuperSU zip on the /sdcard part of the phone? When I access my phone via the pc, i cant find that folder.
Also, how do I go about flashing the custom recovery CWM. I don't know how to do this. The rest I should be OK with.
Thanks again pal
Click to expand...
Click to collapse
When you access phone via PC do you see a list of directories, eg data, documents, pictures. If so that is the sdcard. Just put the superSU zip in any folder, or just copy it across so its not even in an actual folder. As long as its on there its fine.
If you don't see the folders then maybe you don't have the right drivers for the phone. In this case may be easiest to use airdroid app.
You may need drivers for fastboot below though anyway - not sure on windows as I use Linux. Bit of reading on forums should help with that.
CWM - have you used fastboot before? Basically fastboot is a program you put on your PC to allow you to flash images to your phone. You will enter a command like
fastboot flash recovery cwm.img
Where cwm.img is the CWM recovery file. You need to be in the bootloader to allow the phone to accept fastboot commands. The cwm.img is then flashed to the phones recovery partition.
Check the forums for a link to a fastboot program, that's the easiest way to get it.

Honestly, thank you so much for your help guys, a special thanks to you scott. I kinda understand now!
Now, I did all that, but I got a problem. When I try to flash CWM by using "fastboot flash recovery recovery.img"
On my phone, it says mismatched partition size (recovery). Also, a bit off topic but when I try to restore factory settings, the phone doesn't do it properly. The android logo comes up....then it disappears, then appears again and disappears and so on.
Have I messed something up?

The partition mismatch is fine try factory reset on the phone setting not by recovery and see if that works
Sent from my XT1034 using xda app-developers app

Thank you so much guys. Got it sorted now. God bless
Sent from my XT1032 using XDA Premium 4 mobile app

[Q] Help Needed: Unbrick my P500!

Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh

Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app

agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.

xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..

agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2

ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1

CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.

agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2

Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..

[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:

Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..

Recovery.sh

Hello...
I made a mistake and flashed my recovery with out renaming my recovery.sh file.... I am rooted and unlocked status code 3. I am also updated on stock ROM. I need to back up and switch ROM's. I original flashed recovery with ROM Manager and got no results. Then I used a flash tool but failed to read the instructions on the thread before flashing. I have since then flashed several TWRP and CWM versions, as well as stock to no avail. When I select recovery from the boot menu I see the red Motorola emblem for a few minutes then it reboots normally. Does any one have a fix and or the recovery.sh file. Thanks.

Download the latest TWRP and place in your fastboot folder. Disconnect your phone from the computer, boot into fastboot, and then plug your phone in. Wait for the phone to connect. After it's connected type "fastboot flash recovery recovery.img." Recovery.img will be the name of whatever file you downloaded. After flash is complete, unplug phone and power off. Immediately boot back into recovery. Do not boot into OS.
With this method, you don't need to rename recovery.sh. Rebooting directly into recovery allows the updater script to complete, so the stock recovery doesn't take over. If you boot right back into OS, stock recovery will override.
If you can't do fastboot, download Flashify and use that app to flash the TWRP you downloaded. TWRP for this phone is not official, so it won't show up in ROM or TWRP Manager. You'll have to DL off here.
Sent from my HTC6525LVW using Tapatalk

Thank you for your detailed reply, I will try this tonight and let you know how it goes, I suspect it will work.
Sent from my Barnes & Noble Nook Tablet using XDA Free mobile app

You're welcome, hopefully one of methods will work for you.
Sent from my HTC6525LVW using Tapatalk

Thank you! Worked like a charm. Renaming the file Recovery.IMG, disconnecting my USB cable, powering down and rebooting directly into recovery is what I did not do. Doing that has solved the problem!
Sent from my Barnes & Noble Nook Tablet using XDA Free mobile app

Custom recovery unrooted my stock updated ROM.. Be careful!

Custom recovery has an option to root or you can flash SuperSU in recovery.

Well I kinda bricked it any way lol, but I fixed it with HouseOfMoto I think. At least I see the boot screen now...

Yep seems to have booted this time I will flash TWRP instead of CWM.