Guys,
I've stuck the Artemis TouchFLO rom on my device without any issue. Using it for a few days without any issue. Stuck an SD card in my device to test it out...and immediately I have issues. I go into the "Settings" screen and I cannot 'x' my way out of it...it eventually comes up with a "shell error - attempting to reload shell".
I've since taken the SD card out and restarted but I'm still getting this issue.
Anyone got any ideas cos It's doing my head in
Well a hard reset sorted the issue...but I'm wondering if it will return again. Anyone have any idea what causes such an error?
Related
i recently tried to update my universal, with the crossbow rom, after pluging the device in my desktop, it started with the update, and placing a message, connection erorr , resulting in ,that my device is stuck in the boot mode, and will not react anymore.
i have tried to update ,without result , i keep getting the message 150 connection error
id there anybody out therer who has had the same problem, if so did you fix , and how did you fix it?
regards peter
I will tell you what I did it my be wrong but I unpluged the usb from the uni and pushed the front light button,power button and the reset at the same time and pluged it in again you get the popup found new device ppc. Then reran the rom update.
NO, just take the SD Card out of the slot and proceed with the update. You must be using a 4GB SD Card, aren't you?
rom upgrade ,universal dead
i keep getting the following message, even if i take the 4gb sd card out of device:
error 150 rom upgrade utility error.
please help it is driving me crazy.
regards peter
pcsw said:
i keep getting the following message, even if i take the 4gb sd card out of device:
error 150 rom upgrade utility error.
please help it is driving me crazy.
regards peter
Click to expand...
Click to collapse
Hi, are you able to get in to the bootloader mode?
Try reading:
http://wiki.xda-developers.com/inde...tion On How To Upgrade with Bootloader method
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen
http://wiki.xda-developers.com/inde...ose stuck on Boot Screen (UNI_exitbootloader)
Hope it helps.
So I was given this GPS and it's throwing me for a loop... You can power it up and see the Magellan splash screen. The progress bar will go all the way across (or sometimes stop one notch before the end...) then it'll freeze. This is as far as I've been able to get it.
When connected to a computer, it'll register as two devices. First as an unknown device, then halfway through disconnects and shows up as a Windows mobile device. A few seconds once the progress bar goes all the way across it disconnects. It never shows up as a mass storage device. Activesync will catch it momentarily.
I've tried numerous techniques to boot off an SD card or the power-reset combo to access the bootloader but nothing seems to work. Does anyone know of any other mythical techniques that may allow access to this device? I've got the latest firmware upgrade handy. How close it gets to booting makes me feel it's still fixable, I hate calling it a lost cause!
Bricked Roadmate 1212
Just got a new Roadmate 1212 and upgraded it from 3.00 to 3.12. After downloading the update to the unit it rebooted a couple of times in the process of installing the update so your problem may just be a failed update.
The update procedure also stressed not to plug in the unit into the USB before the update install program tells you to do so. If you did this you may need to delete the Windows drivers installed for the unit before attempting the update again. In my case on Vista, when I plugged the unit as prompted by the update, I got one brief message as Vista installed the driver and then the update loaded in about 5 minutes. After then update, Vista reported two drive letters for the unit. The one labeled TFAT was accessible and I was able to browse around and look at files. If you get this far, it may be possible to copy the \SYS files from a good unit and get yours up and running (just a guess).
Help!
I was messing around with the Ubuntu on Rhodium stuff that's posted in the Android sub-forum and I think something got corrupted/overwritten on my phone...
I extracted all the files on to a freshly formatted card and ran haret and everything worked file and I eventually got to the Ubuntu desktop. Then I did a soft reset to get back to WM and then the problems started.
I cannot run any unsigned apps whether they are installed on the storage card or internal memory. Whenever I try and run an app I get an error saying "The file blah cannot be opened either it is not signed with a trusted certificate...".
I cannot get back into Android or Ubuntu coz haret is unsigned too.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting my phone back to how it was.
R.
Tried installing this?
As I said in my original post, I cannot install any CABs that come from "Unknown Publishers" too and it seems that TP2-AppUnlock is one of those.
Thanks for trying,
R.
there is a setting somewhere for this. i saw it the other day while setting up a new rom.pretty sure
same problem
I have encountered the exact same issue...except that for me it occurred after booting back into WM after trying out the latest android build. Anyone have a solution?
dicko99 said:
Help!
I was messing around with the Ubuntu on Rhodium stuff that's posted in the Android sub-forum and I think something got corrupted/overwritten on my phone...
I extracted all the files on to a freshly formatted card and ran haret and everything worked file and I eventually got to the Ubuntu desktop. Then I did a soft reset to get back to WM and then the problems started.
I cannot run any unsigned apps whether they are installed on the storage card or internal memory. Whenever I try and run an app I get an error saying "The file blah cannot be opened either it is not signed with a trusted certificate...".
I cannot get back into Android or Ubuntu coz haret is unsigned too.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting my phone back to how it was.
R.
Click to expand...
Click to collapse
Just found this thread that is supposed to fix the problem: http://forum.xda-developers.com/showthread.php?t=404170
I've already hard-reset my phone so I can't test it...
I too had the same problem but with the HTC hd2. I was trying out a 2.2 rom n the camera wasn't working so I turned off the phone, when I tried going to back android haret wouldn't run .if anybody has a fix to this please let me know.
Hi there,
Have you tried the "Security configuration Manager" mentioned in the thread linked to above?
I can't test it coz I haven't broken my phone again since the initial issue but for future reference I'd like to know if it cures the problem.
Hope this helps,
Richard
Yes i've tried security configuration manager but it still wouldn't work. Does doing the hard rest work? Thanks for the help
Yes, hard reset works.
I've used it on two occasions to fix this problem.
Regards,
Richard
after using config manager i cannot sync with outlook
i am still having the issue with certificates after runnig android and rebooting HD2
any help?
i am in mexico HTC HD2 unlocked if i make a hard reset i am going to loose unlocked feature right?
Hello,
I'm new to the Android scene and already I have a problem.
I successfully upgraded my HTC Magic with Cyanogenmod.
I did it exactly like it said in the instructions on cyanogenmod wiki.
Installed Android SDK R05 for Windows and used:
bc-4.2.15.1-ebi1-signed
recovery-RA-sapphire-v1.6.2H.img
update-cm-4.2.15.1-signed
DRC83_base_defanged
HTC_ADP_1.6_DRC83_rooted_base
So i did the magic on Magic and the CyanogenMod worked, at least until recently.
My co-worker asked me to lend him my sdcard so i opened the magic and took out the sdcard from my htc that was on while i did that.
Than the trouble came forth...After a reboot the phone started booting for a long time...than it showed an error that the sdcard wasn't unmounted properly, and it didn't go away even when i inserted the sdcard back in, even after a hundred or so reboots. Than it started to crash the processes (acore and such)
Than after a milionth reboot the screen and the accelerometer stoped working, soon after that the keys followed the screen and the acc. I was thinking maybe the screen and the keys stoped working permanently and wanted to throw the phone away. But after another optimistic restart the keys worked for some time than the ball when pressed stoped responding...so i could highlight an icon on the home screen but couldn't start it. Than i accidentaly pressed it on the screen and it worked, but shortly after that everything was dead again. Than the phone started rebooting on a low battery. When rebooting to bootloader (with the battery fully charged) the screen flashes and nothing responds. But it still shows in a flash those three androids on the skates. And i can't seem to adb push the recovery.img to the sdcard...states some Read only problem. Sdcard seems alright through the card reader. So that is about it of all the problems.
So i was hoping some experts on here could give me some feedback on the device. Is it finished or can I rescue it. I really fell in love with this phone so I would much rather here the second option. I'm attaching the log from adb logcat if it is for any use to any of you...
Thanks in advance
Hi
I've got a Firephone which was randomly rebooting itself and then refusing to acknowledge the sim card or wireless network.
I decided to re-flash stock ROM via ADB and downloaded update-fire-phone-35.4.6.1_user_461013820.bin from the amazon web site.
I have managed to side load the .bin file OK and rebooted the phone. However, when I am trying to complete the set up, after choosing which language I want, the phone does not recognize my sim card so I just skip that stage and move on (tried with and without sim card and the following issue is the same). I choose the correct time zone but I'm unable to register the phone at this stage as the phone doesn't see any WiFi network. I try Register Later and the next stage is either enable or dont enable location services. It doesn't matter which one I chose as the phone then freezes and then after a while, it reboots and the whole process starts again.
I have carefully removed the back cover (out of warranty) and double checked the antenna connections are being made but this hasn't helped. I've even tried different stock ROM all the way up to update-fire-phone-32.4.6.5_user_465000520.bin but again get no further on each boot up.
Any ideas guys (girls) as its driving me mad now I cant even get a crappy working phone back. TIA
Paul
Update: Fixed the issue with Setup detecting WiFi. Removed back cover and took out antenna cable and refitted it. Must have been a loose connection. Still refusing to see my sim card (which is OK in another phone BTW).