.18!?
Does this means there's a problem with .20 ?? I don't see any (so far)..
Sent from my GT-I9000 using Tapatalk 2
No I think they just didn't make.20 touch screen capable.
Sent from my EVO using Xparent Blue Tapatalk 2
[RECOVERY] ClockWorkMod Official "TOUCH" recovery v5.8.1.8 [UPDATED 24/5/12]
- Thread starter Doktaphex
- Start date
-
- Tags
- development
No I think they just didn't make.20 touch screen capable.
Sent from my EVO using Xparent Blue Tapatalk 2
Hi,
Does anyone know what happens if you try and flash a custom recovery blob, say from here:
http://xdaforums.com/showthread.php?t=1601942
directly to the /dev/block/mmcblk0p4 partition using dd when you're on a locked bootloader, assuming one has root? Will it not allow it or will it brick it?
Also, how to find out if your bootloader is unlocked? Is there some change in some getprop entry?
If you are unlocked it's written on top left during first boot screen. And you can't do what you want to do. At best it will do nothing at worst you'll end bricked.
If an experienced dev wrote this warning in OP there is a good reason.
I installed CWM via Method 2 after unlocking bootloader. Worked perfectly from Android terminal. No problems.
However, I initially tried to install via Method 1 (ADB). I've done this before on my Android phones, so I'm not a noob, but I'm no expert either. The problem is that I was not able to find a driver which would allow ADB to recognize my TFP. I opened a command prompt (shift+right click) in the SDK tools folder (where all of the relevant files are located), and the command "ADB devices" showed nothing. Asus sync was not installed on the TFP. My TFP was in fastboot mode. USB debugging enabled. I started by letting Windows 7 search for a driver. No go. So I deleted that driver and installed the naked driver from this forum. Still no go. While this is not an urgent problem, I would like to be able to communicate with my TFP via ADB in the future in case I have a problem.
Thanks in advance for any ideas.
Edit: I am an idiot. I forgot that "adb devices" only works when device is booted, not in fastboot. Naked driver is working fine for ADB with my TFP.
However, I initially tried to install via Method 1 (ADB). I've done this before on my Android phones, so I'm not a noob, but I'm no expert either. The problem is that I was not able to find a driver which would allow ADB to recognize my TFP. I opened a command prompt (shift+right click) in the SDK tools folder (where all of the relevant files are located), and the command "ADB devices" showed nothing. Asus sync was not installed on the TFP. My TFP was in fastboot mode. USB debugging enabled. I started by letting Windows 7 search for a driver. No go. So I deleted that driver and installed the naked driver from this forum. Still no go. While this is not an urgent problem, I would like to be able to communicate with my TFP via ADB in the future in case I have a problem.
Thanks in advance for any ideas.
Edit: I am an idiot. I forgot that "adb devices" only works when device is booted, not in fastboot. Naked driver is working fine for ADB with my TFP.
Last edited:
jyarborough
Senior Member
jyarborough
Senior Member
Well I just bought cwmtouch via room manager and I can't boot recovery. Weird thing IDs I was able to go in recovery and wipe clashes two weeks ago via volume down and power holding. Now my prime vibrates and boots up. Any got any ideas for me? I really want to flash this update tonight
Edit... i got it to w work
Sent from my Transformer Prime TF201 using Tapatalk 2
Last edited:
Hi all,
I flashed the CWM touch 5.8.3.4 (downloaded from http://www.clockworkmod.com/rommanager) using Method #2.
When i want to backup current rom, i receive this message:
"error while backing up boot image"
Anybody help me?
I flashed the CWM touch 5.8.3.4 (downloaded from http://www.clockworkmod.com/rommanager) using Method #2.
When i want to backup current rom, i receive this message:
"error while backing up boot image"
Anybody help me?
Backup is borked on 5.8.3.4. Install 5.8.1.8 (touch) or 5.8.2.0 (classic) instead.
jyarborough
Senior Member
jyarborough
Senior Member
Hoe do I get that 5.8.1.8? It is not an option in rm under cwm recoveries
Edit.. nevermind,, I found it
Sent from my ice cream sandwich
Last edited:
can someone help a brutha out?! i flashed CWM v5.8.2.0 to make a backup, booted into recovery, and made a backup. BUT, now when i select "reboot system now" it keeps booting me back into recovery. i've tried about 10 times, and can't figure out how to get my system rebooted.
i tried to restore the backup i had just created - didn't work. i then wiped and reflashed rom and gapps - didn't work. i also tried flashing a couple of different recoveries, and then rebooting into recovery thru the advanced menu. but, that doesn't work either - it just takes me back to CWM v5.8.2.0, and won't let me reboot system.
my usb cable is at home and i'm at work, and i can't get the blasted thing to boot into system. any suggestions??
i tried to restore the backup i had just created - didn't work. i then wiped and reflashed rom and gapps - didn't work. i also tried flashing a couple of different recoveries, and then rebooting into recovery thru the advanced menu. but, that doesn't work either - it just takes me back to CWM v5.8.2.0, and won't let me reboot system.
my usb cable is at home and i'm at work, and i can't get the blasted thing to boot into system. any suggestions??
Gosh...
Always same cwm bootloop... When will someone erase prime support in ROM manager...
Go in dev threads, stickies ones, Debrick your prime... Option 1a, and then throw cwm in a dumpster... Twrp only!.
damn, i was afraid of that. problem is that i don't have my usb cable with me... i should have learned by now. i've been running TWRP, and only flashed CWM so that i could make a backup, until i had time to read up and go thru the nvflash process. thanks for the help!
Better late than never! Was given a TF 201 my friend didn't want so thought I would breathe new live in 'er! Thanks for the reminder of ADB pushing!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
35[RECOVERY] ClockWorkMod Official "TOUCH" recovery v5.8.1.8 [UPDATED 24/5/12]
As I seem to have come under a little fire for not stating that you need to be unlocked to install a custom recovery, I thought that I would add a little clarification.
At the time I started this thread the unlock had only just been released, and EVERYONE knew that the methods contained within this thread were only possible if you were unlocked. I apologize for my assumptions.
PLEASE NOTE, YOU MUST BE UNLOCKED TO BE ABLE TO INSTALL A CUSTOM RECOVERY AND/OR CUSTOM ROM!
I also received a little flak for not explaining the adb/fastboot processes more clearly. While I can understand that many people who come to XDA are new to the whole custom ROM kettle o' fish, it is my honest opinion that if you have not already read up about ADB and FASTBOOT and have an understanding of how to use them, you most definitely have absolutely no business whatsoever flashing a recovery or ROM at all.
I was a noob when I first arrived here at XDA, but I read and re-read as much information as possible before going anywhere near flashing custom recoveries and/or ROMs to my Desire HD.
There are plenty of great guides around for learning how to use ADB and FASTBOOT, please I implore you, before attempting to flash anything to any device you own, read these guides over and over again until you feel that you have the confidence to flash your device without the need for someone to hold your hand.
I think that about covers everything that I wanted to say other than a big thank you to Swiftks and Striatum_bdr for answering so many peoples questions in this thread.
That's all folks.
As always Peace, Dok
!!!YOU MAY WANT TO GO HERE FOR UPDATED UNOFFICIAL RECOVERIES, BOTH TOUCH AND STANDARD VERSIONS ARE AVAILABLE!!!
Huge thank you to Roach2010 for the updated recoveries.
LETS GET THE FORMALITIES OUT OF THE WAY
1. I did not build this, it is the official CWM touch recovery from the CWM website.
2. If you brick your device flashing this, I am in no way responsible.
3. If you brick your device flashing this, I am in no way responsible.
4. Please, follow all steps very carefully, especially the actual flashing step.
5. I have personally flashed this without issue.
6. THERE IS CURRENTLY NO VERSION OF CWM FOR THE PRIME THAT SUPPORTS EXTERNAL SDCARD STORAGE. USE THE INTERNAL MEMORY FOR ALL YOUR FLASHING NEEDS.
CREDIT: KOUSH FOR HIS AWESOME WORK
So, you want some lovely touch based CWM recovery on your device?
METHOD NUMBER 1: The Fastboot! - NO NEED FOR ROOT
Come right this way you fearless young chap.
http://www.clockworkmod.com/rommanager
download the tf201 touch recovery, version 5.8.1.8
Now, switch off your device, then hold volume DOWN and the power button together until your Prime shows the RCK screen.
At this point press volume down. This will take you to the options of which fastboot is one.
Switch to fastboot mode by pressing volume DOWN (It's the USB symbol, but you knew that already else you wouldn't be here) then press volume UP to select the option.
Connect your USB cable now, if you haven't already.
Next you need to open a command prompt/terminal window and cd to where you have downloaded the .img
Next type fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
Once the flash has completed (the screen will sit with a full blue bar doing nothing) you can reboot to recovery as per normal, but now you will have the wonderful touch recovery.
METHOD NUMBER 2: The blob!
CREDIT to Striatum_bdr
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/"path to blobfile" of=/dev/block/mmcblk0p4 (REPLACE "path to blobfile" with the path to where you have saved the file).
You're done.
Reboot, the blob file will be flashed at boot (same as kernel).
METHOD NUMBER 3: The Terminal noob!
CREDIT to darksiiide
It is also available via ROM Manager, for a fee.
!!!HUZZAH FOR KOUSH!!!
I hope you all enjoy.
My recommendation would be to do a fresh backup of your ROM as soon as you boot into the new recovery, just in case.9Touch Recovery is completely buggy on my phone, I'll wait a little for some user feedback lol...
EDIT: another method (need to be rooted)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/path/to/blobfile of=/dev/block/mmcblk0p4
You're done.
Reboot inrecovery as usual, the blob file will be flashed at boot (same as kernel), you'll ony need to reboot in recovery.5
Yes, change the following - take out the """...""" to where you have the file on the sdcard:
$ su
# dd if=/"""file path""" of=/dev/block/mmcblk0p4
Like this for me: # dd if=/sdcard/clockworkmod/cwm_touch.blob.img of=/dev/block/mmcblk0p4
Should work for you then.2
You will lose touch, yes; however, you will not gain ext sd card support. There is NOT a CWM version available yet in any fashion.
Sent from my EEEPAD using Tapatalk 2 Beta-5
