.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
.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
PLEASE NOTE, YOU MUST BE UNLOCKED TO BE ABLE TO INSTALL A CUSTOM RECOVERY AND/OR CUSTOM ROM!
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?
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.
Wow.. I too have dine the same thing... Lol
Sent from my ice cream sandwich
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?
Backup is borked on 5.8.3.4. Install 5.8.1.8 (touch) or 5.8.2.0 (classic) instead.
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??
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!.
I tried method 2 but it did not work...am I supposed to insert the filename somewhere?
Sent from my SGH-I897 using xda premium
Quick question.
When I install Rom Manager from market and let it install CWM.
Do I have ext sd card support back and only lose the ability of touch?