![]() |
unable to uninstall *#Starhsah Enabler
am using maemo5 when i try to uninstall *#Starhsah Enabler 0.2 it says "internal error"
i would like some help on how to remove this app from my app manager please |
Re: unable to uninstall *#Starhsah Enabler
Open xterm
Code:
sudo gainroot |
Re: unable to uninstall *#Starhsah Enabler
If AgogData's suggestion doesn't work, you can also try
Code:
sudo gainroot |
Re: unable to uninstall *#Starhsah Enabler
Well I can't run *115# to check my balance until I install starhash-enabler, so I guess you do need it even in PR1.3.
|
Re: unable to uninstall *#Starhsah Enabler
I could've sworn I tested it before... Well, if you're sure it doesn't work, fair enough.
|
Re: unable to uninstall *#Starhsah Enabler
Its working since PR1.2, i check my balance, send msgs to Vodafone (my provider) and send credits using *#
|
Re: unable to uninstall *#Starhsah Enabler
i teried both of them non work this is what happen(BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands. ~ $ sudo gainroot Root shell enabled BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) Enter 'help' for a list of built-in commands. /home/user # opt-get remove stsrhash-enabler /bin/sh: opt-get: not found /home/user #) |
Re: unable to uninstall *#Starhsah Enabler
Quote:
|
Re: unable to uninstall *#Starhsah Enabler
USSD ( 3digit *NNN# ) works since PR1.2 iirc without *#-ena
network control codes ( 2digit *NN# ) need *#-ena to work If HAM refuses to uninstall *#-ena, simply open menu in dialer and set autorotation to some arbitrary value, THEN STORE. This creates the file that *#-ena modifies on installing/uninstalling - sorry for the little flaw in install routine of *#-ena causing this inconvenience (I simply didn't think of situations where that file would vanish after *#-ena got installed - usually there are no such cases ;-D ) BTW *#-ena must get installed/uninstalled via HAM, it doesn't work in apt-get reliably, a "returns -1" or "internal error" could also mean you ran into this trap. /j |
Re: unable to uninstall *#Starhsah Enabler
i tried it again and this was wat happen (BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands. ~ $ sudo gainroot Root shell enabled BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash) Enter 'help' for a list of built-in commands. /home/user # apt-get remove starhash-enabler Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: rootsh Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: starhash-enabler 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 16.4kB disk space will be freed. Do you want to continue [Y/n]? y dpkg: error processing starhash-enabler (--remove): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: starhash-enabler E: Sub-process /usr/bin/dpkg returned an error code (1)) |
Re: unable to uninstall *#Starhsah Enabler
thanks for all ur help guys i try installing it again and it work and not sure if i want to belete it
|
Re: unable to uninstall *#Starhsah Enabler
Quote:
You also noticed about my rather simple workaround to enable uninstalling *#-ena once you managed to delete the relevant file that makes *#-ena uninstall fail when not existing (open dialer menu, select "screen rotation", switch "orientation" to some new value, "store")? Please also refer to original thread linked to under "report bug" on http://maemo.org/downloads/product/M...hash-enabler/# -> http://talk.maemo.org/showthread.php...930#post807930 , http://talk.maemo.org/showthread.php?p=756257 thanks for using *#-enabler, sorry for the inconvenience, don't forget clicking "thanks" down ->there if you feel this post or *# was useful /jOERG |
Re: unable to uninstall *#Starhsah Enabler
2 Attachment(s)
Hi guys,
I have a problem uninstalling Starhash-enabler, I have tried all the below but it gives the same error (see attached please), when I try using the Hildon Ap Man, it fails and exits and log is; "hildon-application-manager 2.2.72 apt-worker exited. apt-worker: too weak to get lock from 2311. read: Bad file descriptor" See also attached a screen capture of the same. pls assist as am not able to install or un-install/upgrade anything. Am Fred. |
Re: unable to uninstall *#Starhsah Enabler
Please give the terminal output of
Code:
sudo gainroot |
Re: unable to uninstall *#Starhsah Enabler
2 Attachment(s)
Quote:
see attached images as found after using the codes. regards |
Re: unable to uninstall *#Starhsah Enabler
Please try
Code:
sudo gainroot |
Re: unable to uninstall *#Starhsah Enabler
It has actually now gone bad;
I have two batteries, I charge and change since my usb is faulty. This afternoon, my battery died so I removed that one and put in another one which was fully charged by then. On restarting, the phone starts up as usual, nokia logo and the hands pass and after that, the phone stays on for like 5-10 seconds and goes off. After 15 seconds, it brings itself back on and this repeats over and over again. I can't really tell what went wrong, and it goes off so fast, before I even get to contents of Menu..... Confused and really confused, please advicee..:mad: |
Re: unable to uninstall *#Starhsah Enabler
Quote:
I need serious help:o |
Re: unable to uninstall *#Starhsah Enabler
Try to pull the battery for a couple of minutes for the memory to reset, try to charge the last working battery and start the N900 with that again.
If your N900 shuts itself down due to low power, it could happen that the kernel gets corrupted. Is this stock nokia kernel or kernel-power? |
Re: unable to uninstall *#Starhsah Enabler
Quote:
what happens when the kernel gets corrupted Michaaa62? btw, I have just tried to restart it, and just after entering the lock code and starts, a call came through, I answered and the call lasted up to around 1 minute. On checking it again, it was locked on the qtlockscreen and on sliding to unlock, the led lit white and went off |
Re: unable to uninstall *#Starhsah Enabler
Please try to reflash the kernel only from a firmware image. It seems the failed kernel install makes the device fail.
This is the wiki article giving you the instructions and informations about the processhttp://wiki.maemo.org/Updating_the_t...rt_topic.21.29 |
Re: unable to uninstall *#Starhsah Enabler
Quote:
|
Re: unable to uninstall *#Starhsah Enabler
Quote:
|
Re: unable to uninstall *#Starhsah Enabler
Quote:
I tried the flasher style to no avail since it looks like I'll have to do this from linux since the command looks ubuntuish "sudo....." To be honest, am not well acquitted with deep programming, anybody can help me roll out this one? I will have to learn more i know but for now I need my tablet back up....:o The only point am missing and it makes it hard is..."Flashing only the kernel from a FIASCO image" |
Re: unable to uninstall *#Starhsah Enabler
Simply face it, Maemo is also Debian-based, a little knowledge about linux will not hurt you too bad. Windows USB-driver seem to fail in certain situations. But you also could just look into running linux in a virtualbox to access the phone.
Prepare your folder with the fiasco image and the flasher utility package in an easy to access place on your hard disk, like drive C:. Grab the Live-CD from ftp://ftp.lug.udel.edu/pub/siduction...1212092122.iso This is a Debian system. Boot your PC from the CD. May be you have to access the BIOS settings to change the boot order to start the CD. Inside the running Debian-Live-CD start a terminal application, gain root rights Code:
su Code:
mount /dev/sda2 /media/diskpart2 Code:
cd /media/diskpart2 Code:
dpkg -i maemo-flasher-3.5* Code:
flasher3.5 -F RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R If not, you have to use the command without the flash-only=kernel option to reset the phone. Hope it helps! Please feel free to ask, if necessary cheers Micha |
Re: unable to uninstall *#Starhsah Enabler
Quote:
Question; I managed to get a system running on Ubuntu, do I still need the Live-CD? Or do I go into the next step direct. |
Re: unable to uninstall *#Starhsah Enabler
No need for the Live-CD in this case!
But you have to change the commands slightly for Ubuntu. You need to add 'sudo' to the commands that need root privileges. For sudo to succeed you need the password of the user: Code:
sudo mount /dev/sda2 /media/diskpart2 |
Re: unable to uninstall *#Starhsah Enabler
Quote:
I keep getting the error, "mount: mount point /media/diskpart2 does not exist" after being prompted for password and inputting the same....kindly assist. Fred. |
Re: unable to uninstall *#Starhsah Enabler
Sorry my fault, did not adapt all the code to Ubuntu, sorry! I am not that familiar with mount point naming in Ubuntu, but almost everything 'custom-made' works.
To make it clear: The partition number might differ on your PC, this is /dev/sdaX, where X is the digital to correspond to windows drive where you have the files. Add this command before the above commands Code:
sudo mkdir /media/diskpart2 |
Re: unable to uninstall *#Starhsah Enabler
2 Attachment(s)
Hi Michaa, all this time av been tryin to flash the kernel image but I seem to get issues anytime anywhere. I was able to mount my phone onto ubuntu bt now my issue is a dpkg error processing instalation, maemo-flasher-3.5. See, the third line of the code you sent me Michaa, any advice?
See below, the error message am getting.... Please assist.... Guys, am so so so so glad I made it. I was not able to flash the kernel alone, said was successful but on restarting, experienced the same issues. So I flashed the firmware and here we go, check out the image just in-case someone else has this same issue; plus please note that I didn't lose my internal memory data... Thanks to you Michaa, you inspired me to learn Terminal codes..can't thank you enough. Incase the image ain't visible; Image '2nd', size 14848 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Image 'xloader', size 14848 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Image 'secondary', size 109440 bytes Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606 Version 1.4.14.9+0m5 Suitable USB device not found, waiting. USB device found found at bus 002, device address 017. Found device RX-51, hardware revision 2204 NOLO version 1.4.14 Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0 Sending xloader image (14 kB)... 100% (14 of 14 kB, avg. 483 kB/s) Sending secondary image (106 kB)... 100% (106 of 106 kB, avg. 962 kB/s) Flashing bootloader... done. Sending cmt-2nd image (79 kB)... 100% (79 of 79 kB, avg. 742 kB/s) Sending cmt-algo image (507 kB)... 100% (507 of 507 kB, avg. 981 kB/s) Sending cmt-mcusw image (5826 kB)... 100% (5826 of 5826 kB, avg. 984 kB/s) Flashing cmt-mcusw... done. Sending kernel image (1705 kB)... 100% (1705 of 1705 kB, avg. 983 kB/s) Flashing kernel... done. Sending and flashing rootfs image (185728 kB)... 100% (185728 of 185728 kB, avg. 987 kB/s) Finishing flashing... done CMT flashed successfully |
All times are GMT. The time now is 18:20. |
vBulletin® Version 3.8.8