clrcad.exe not working when I try to use it before starting android 2.2 on my htc hd2. need help thanks
I had the same problem as well, hoping for a solution
+1
Same here, I run it before launching linux but still have teh same audio problem.
bump.
Anybody know what problem is?
bumpin...
same problem here.
hm. No help huh...
I've got the same problem.
ditto... i think we need some support over here lol
I can't run it any more - it says "CLRCAD cannot be opened. Either it is not signed with a trusted certificate, or one of it's components cannot be found... blah blah" I've tried deleting it and copying over a new copy but it still doesn't work - it worked the first couple of times though?
I have the same problem. And even more: after trying run clrcad.exe now I can't run any exe from sd card!
Solution to CLRCAD.exe will not execute.
I have an HTC HD2. I have been playing around with different android builds for the last week. About two days ago CLRCAD.exe stopped working for me. I ignored it and continued to load. It was only when I got an extemely garbbled called that I realized how important it was to have CLRCAD.exe working. I tried reformatting my SD Card with not luck in getting it to work. Tried searching the forum and gave up and googled the problem which in turn lead me to this post and it seems a lot of people have this issue. I don't know the cause yet....but in a flash I thought about doing a factory restore for the windows 6.5. Eureaka!!!!! that solved my problem !!!!!
I done the same thing thinking a factory restore would solve the problem - but no..., it's not recognised on me pc nor my device - keep gettin the error "This is not a windows 32bit application."
same problem here.
Winmob does simply nothing if I click on clrcad.exe. No question if I want to run it or something.
Anybody got any idea what the problem could be?
Hellbanan
edgasket said:
I can't run it any more - it says "CLRCAD cannot be opened. Either it is not signed with a trusted certificate, or one of it's components cannot be found... blah blah" I've tried deleting it and copying over a new copy but it still doesn't work - it worked the first couple of times though?
Click to expand...
Click to collapse
Did you resolve this issue? I have the same problem and have searched for the resolution but have not found anything. Help!
Hard Reset worked for me - but still now I have to deal with black-outs (no wake-up screen up)...
Raman HTC hd2
Hi have installed successfully android on htc hd2,but having problem with calls.
i will not able to hear voice of others.
have run the clrad.exe even after, any suggestions ?
This is quite strange, because I have had Froyostone Sense V3.1 running on my stock HD2 for nearly a month without any issues. Then out of the blue, the screen went blank yesterday, so I rebooted, and then tried to run CLRCAD from the Android folder.
I then got "CLRCAD cannot be opened. Either it is not signed with a trusted certificate, or one of it's components cannot be found" message. So I downloaded the latest Froyosense, and copied over the system.ext2 and the zImage files, and a clean CLRCAD and HARET. But still I get the same thing. And I get that message on HARET as well.
Does anyone know the cause and best resolution, preferably without the factory reset?
Same issue here too. Interestingly, when I run CLRCAD, i get the same interference on the WMOS as well as ANDROID.
same here.....the exe simply does nothing when i click it.
and i cannot load android at all...............after loading the kernel for a while , the phone rebooted back to WM!!!
I am able to run CLRAD.exe and I know that is normal that nothing happens but I have problem that after loading ANDROID there is no any sound. I also tried to reset factory settings... So is there any solution to this or not?
SOLVED by Kwbr_HD2 ROM, but again stopped working after few reboots!
The first time i excecuted clrcad.exe a message appeared "do you really.. bla bla bla" (u know what i mean) which ich answered with YES. Then some days later i did a reboot and since this time the message didn't appear. But Android works also great without the message. I tryed to figure out if there is running clrcad.exe in wm but i cant see it. So, i have no clue if clrcad.exe is running, but Android works. The Sound is good!
Hello.
Yesterday I bought Toshiba Folio 100 tablet. After first run, I ran update (from 02.2011). When I downloaded it, I turn on this update. After the moment, tablet has been restarted. Instead Android screen, I saw Toshiba logo and message "booting recovery kernel image". I think it's okey, i left this tablet for night. In the morning, I didn't see no change, so I restarted tablet.
On this forum I found the way to fix this problem (instruction for install Foliomod), but in my computer, it doesn't work. After install Android SDK, I modifed android_winusb.inf, I turn on folio 100 in fastboot mode. System doesn't find drivers, and I can choosed only folder with driver, not exactly file, so I select usb_driver folder. Driver has been installed, but no one info doesn't shown. After run fastboot.exe, window appears and quickly disappears.
What can i do? Without update tablet's working so slowly.
I please for your help.
Hi All
I have a Google Nexus S, bought last year and it was working fine till last week.
It came with Android Ginger Bread, and I rooted the phone and installed several custom ROMs including Cyanogenmod.
Recently I installed Android Jelly bean ROM, and it was working fine.
Last week, I wanted to try the Cyanogedmod 10 (on Jelly bean). I went to recovery mode for taking a backup.
But I saw a recent backup which was taken before 2 months. I thought that should be fine.
I cleared all cache and did a factory reset for getting ready for the new ROM.
Now something went wrong!
I tried to reboot the device, but I could only see the usual animated CROSS logo( with four colours) for ever.
I even left the phone for more than a hour. But it is not rebooting.
//SO CAN'T RELOAD THE PREVIOUSLY WORKING OS
I tried restoring from the previous backup.. It shows that "installation complete".
After that while rebooting the device just hangs in the same place.
//SO CAN'T RESTORE FROM MY PREVIOUS BACKUP
I thought of copying the new rom in the device. I could not succeed.
I tried adb command through my SDK.
ADB is not listing my device.
In all the forums it is mentioned that to enable the USB debugging from the phone.
I cannot do this, because I cannot go into the device OS other than recovery mode.
I even tried some GUI stuff like Android commander / QtADB but every thing needs USB Enable from the OS Menu.
Finally I tried mounting disk from recovery mode.
Whenever I mount the disk, Windows 7 is fixing the file system errors and bad sectors for a while
and shows "no problems were found" and it is ready to use.
Here something weird happens.
I can copy the files in windows explorer and can see the files in the device thru explorer,
BUT when I unmount and browse from the recovery mode the files are not there. (may be the files are copied in cache)
//SO I CAN'T COPY ANY FILE TO THE DEVICE.. ( May be here I am doing something silly. )
My phone is now unusable!
Any advice/tips is highly appreciated!
Cheers
Kum
Hi
Apologies for the longwinded explaination of my problem but I wanted to be thorough and to let you have as much info as poss to know what I have tried and I think I have it mostly down here..
I recently sucessfully (I think) rooted my i9100 with Neat Rom 4.4.2, which seems very nice
I also have two ZTE Kis phones (via Virgin) which I thought I would try to revive.
I managed to flash one with Firefox OS and it seems fine for the most part although it flickers occasionally
The other one that I had rooted ages ago I eventually managed to reset my recovery via a terminal emulator and flashed a Rom back to its original state except with an unbranded rom courtesy of http://blog.podtwo.com/android/rom/de-branded ROM for ZTE Roamer2 [gingerbread].html THANK YOU SEBASTIAN
As this was not ideal as the storage space quickly disappears I though I would try to flash it with something else... and after some looking around I went here http://www.youtube.com/watch?v=n_DJhaNH14o and downloaded the miscellaneous files attached (first dumb move)
I then tried to flash each of these Roms in no particular order and finally got one of the Xperia Roms to take me to the install stage (2nd dumb move) I was working on some other stuff and yessed away in my own smugness only to find that the rebooting phone showed a green android that gradually faded to a blueish whiteout...
It also would not boot to recovery! power + volume = same android fading away...
It also would not boot to FTM
My main OS - OSX could not recognise the phone via adb/fastboot etc so I decided to try Win 7 (3rd or possibly a lot more by now dumb move)
so I booted to windows and low and behold... adb/fastboot could not see the device upon opening my Browser to try to find a solution I discovered that my Browser had been taken over by Conduit... (I am certain it was not before attaching the Kis and the suspect rom) and I was bombarded by a number of options to remove malware threats and virus' etc.. figuring something was wrong (first smart move) I switched operating systems back to OSX and ran Clam scan and Sophos scan of Windows drive (infected with something in the region of 40 nasties) I quarantined and deleted all the nasty infected files. I booted into Linux and ran ClamTK scan of the windows drive which found something in the order of 1200 threats.. some of which were standard methods used by programs but I spotted a few trojans I think amongst the readout.
I have deleted the Rom files and formatted the SD card that it was on.
Neither ADB nor Fastboot sees the infected/soft bricked Kis device from any OS
I have discovered too that the infected Kis does actually do different things when volume buttons are held down in conjunction with the power button (I am guessing that although the rom was corrupt - or perhaps not meant for my device) the phone is still trying to enter FTM mode as it just boots to a red light on.
From Linux in terminal (lsusb, usb-devices and dmesg | tail) all identify the device - attached file which has a different device id depending on the "mode" it is in when I attach it - Vendor ID is always 19d2, but Device ID is either 1353 or 0112 (the latter is when it is in FTM? mode - Vol down, power on , red light constant)
OS X also see the device: when the device ID is 1353 it identifies it as ZTE HSUSB Device, serial no ROAMER2, version 2.29, ZTE Incorporated. Whne device ID is 0112 it identifies it as ZTE WCDMA Handset Diagnostic Port
Win 7 sees it in "FTM" mode as ZTE Handset Diagnostic Interface (DSU)
Now I have... (mainly from OSX and more recently unbuntu 12.04) with my limited intellect and even more limited knowledge of programming and restricted understanding of terminal commands tried to have tried to cp files directly to the device, I have looked to try to boot from an sd card, I have tried to go into the recovery mode even though I can't see the screen and navigate blindly to the update.zip or recovery.img etc --- I have put them all on the card. I tried to do this http://linux-sunxi.org/Boot_Android_from_SdCard - but got a failure around "awutils, make" I have looked at Odin, Heimdall options, I have tried to adapt other solutions for different phones to mine (which was how I somehow or other managed to recover my CWM through terminal emulator in the first place). I have tried through ZTE to get thir automatic update program/instructions.zip (which despite being on broadband was proposing to take something in the region of 2 to 3 hours to download 136MB....! made me think that that might be how long it might take to copy my 4 and a half ish Terabytes of data... (paranoid now? MAYBE) so I cancelled the download and rebooted to Linux where I feel comparatively safe!?
BUT NOW I AM STUCK
I have the Unbranded rom and CWM recovery I can see the device but I don't know how to force the two together... can anybody help me (I have just tried very hard to resist an Obi-Wan-Kenobi joke)
I hope someone can help
I need to update the Bauhn Sphere AHD5-114 from V1.2 to V1.3 as this is a fix to repartition the device (only allows 1GB for apps, has 32GB storage).
Instructions to update, including driver files are here: https://onedrive.live.com/?cid=a25f...06&ithint=folder,zip&authkey=!ANnJGmqdleVuyX0
The Problem: The phone won't connect to the PC when the phone is off. It connects fine when on. I have tried 3 different computers and about 10 different charging cables, all using the drivers included in the folder.
It connects for 2 seconds then disconnects, windows tries to find a driver but comes up with 'device unplugged'.
Need to either fix connectivity issue or find another way to install the update (this method is with SP Flash Tool).
Note: phone is unrooted (tried Framaroot, SRSroot and Towelroot). Also I'm sure there's a fix somewhere but I've looked for hours, maybe using the wrong keywords but all I've found is connectivity issues with the phone on. All PCs have windows 7.
bump
Created this account to thank you for the files! A friend of mine has the 1GB limit issue, and I want to try their official fix first, before going to unofficial means. I'll try it and let you know what happens.
Not sure where you got with this. Initially I tried the upgrade on a Windows 7 laptop and ran into the same problem you did. The phone wouldn't stay connected. I noticed the instructions "highly recommended" doing the installation on a 32-bit Win XP machine. I gave it a try on a 32-bit WinXP machine and had the same issue. I left the software running, phone plugged in, then unplugged the computer-end of the cable and plugged it into a different USB port. It needed driver software installed, again, so I pointed it to where I'd unzipped the driver, it installed the driver (for the second time) and then the upgrade worked.
The phone is *far* more usable now, it seems that just about all the 32gb is available for app installation. This is how the phone should've been configured out-of-the-box, imo.
Thanks for making the installation software available for download. I couldn't get it from the bauhn site.