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
Related
Hellooooooooooooooooooooooooooooooooo!!!
this is my first thread in this forum, mi name is Nicolas and i ve a very big problem with my new tablet.
I was trying to install the new Jelly Bean (OS_Acer_RV09RC08.WW.GEN1_A41J_A) and everything was OK
I unlocked the bootloader .......and....
I try to root and just bricked....
Everytime i turn on the tablet i can see the "Acer logo" and the line: Bootloader Version JB-653b3d3 (Unlock Mode)
I cant get into the recovery mode.....
Sorry for my bad english....i need your help ppl!!!!
Thanks for ur time.
Nicolas.
May you can get into Fastboot mode and reflash the recovery.
Give it a try =)
Do you have a androids of your original ROM?
I did the exact same thing just yesterday...
If you have a JB image to work from, get it in fastboot mode and look at the thread on CWM Recovery 6.0.1.5...
Sent from my A700 using xda premium
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
freejack84 said:
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
Click to expand...
Click to collapse
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Moscow Desire said:
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Click to expand...
Click to collapse
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
freejack84 said:
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
Click to expand...
Click to collapse
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Moscow Desire said:
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Click to expand...
Click to collapse
Okay, so since I just did this, I'm going to try and give you a "how to" on how I fixed it...
MD and pawitp both are the authorities on this, but I think this will help and I a, sure they will correct me where I go wrong.
First, use the manual process for getting your A700 in fastboot.. power button + down vol, wait for the first buzz then release only the power button, wait for the second buzz then press the up volume button. Your tab should now be in fastboot mode.
Connect it to your computer.
Get a copy of the proper recovery image "recovery-a700-6015" and the following ROM ( http://forum.xda-developers.com/showthread.php?t=1952124) and save them to a directory where you can find it easily.
Pull the SD card from your tab and put the ROM from above in the base directory and put it back in your tab.
From the c prompt on your computer use the following fastboot command:
Fastboot devices
----#make sure that the computer sees your a700
Fastboot boot <save directory>recovery-a700-6015.img
----#your tab will reboot into CMR Recovery
In recovery format system, data, cache, dalvik
Still in recovery install the ROM from your external SD card.
The Aroma Installer will guide you through it, but make sure you tell it to install the new firmware.
Reboot.
You should be on the stock rooted ACER Great Britain release.
From there you can download and install CM10 (which is what I did), or any other ROM you would like.
Sent from my A700 using xda premium
well.......30 minutes with the tablet and:
I put the tablet in Recovery state with the last instructions.....but now i ve too much errors lines:
Important: all this error are "before" flash again the recovery
The recovery cant:
mount /cache/recovery/command
mount /cache/recovery/log
mount /cache/recovery/last_log
cant open cache/recovery/log
and.....
cant mount SDCARD, EXTERNALSD, SYSTEM, CACHE, etc etc...
when i try to flash again the recovery: <waiting the device> and nothing......i cant put the tablet in fastboot mode.
i have the same problem before. 無得整的, 要上acer換底版的
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Uhmmmm.... didn't I state that the other day?
Glad you got it going Mate :good:
MD
thks ppl
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
:
Click to expand...
Click to collapse
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
LukeRG said:
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
Click to expand...
Click to collapse
LOL
pls step step explain ı recovery my tablet but ı want to back syock rom tablet internal storage not ready in pc ı cant see internal storage ı see only sc card camera dont workk how back to syock rom pls help..
thank's man
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Thank's... you just safe my problem today
u welcome .......
Hello everybody,
I think I have NOT exactly the same problem but very similar.
Let me explain how I got there:
I had JB bootloader and CM11 installed for long and working fine.
Last days I tried out the CM12.1 unofficial rom with successful installation.
I noticed that the camera focus was not working. Usually I never use the camera and was not sure if it worked before. So I went back to CM11 to look if it is rom dependent. In CM11 it still was not working and I went back to stock. The stock rom I found was Android 4.0.4 and I tried to make OTA update what showed me a “not allowed to your device” –error.
However, at this moment I was quite sure that the camera focus is a hardware defect and wanted to go on testing the new CM12.1. I installed it again from CWM recovery and it was not booting anymore.
The problem is, that the stock rom flashed an ICS bootloader which is not compatible anymore. I also cannot boot into recovery anymore but fastboot is working.
Power-On:
shows Bootloader Version ICS-MR1-a055314 (Unlock Mode) and nothing more
Power-On + Vol.Down:
Bootloader Version ICS-MR1-a055314 (Unlock Mode)
Erasing Cache before SD update…
SD update cnd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Then for just a second CWM is shown:
CWM-based Recovery v6.0.5.1
Finding update package
E:unknown volume for path [SDCARD:update.zip]
E:Can't mount SDCARD:update.zip
Installation aborted.
Rebooting...
Then it holds on Bootloader Version ICS-MR1-a055314 (Unlock Mode)
I could not find any button combination to boot something else.
What I tried and what did not make any changes:
Flashing the recovery.img again
Erase userdata, cache, system
Please help me to boot up recovery again and flash a JB bootloader and new rom.
Thanks and kind regards,
Gandlz
Well, in between I found a solution and can answer my own question now:
The trick is to flash the CWM Recovery not to the recovery partition but to the boot partition. (fastboot flash boot recovery.img)
After restarting the tablet it boots directly into CWM Recovery.
I found a newer stock rom with jelly bean android and installed it to come back to JB-Bootloader. Now I could install CM10.2 CM11 or CM12.1 again.
The stock rom is from a german forum:
android-hilfe.de/thema/a700-zurueck-aufs-deutsche-stock-rom-flashen-anleitung-imagefile.329590
By the way: I’m running CM10.2.1 and it is very much faster than CM11 or CM12.1. I don’t need the newer features and like the old design even more. And also the camera focus is working now, so it is definitely a software issue with newer CM versions.
Best regards,
Gandlz
I purchased a new TF300T from BB the other day, and while I have rooted many phones and other tablets (Galaxy Tab, Lenovo A2107), I did some searching but could not find any specific instructions for my Software version.
So, new TF300T with 4.1.1 and 10.4.2.9, I see many threads on how to upgrade to JB and keep root etc, but nothing on how to get this one rooted. From what I read around I have to unlock bootloader, i guess there is no way around that, now what about rooting 10.4.2.9? Is there a how to thread up somewhere here? Since i will be voiding the warranty by unlocking I don't want to eff it up on my first try.
Any help, will be greatly appreciated.
So first off I totally understand the apprehension. I have rooted a lot thingd and this tablet seems especially technical and convoluted.
First read through this thread:
http://forum.xda-developers.com/showthread.php?t=1697227
1) In that thread download the "unlock bootloader" app, run it and unlock the bootloader. Your device warranty will now be void and it will say "device unlocked" in the top left corner every time you boot it up.
2) Now go to this thread, http://forum.xda-developers.com/showthread.php?t=1845377, scroll down to Part 3 and download the "fastboot + JB recovery" files. Extract them into the Fastboot folder that they are zipped in. There will be two .dll files, an ADB file, a Fastboot file and a twrp.blob file.
3) Turn off your tablet. Once it's off press the power and vol/dwn buttons at the same time. Keep holding them down until you see the screen with "RCK", "android", a usb symbol, and "wipe data". Once in that screen let go and use the Vol/dwn to move the cursor and vol/up to select the USB icon. Plug your tablet into your computer and the computer should recognize it as a "fastboot" device. You can check under "devices and printers".
4) Enter the "Fastboot" folder and while holding down shift, right click the mouse. In the menu you should have the option "open command window here". Select that and it will open a cmd window. Type in the line:
fastboot -i 0x0b05 flash recovery twrp.blob
This will copy the TWRP recovery file to the tablet and flash it. You will see a blue progress bar on your tablet while this is happening. Once that is done type:
fastboot -i 0x0b05 reboot
This will reboot your tablet and you will now have TWRP recovery installed.
5)Once in android again, go to this thread, http://forum.xda-developers.com/showthread.php?t=1668173, and download the "root-signed.zip" file in the second post and copy it to the tablet.
6)Turn off the tablet and boot into recovery by holding power and vol/dwn again. Once at the menu select "RCK" with Vol/up. It will boot into TWRP recovery now. Install the "root-signed.zip" file, reboot and the tablet should be rooted.
At this point I recommend creating a backup in recovery in case anything goes wrong from here on out.
Now you can flash any ROM your heart desires. I recommend CleanROM 2.7. It's fast, clean and very easy to install.
TWRP is easily the best recovery for this tablet. I have had many problems with CWM not installing ROM's properly and causing boot issues.
I hope this help you out. I know it's kind of a mine field of information but it works very nicely.
Ramrod421 said:
So first off I totally understand the apprehension. I have rooted a lot thingd and this tablet seems especially technical and convoluted.
First read through this thread:
http://forum.xda-developers.com/showthread.php?t=1697227
1) In that thread download the "unlock bootloader" app, run it and unlock the bootloader. Your device warranty will now be void and it will say "device unlocked" in the top left corner every time you boot it up.
2) Now go to this thread, http://forum.xda-developers.com/showthread.php?t=1845377, scroll down to Part 3 and download the "fastboot + JB recovery" files. Extract them into the Fastboot folder that they are zipped in. There will be two .dll files, an ADB file, a Fastboot file and a twrp.blob file.
3) Turn off your tablet. Once it's off press the power and vol/dwn buttons at the same time. Keep holding them down until you see the screen with "RCK", "android", a usb symbol, and "wipe data". Once in that screen let go and use the Vol/dwn to move the cursor and vol/up to select the USB icon. Plug your tablet into your computer and the computer should recognize it as a "fastboot" device. You can check under "devices and printers".
4) Enter the "Fastboot" folder and while holding down shift, right click the mouse. In the menu you should have the option "open command window here". Select that and it will open a cmd window. Type in the line:
fastboot -i 0x0b05 flash recovery twrp.blob
This will copy the TWRP recovery file to the tablet and flash it. You will see a blue progress bar on your tablet while this is happening. Once that is done type:
fastboot -i 0x0b05 reboot
This will reboot your tablet and you will now have TWRP recovery installed.
5)Once in android again, go to this thread, http://forum.xda-developers.com/showthread.php?t=1668173, and download the "root-signed.zip" file in the second post and copy it to the tablet.
6)Turn off the tablet and boot into recovery by holding power and vol/dwn again. Once at the menu select "RCK" with Vol/up. It will boot into TWRP recovery now. Install the "root-signed.zip" file, reboot and the tablet should be rooted.
At this point I recommend creating a backup in recovery in case anything goes wrong from here on out.
Now you can flash any ROM your heart desires. I recommend CleanROM 2.7. It's fast, clean and very easy to install.
TWRP is easily the best recovery for this tablet. I have had many problems with CWM not installing ROM's properly and causing boot issues.
I hope this help you out. I know it's kind of a mine field of information but it works very nicely.
Click to expand...
Click to collapse
Thank you for the directions. Worked liked a charm. Downloading CleanRom now and cant wait to see how it runs!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
My pleasure!
Thank you very much, you have been of great help.
You're welcome.
Nice TUT Ramrod.
+ 1 on TWRP.
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2
d08speed3 said:
Thank you for the directions. Worked liked a charm. Downloading CleanRom now and cant wait to see how it runs!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I too just got 2 tablets from BB and want to install CleanROM on them but the information was just too overhelming.
Could you share your experience with following the instructions above?
Did you have to read all the threads that were linked?
smokarz said:
I too just got 2 tablets from BB and want to install CleanROM on them but the information was just too overhelming.
Could you share your experience with following the instructions above?
Did you have to read all the threads that were linked?
Click to expand...
Click to collapse
He only linked 3 threads, it's a good idea to at least read the first page or so of each. If it still looks a little daunting, there is a video thread I found to be very helpful, specifically, this video:
http://www.youtube.com/watch?feature=player_embedded&v=zSTf6ZY4NGo
watch this entire video from beginning to end. A couple of things are a little different from the thread (such as flashing CWM instead of TWRP, and installing the SDK to get the ADB and Fastboot files), but it will give you a better idea of what you will be doing with your PC and tablet.
Then go back to Ramrod's post. He linked 3 threads, though you really only need to read the first 2 imo. The first one is more of a reference thread that contains links to the unlock file you need. You can also just go to support.asus.com and download the unlock apk from there (like I did).
The 2nd thread he linked is what I used mostly. Since I did the OTA update to JB, I started at step 3. That will get you recovery and root files you would need to flash.
I then fired up the video I linked above again, and used it as a visual guide to setup my files for flashing and just followed along using the files I got from Ramrod's 2nd link.
Really, all you need to do is install recovery (most recommend TWRP). once you have recovery, you can flash the root files. Or, just flash CleanRom which is a tweaked stock ROM that is already rooted.
Note everything I wrote above worked perfectly for me on my TF300t with the OTA JB update.
For the amateurs. Could you elaborate on these steps?
Step (1) (a) which file to download? the .apk for the .exe file?
(b) Download to where (the tablet or onto a laptop/desktop)?
Step (2): (a) Again, download to where? Tablet or laptop/desktop? And extract to where?
Step (3) & (4): This make it sounds like the files in previous steps should be downloaded and extracted to a laptop/desktop?
Step (5) & (6): CleanRom 2.7 is already rooted. Do we need to run these steps? Or can we install CleanRom after Step 4?
Backup: What files to back up? Everything?
Flash CleanRom 2.7: Do i copy the CleanRom file and put in on the tablet's internal SD card? Then reboot into TWRP to install the rom?
Critical Questions:
Do the above steps work for tablets already on Android version 4.1.1 with .29 (or .17) builds?
Sidenote: Last night, my tablets had an ASUS update and it went from build .29 to .17. Is this strange? It's going backward?
really, just watch the video, it helps a lot.
I did. It only shows the part where you're flashing CWM.
Didn't show anything about unlockingthe bootloader, or flashing the ROM
again, the video thread is very helpful. We can only help you so much. I'd do it for you if I could, but since you have to do this on your own, you really need to read, read, read, so you understand what you are doing before you do it.
unlocking the bootloader
http://www.youtube.com/watch?feature=player_embedded&v=D2ATyGP5JAk
I totally agree about using the video link above.:good:
It gives you the basics of what you are going to need. I tried it with CWM but had problems off the bat with making a recovery backup so I went ahead and flashed TWRP. I also tried the root zip from the video link but was unsuccessful after 2 tries so I went ahead and flashed a custom ROM. Heh, I was gonna do it anyway. lol
I used the rooting and recovery flashing method mentioned earlier and it worked like a charm. Flashed on CleanRom afterwards and that also worked fine. But as i didn't like the resolution i though of re-flashing it as the aroma installer gave me the option to choose the screen DPI. But when I restarted into recovery, I couldn't press the buttons, the screen just refused to react. Flashed back original firmware using the USB fastboot but still nothing.
Anyone that have experienced this or know how to fix it?
I just guessing here, but did you wipe cache after flashing back to original wipe cache or factory reset? Maybe with more knowledge could elaborate.
MrxBurrito said:
I just guessing here, but did you wipe cache after flashing back to original wipe cache or factory reset? Maybe with more knowledge could elaborate.
Click to expand...
Click to collapse
As I lost TWRP recovery when flashing back the original firmware I used the reset data thats found on the original recovery menu. I also tried flashing different versions of the original firmware(.17 & .18). On top of that I also tried using CWM to flash another version of CleanROM (2.5) in case it was something that failed to completely flash when I first did it. But CWM couldn't flash anything properly so I just ended up with bootloops after that. Tried CWM because I can use it with the buttons instead of the screen.
I have reset data several times & used the reset button below the micro SD slot a few times in case it would be some stuck currents.
The most annoying part is that I know that pad is working because I get to the initial setup display when starting it and if I plug it into my computer, I can access the internal memory. It just refuses to react and as I don't have the keyboard, I can't try using a mouse.
Thank you for the help, I'm on jb build 10.4.2.13 & had the same questions as the op since none of the tutorials said anything specific to us. One question I have for those that have rooted, did it speed up your tab? Mine is pathetically laggy while browsing , stock,boat , and chrome browsers all suffer the same. Loading pages takes probably 3-4 Times longer than my gnex does, and when I scroll it hangs , freezes , and sometimes fc's the browser. About an hour ago I downloaded a 7Mb pdf and when I tried to view it , it fc'd with a message about not enough memory. I don't see anything running that is taking large amounts of memory and looking under "apps" I'm using about half the available ram but I could be missing something . Bottom line I want to know if I should return this thing or if rooting and removing some of the bloat will improve its performance. Hope I didn't take this too far off topic. Thanks again for the rooting info.
Thanks for the tut ramrod, gave me some more informations
I was never really comfortable with any guides I came across ....until now, I'm really tempted to go ahead and root my tab.
Would CLEANROM be one of the most updated roms?
Sent from my ASUS Transformer Pad TF300T using xda premium
Apparently I just have tons of regular SD cards laying around and none of the micro variety. Ive rooted and put custom roms on 6 phones and kindle fires in the last two weeks so it seems a bit strange that this device would be the only one that would be different, but everything ive been able to read uses a micro card. Any info would be really appreciated. Thanks! (using US wifi board by the way)
Nada?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
You sure can.
Unlock the boot loader, ( note doing so will wipe all data from your device )
Reboot into android download a ROM and place on internal memory.
Fast boot flash a custom recovery ( see my SIG for twrp recovery for xoom)
Boot into the custom recovery ( see my SIG for my YouTube videos, there is a quick video on how to enter recovery)
Once in twrp recovery select install and the flash your ROM from internal memory.
runandhide05 said:
You sure can.
Unlock the boot loader, ( note doing so will wipe all data from your device )
Reboot into android download a ROM and place on internal memory.
Fast boot flash a custom recovery ( see my SIG for twrp recovery for xoom)
Boot into the custom recovery ( see my SIG for my YouTube videos, there is a quick video on how to enter recovery)
Once in twrp recovery select install and the flash your ROM from internal memory.
Click to expand...
Click to collapse
I used The Lord all in One tool to unlock the boot loader. Im pretty sure that worked, device was seen and after it rebooted its like a completely wiped machine.
Now, then I reboot into recovery all i get is the green droid on its side with the warning triangle. I went to the TWRP post in your sig and there are 4 different install methods. I cant get any of them to work, but I havent tried option 2 because I dont have any idea how to use the adb commands. The windows script adb never sees my device although the LAIOT adb script does. I guess Im stuck on how to get TWRP onto this damn thing.
Roseysdaddy said:
I used The Lord all in One tool to unlock the boot loader. Im pretty sure that worked, device was seen and after it rebooted its like a completely wiped machine.
Now, then I reboot into recovery all i get is the green droid on its side with the warning triangle. I went to the TWRP post in your sig and there are 4 different install methods. I cant get any of them to work, but I havent tried option 2 because I dont have any idea how to use the adb commands. The windows script adb never sees my device although the LAIOT adb script does. I guess Im stuck on how to get TWRP onto this damn thing.
Click to expand...
Click to collapse
download this zip Install_Scripts_v2.3.3.0.zip - 10.03 MB
and extract
open your cmd ( command prompt )
cd ( change directory to where you extracted the above zip)
now connect your tablet to pc,
from the cmd type
Code:
adb devices
ensure that your pc sees your device, should read out sn#
now click the runme.bat
and follow onscreen instructions.
once the recovery img has been flashed ( you can verify on the xoom's screen.)
from the runme.bat select option 3 to reboot, you MUST reboot straight into recovery ( again see video for video steps here http://www.youtube.com/watch?v=koxgbdQuzOQ ) and flash rom, if you dont catch the boot process in time it will boot into android, and the custom recovery you just flashed will be replaced by the stock android recovery, and you will need to repeat the whole process. after you flash the rom your custom recovery will stick and you will be good from here on out
Hey, thanks for all your help. I finally got it going, and im really glad I wont have to do all of that stuff again, but your help was greatly appreciated.
Roseysdaddy said:
Hey, thanks for all your help. I finally got it going, and im really glad I wont have to do all of that stuff again, but your help was greatly appreciated.
Click to expand...
Click to collapse
Any time
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!
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..