Related
i been reformatting and trying to everything i can to get the hd2 to work android but when i try to run clrcad or haret i get this error
The file 'CLRCAD' cannot be opened.Either it is not signed with a trusted certificate,or on of its compenents cannon be found.If the problem persists,try reinstalling or restoring this file
The file 'haret' cannot be opened.Either it is not signed with a trusted certificate,or on of its compenents cannon be found.If the problem persists,try reinstalling or restoring this file
can someone pleaseee help
no idea what problem you have i only know that CLRCAD doesnt show any activity. if you see notthing .. thats how it should work
The signing messages i've never seen
I had the same thing.
My android 'crashed' and my telephone did a soft-reset.
After that I could not open any program again, always said: Either it is not signed with a trusted certificate etc.
Did a hard reset, and again on android. But a bit annoying
is there even a way to fix it? cause it was working at first then now it doesnt work at all and i reformatted my sd card so many times and trying to redo everything all over again and still no luck
i have the mattc 1.5 desire build in my phone for over 2 weeks and its
my fav one but just yesterday it i couldnt find my charger and phone died
when i charged it and try to go back to android it wouldnt let me in
same dumb message , then i it stopped with the message but now it gets
stuck in were it booting android ughh its annoying i only want Desire build ! mattc 1.5
and ive try downloading other links but they dont work anyone have links that work ??
To answer OP's question, the easiest way you can do to fix it is downloading another Android build and run it to see if it works. It might be caused by corrupted downloaded files.
Btw, have you gone through all essential setup steps?
yeah im pretty sure i have...i also tried downloading other ones too same message. i HARD SPL the phone...then i unzip all the files to the root of my sd card...and if that didnt work then i also tried putting it in an android folder...still didnt work..and reformatting the sd card also.
Same issue as above, I ran android for the first time today. I have gone back to it couple times during the day with no issues.
About an hour ago I tried to run it again and this time I got the error message.
I have tried the following
- Restarting the phone
- Copying different android builds onto the card and running them
- Formating the sd card and running different android builds
My hd2 is running a
- stock rom 1.66.707.1
- Radio 2.12.50.02_2
stock roms probably dont allow the running of unsigned files to protect the system files, either find the cab file to disable this or you need to change to a custom rom
a lot of people like the energy rom but i dont know how to flash the rom..
YES!!!! THANK YOU... it worked i flashed my rom to the ENERGY ROM and then i got it to android with macfroyo build
Viktorca said:
Same issue as above, I ran android for the first time today. I have gone back to it couple times during the day with no issues.
About an hour ago I tried to run it again and this time I got the error message.
I have tried the following
- Restarting the phone
- Copying different android builds onto the card and running them
- Formating the sd card and running different android builds
My hd2 is running a
- stock rom 1.66.707.1
- Radio 2.12.50.02_2
Click to expand...
Click to collapse
I have noticed that none of the applications on the sd card were working anymore. It was the same message as when trying to run android.
Hard reset and now everything (including android) is working.
If it happens again, I think it will be time to try a custom rom because using android is far too fun to give up.
well i didnt hardset mine because its unlocked it is tmobile but i got it unlocked for AT&T so i was to scared to hardset it and it might have relocked...idk if that is possible but didnt want to take the chances but i flashed it with the energy rom, and then did the android. but at first my android wasnt working. it will boot and then when i turn it off and back on it didnt work and that was pissing me off..but now i got it working. its pretty much easy doing this..its just time consuming if you dont know what ya doing cause it took me a while
It won't relock!
Sent from my HTC Desire using XDA App
oh...thanks..well i got it working now =] on android and its so much better then WM6.5
Same problem
Hi, I have a similar problem. the thing is that I try t run clrcad but nothing. then I flash the phone again and it works during 3 more times that I have to run again.
Really i´ts anoing.
I would like to if somebody knows why this happens.
Thank you
My backlight/brightness has just started to go on and off/up and down all the time via WM6.5.
Im not sure if its releated but it seemed to start after the last I used excellers bootloader, I forgot to switch to my android card got a error and then after that ive had the prob.
Ive restarted and also left battery out for 10 mins and every time I go back into windows have same problem.
Anybody know solution other then trying hard reset?
Have you tried to disable the automatic brightness adjusting?
Yeah tried that.
Rebooting into android fixed it though. Looks like when haret doesnt find android folder it for some reason affects the power/backlight. Whether this is to do with the loader or my specific custom rom im not sure.
Hey Guys,
So..... I'm trying to fix my friend's TouchPad and having no luck what so ever. I'll describe the problem the best I can and then tell you what we've tried so far.
In a nutshell, it seems almost like the drive inside the touchpad is write protected.
I can delete and add files no problem but if I either
Restart Luna: It does a sort of "half reset" and start acting weird. Preware might not work properly or sometimes the app catalog won't connect. Plus all the icons rearrange themselves to their factory setting with my downloaded apps (both store and preware) being bundled together under the downloads tab.
or
Restart Touchpad: Any changes made during the previous session get reverted back to a point about a week ago (not factory default). Everything from icon positions, apps installed to even content on the touchpad. For example I could delete a movie or a song from my library, restart the device and the file would reappear. It's like it reflashes an earlier image of itself. (Skynet has become self aware?)
So here is what I've tried so far.
Full Erase: Nothing happens. Device restarts and we're back to square one.
Secure Full Erase: Same thing.
WebOS Doctor: Doctor starts up... I click through the screens, progress bar appears. Usually somewhere before 28% Doctor just quits and says it had an issue resetting my TouchPad and to go to the support page. The support page is useless, just tells me to re-download and restart/connect both my devices. Which I have done.
(I'm also using the latest version of WebOS Doctor and the ToucPad is on 3.0.2)....
I also tried running WebOS Doctor from Dev. mode (Hard Reset TouchPad and then hold Power+VolUp)
When I restart the device after a WebOS Doctor attempt, things revert back to the same state as before.
help?
ps: The touchpad functions fine otherwise. Everything runs it's just....stuck....
did he have 3.0.3 and/or the chomper android ipk installed?
if so, the kernel could be stuck on there. i'd try going back to 3.0.3, install chomper 0.1, uninstall through menu (NOT THE X-OUT UNINSTALL), and then try another doctor (3.0.2 or 3.0.3 shouldnt matter)
to be honest i don't have to much know how with tablets. my guess is if you have issues with webosdoctor
you have hard drive issues. maybe googling hard drive problems will eliminate that.
Sent from my HTC HD2 using XDA App
Just triple checked..... not on 3.0.3 (he's running 3.0.2) and no chomper/android ipk....
He did have the Warthog Kernel OCed at 1.7ghz installed. Though that ran perfectly fine for the the last few weeks. We just tried uninstalling the kernel just to double check and see if it has any effect, but no luck. Still back to previous state after restart, with Warthog Kernel back in place.
Update: Just flatout reinstalling the stock kernel on top does nothing either.
lehel.babos said:
Just triple checked..... not on 3.0.3 (he's running 3.0.2) and no chomper/android ipk....
He did have the Warthog Kernel OCed at 1.7ghz installed. Though that ran perfectly fine for the the last few weeks. We just tried uninstalling the kernel just to double check and see if it has any effect, but no luck. Still back to previous state after restart, with Warthog Kernel back in place.
Update: Just flatout reinstalling the stock kernel on top does nothing either.
Click to expand...
Click to collapse
Have you tried membooting the device off a kernel you ripped from webOS Doctor?
http://www.webos-internals.org/wiki/How_To_Recover
webOS doctors reinstall
Nburnes said:
Have you tried membooting the device off a kernel you ripped from webOS Doctor?
The best way per HP support to reload the webOS doctor is to go to the HP profile manager from a Windows PC and you can download and install clean webOS doctor. I have successfully reloaded a clean webOS on my touchpad using the following steps.
You will need to put your touchpad into recovery mode, first turn off you touchpad then hold down volume up and power button and will go into recover mode
Connect USB cable between Windows PC and Touchpad
Go to the HP profile manager website and select download webOS Softer
Follow the steps on screen
---------- Post added at 12:06 PM ---------- Previous post was at 12:06 PM ----------
Nburnes said:
Have you tried membooting the device off a kernel you ripped from webOS Doctor?
http://www.webos-internals.org/wiki/How_To_Recover
Click to expand...
Click to collapse
Best way to reload the webOS doctor is to go to the HP profile manager from a Windows PC and you can download and install clean webOS doctor. You will need to put your touchpad into recovery mode, first turn off you touchpad then hold down volume up and power button and will go into recover mode, connect USB cable between Windows PC and Touchpad.
Click to expand...
Click to collapse
I have the same problem as the OP. Also running 3.0.2, updates fail, doctor fails. Nova booted the image extracted from doctor, can't write anything, can't wipe LVM. It's like the whole thing is write protected.
If anyone finds a solution, please post!!!
try reinstalling novacom drivers, also, try just rebooting the pc, you'd be surprised how often that works (i had the same problem, rebooted, was able to doctor with no problem after that. seems like you have to hard terminate the connections)
Solidus_n313 said:
try reinstalling novacom drivers, also, try just rebooting the pc, you'd be surprised how often that works (i had the same problem, rebooted, was able to doctor with no problem after that. seems like you have to hard terminate the connections)
Click to expand...
Click to collapse
TouchPad says it can't umount the log volume (as a matter of fact it can't even mount it to begin with), so its entirely unrelated to any computer the doctor runs on.
Eh, if only doctoring was the key. I'm not able to make persistent changes to the block device or the filesystems while I am working in a terminal, both the developer mode in WebOS or the nova booted rescue image. System executes write commands, but then I check things didn't get written.
As for computer, HP made me do doctoring on two different computers. Unsurprisingly the result was not any different.
HP is taking their sweet time to call me back from Level 3, personally I'm quite ready for the replacement, as at this point I am certain that I won't be able to fix it short of opening it up, and programming the flash using other means.
I just found that i have the same problem. Worst of all, it seems it's doing this on cyanogenmod also. I have android and webos on dual boot, tried to erase the android part with ACMEUninstaller, after reboot android was back. Erased the cm particions with novaterm, same result after reboot. I would really appreceate some help please, really desperate ...
I have the same problem with my touchpad. do you find any solution.
rai177 said:
I have the same problem with my touchpad. do you find any solution.
Click to expand...
Click to collapse
I also have the same problem and I've ignored my Touchpad for months as a result. I read somewhere that a person with the same problem got it replaced by HP under warranty, but that was a long time ago.
I got the itch to work on this problem again. I will report any solutions I discover.
You guys ever figure out this issue?
Sent from my HTC One using Tapatalk
read only
A friend of mine has the same read only problem on her touchpad, and she doesn't have android or has never tried installed android. I tried factory resets and webos doctor and nothing works, after reboot it reverts back to last known good configuration. I haven't tried to do a complete data reset through the tptoolbox v41, has anyone tried that method? Any other ideas that may work, or is this really a hardware issue? Thanks
Just got a a used Droid X2 and accidentally updated to 2.3.5/1.3.418 now trying to follow these instructions and root it:
[How To] Root DX2 2.3.5/1.3.418 magic md5 method
I installed MotorolaDeviceManager_2.3.9.exe from here:
MY MOTO CARE
Hooked-up the phone which was factory reset, set 'USB debugging', and ran the batch files trying USB connection in both 'PC Mode' & 'Charge Only' and keep getting these errors:
Code:
error: more than one device and emulator
error: device offline
The batch stops at '---Reboot Bootloader---' and nothing happens. I've tried following the instructions to hold volume up while turning off and on, but the phone just hangs at 'Starting RSD protocol support' and the batch stops at '< waiting for device >'.
I've even tried uninstalling and re-installing the Motorola drivers and going through everything again, but no change. Any help?
Thanks!
I just downgraded to Android version 2.3.4/1.3.380 with RSDLite and tried the VooDoo method, but Pete's Motorola Root Tools failed.
The Root Tools program was able to detect the device initially, but none of the commands seemed to have any effect and when it tried to reboot the device nothing happened; it goes through the rest of the steps and then indicates that it failed.
I'm running Windows 7 and even tried a system restore then re-installing the drivers, but no change. When I check the device manager there are no unknown devices or anything like that.
Got it!
Finally tracked down the solution to the error 'more than one device and emulator'
Had to use adb.exe that came in Pete's Root Tools to run the command 'kill-server' in the command window:
Code:
adb.exe kill-server
When I checked
Code:
adb.exe devices
initially there were multiple devices listed, somehow the phone was not disengaging when I was plugging and unplugging it. Running kill-server reset the list so that running the root application could finally identify the phone correctly.
If anybody knows why this was happening and how to prevent it please let me know.
Now I can finally go on to flashing a ROM!
jhsu888 said:
Got it!
Finally tracked down the solution to the error 'more than one device and emulator'
Had to use adb.exe that came in Pete's Root Tools to run the command 'kill-server' in the command window:
Code:
adb.exe kill-server
When I checked
Code:
adb.exe devices
initially there were multiple devices listed, somehow the phone was not disengaging when I was plugging and unplugging it. Running kill-server reset the list so that running the root application could finally identify the phone correctly.
If anybody knows why this was happening and how to prevent it please let me know.
Now I can finally go on to flashing a ROM!
Click to expand...
Click to collapse
Let me know what rom you stick with, I just ordered one 4 days ago and should be getting it today. I'm torn between eclipse(on gingerbread) and Cyanogenmod 10(jelly bean) (i want to be able to call, text and use data reliably, and I like being on the newest version of stuff)
DQEight said:
Let me know what rom you stick with, I just ordered one 4 days ago and should be getting it today. I'm torn between eclipse(on gingerbread) and Cyanogenmod 10(jelly bean) (i want to be able to call, text and use data reliably, and I like being on the newest version of stuff)
Click to expand...
Click to collapse
I actually haven't bothered trying CM10, after I got everything running smooth with Eclipse I just left it at that. I can say that I haven't run into a single issue with Eclipse and I've been using it pretty heavily installing/uninstalling apps and trying all the components including the camera, wifi, led lights, sms and calling - all working solid.
A little off topic, but I also installed a home launcher app and after trying GO Launcher and Holo, I found ADW to have the easiest way for me to manage all the apps in groups and still be highly customizable. GO launcher I found buggy and Holo looked great out of the box, but felt a little limited.
I would also suggest getting the Widget Locker app, it's paid, but worth it to be able to customize the lock screen and get to things like the camera, flashlight, dialer etc quickly from the lock screen. I tried a few of the free ones for that and they were buggy or gave me a flash of the old lock screen, Widget Locker works pretty seamlessly.
Enjoy it!
I am a first owner DX2 owner running CM7. Most of the original owners have all moved on and upgraded. I am waiting until my contract ends to ditch VZW and go to prepaid to save money. But I digress.
You have to be on 2.3.4 to install CM7. This is by far my favorite rom, second to eclipse. It is faster and smoother than eclipse. Eclipse starts to slow down over time.
CM10 also has to be installed from 2.3.4. It's fun to play around with, but at the end of day it is too glitchy and not functionable enough due to the bootloader being locked. So in my opinion, it's best to stick with the gb roms.
Sent from my MB870 using Tapatalk 2
Juice3250 said:
I am a first owner DX2 owner running CM7. Most of the original owners have all moved on and upgraded. I am waiting until my contract ends to ditch VZW and go to prepaid to save money. But I digress.
You have to be on 2.3.4 to install CM7. This is by far my favorite rom, second to eclipse. It is faster and smoother than eclipse. Eclipse starts to slow down over time.
CM10 also has to be installed from 2.3.4. It's fun to play around with, but at the end of day it is too glitchy and not functionable enough due to the bootloader being locked. So in my opinion, it's best to stick with the gb roms.
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Cm9 wasn't too bad. Its quite a bit more stable then cm10 and now that time has past more apps actually work on it. Give it a try and see how you like it. I couldn't stand the delayed text issue that appears on cm7
Sent from my SCH-I535 using xda premium
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
shared_joy said:
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
Click to expand...
Click to collapse
use fastboot to manually flash the stock partitions, then it will be clean stock, and you can start over.
search google for how to setup fastboot on your linux machine if you dont know how, i cant help with that.